Printable View
If you use WPA or WPA-PSK, then this strangeness is probably due to WPA supplicant software (i.e. vendor utilities). If you're running WXP SP2, then it's probably a good idea to remove utilities and let windows to configure your card.Quote:
Originally Posted by int
if i connect directly to my ISP without the Asus, i did not get any DNS Server Errors, i can connect to Ebay in my account.Quote:
Originally Posted by Oleg
with the CR3c i was not able to log in ebay.
strange
maybe ill tray again next week
Does this firmware allow to use the rootfs from a stock wlhdd firmware? I have extracted rootfs from 1.2.3.2 WLHDD. Would I need the kernel image too?
Have not tried that, as I do not have wl-hdd, but it should work. No kernel image needed, but I'm suggesting to replace at least wl.o and et.o modules. In fact, replacing whole /lib/modules is a good idea.Quote:
Originally Posted by hugo
I use only WEP! and i dont use any utilities on windows..... (i dont like them)Quote:
Originally Posted by Oleg
Don't you think I would get a better speed using the one from the stock firmware? Latest tests from 1.2.3.0 shows a good speed measurement?Quote:
Originally Posted by Oleg
Unlikely. They've got speed increase due to switching to ext3, which I've performed initially. Also, wl-hdd kernel sources is a complete fake.Quote:
Originally Posted by hugo
WDS with WPA-PSK/AES. I used it with the previous version 1.9.2.7-3b.Quote:
Originally Posted by Antiloop
WDS with WPA/WPA-PSK never worked with 1.9.2.7, I'm wonder why it worked in 3b. If I recall correctly there was no changes in this part in the 3c.Quote:
Originally Posted by jbrbv
After testing, I had my wl-hdd booting a system. But probably all nvram are false, because I couldn't access it using wifi or ethernet. Usuallly when switching from one to one other, I still get some heartbeat by scanning the network cable. I suppose it has booted, but not set any value.Quote:
Originally Posted by Oleg
I leave the next part for the more adventurous, my baby daughter need more attention than my wl-hdd right now :)
yes, nvram settings are totally different. this due to the fact, that stock wl-hdd uses semi-complete 1.8 style firmware. :)
First of all: Great work Oleg. Everthing works just fine.
So, I've got a problem concerning my smb.conf. I searched the internet for quite a while, read some forums and then built my smb.conf. All commands seem to be okay, I can access the share via network.
But whenever I copy new files on the share, the filenames are changed to lower case.
I'll just post my smb.conf, maybe s.o. has got an idea what's wrong:
Code:[general]
workgroup = ASD1
netbios name = abc
server string = abc
preserve modes = Yes
preserve case = Yes // Don't change filenames - doesn't (?) work
interfaces = 192.168.1.129/24
mangled names = No
log file = /tmp/harddisk/samba-log.%m
default case = Upper
case sensetive = No
mangle case = No
[wl-hdd]
path = /tmp/harddisk/
public = Yes
writeable = Yes
browseable = Yes
Perhaps you need to set 'case sensitive' to 'Yes' too.
I'm now using 2 WL-500g's, WDS with WPA-PSK/AES and 1.9.2.8. I got confused by your answer about 1.9.2.7.Quote:
Originally Posted by Oleg
I'll try the Oleg versions with WDS.
Quote:
Originally Posted by kn0rz
try this:
In NT I had the problem that using names shorter than 8 letters were converted to lower when naming it like 'UPPER' you can set this nvram value to solve thisQuote:
[global]
workgroup = WERKGROEP
guest account = nobody
security = share
browseable = yes
guest ok = yes
guest only = yes
log level = 1
max log size = 100
encrypt passwords = no
preserve case = yes
short preserve case = yes
[share]
path = /tmp/harddisk
[share$]
path = /tmp/harddisk
writable = yes
force user = root
browseable = no
Code:nvram set usb_vfat_options=shortname=winnt