Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I have noticed that occasionally, with my customised fun_plug script, the WLAN light doesn't come on when I switch the router on, or sometimes it comes on and then goes out again. Consequently, I don't get wireless access.
I've tried commenting out most of the fun_plug script, and the problem still seems to be there. The problem seems to be due to a sleep command that I added, as removing it solves the problem.
This is very strange, not least because fun_plug is run as a background process, so I can't see how it's interfering with the rc.sh script.
There is a workaround for this, which is to add the following lines to the end of the script.
ifconfig ra0 up
/bin/wireless
Offline
I haven't noticed that on mine. I used to have sleep 10 when I exported root through samba. I'll reenable it and see if the problem shows up on mine.
By the way, routers such as the WRT54G/GS can be used as a bridge or extender as they have multiple wireless interfaces. The DSM-G600 only has one, correct? I suppose to turn it into a bridge one can plug in an USB wireless unit. Has anyone tried this?
--
Quang
Offline
If you type "ifconfig -a", there are wds<n> devices listed, where <n> is 0 to 7. I'm pretty much a beginner when it comes to Wireless LAN, but someone else might be able to confirm that the only thing preventing the device being used as an extender is the firmware as the ralink driver itself supports WDS.
To use a USB wireless unit, I think you'd need to compile a USB driver for it.
Offline
I have also seen this problem lately. Thanks for your fix.
if [ ! `ifconfig | /mnt/HD_a2/busybox cut -c1-5 | grep "^ra"` ] || [ ! `lsmod | grep rt2500 | /mnt/HD_a2/busybox cut -c32 | grep 2` ] then ifconfig ra0 up /bin/wireless # debug how many times we need to fix this wifi bug # echo `date +%Y-%b-%d,%H:%M:%S` >> /mnt/HD_a2/wifi.log fi
//edit
This is the error I get if wireless fail to load.
SIOCSIFFLAGS: Cannot allocate memory D_WLN_SetCountryRegion: IOCTL fail change bridge V2.02.03062006 detect wireless device D_WLN_SetWlanOnOff: IOCTL fail D_WLN_SetCountryRegion: IOCTL fail D_WLN_SetEncryptionMode: IOCTL fail SIOCIWFIRSTPRIV_SETREMOVEKEY: IOCTL fail D_WLN_SetConnectionMode: IOCTL fail D_WLN_SetChannel: IOCTL fail D_WLN_SetAuthenticationMode: IOCTL fail D_WLN_SetEncryptionMode: IOCTL fail D_WLN_SetConnectionMode: IOCTL fail D_WLN_SetSSID: IOCTL fail D_WLN_SetChannel: IOCTL fail D_WLN_SetAuthenticationMode: IOCTL fail D_WLN_SetEncryptionMode: IOCTL fail D_WLN_SetPresharedKey: IOCTL fail D_WLN_SetSSID: IOCTL fail GetMediaConnectStatus = 0 connect SIOCIWFIRSTPRIV_GETBSSIDSSIDRSSI: IOCTL fail get macaddress = 00:00:00:00:00:00 SIOCIWFIRSTPRIV_GETBSSIDSSIDRSSI: IOCTL fail rssi = 0
Last edited by sala (2006-09-17 17:19:13)
Offline
hi
is it posible to replace a mini-pci for atheros chip en8602 400mw card and what will it take ?
as the card in it is junk
dusan
Offline
dusan2 wrote:
hi
is it posible to replace a mini-pci for atheros chip en8602 400mw card and what will it take ?
I guess it is, but you need to compile a module for your new wifi as well as wireless tools, also you need to configure all your wifi realted settings by hand, over telnet.
Offline
The wireless on my box dies after several days of uptime. The SSID is no longer broadcasted, so I can't join the network. I have tried doing the following:
ifconfig ra0 down ifconfig ra0 up /bin/wireless
This has no effect. Since it takes approximately an hour to repair permissions after a reboot, I'd like to avoid a reboot if possible. Any suggestions?
Thanks,
Joe
Offline
You can't fix it unless you reboot, it's simple as that.
To resolve long boot-up you need to setup second partition for your files (/dev/sda3) and mount it manually using fun_plug.
You might want to try latest US firmware. I think they did change something in hard drive mount script, but I am not sure if this fixes chmod bug because I have not tested it out yet.
Offline
Thanks sala. I think that the latest US Firmware no longer runs chmod on the entire filesystem. My reboot time was on the order of seconds rather than close to an hour after applying the 1.0.2 patch.
Joe
Offline