After two months of reliable operation my wifi unit is now failing to connect to my wireless router. Blinking blue LED. I was able to get it to reconnect for a short while today by power cycling the router, my cable modem, and the wifi unit. But the problem has returned.
Nothing has changed on my router as far as SID and password, and I have 9 other devices able to hook up to it fine.
I did upgrade the router firmware two weeks ago, but up until this morning the wifi was fine.
Any tips on debugging this through the teraterm connection or other means?
wifi stopped working
Re: wifi stopped working
Assuming you meant wifi firmware:
$$$
CMD
ver
wifly-GSX Ver 4.00.1, Apr 19 2013 11:48:31 on RN-131
$$$
CMD
ver
wifly-GSX Ver 4.00.1, Apr 19 2013 11:48:31 on RN-131
Re: wifi stopped working
Roberto - here is some more info (from poking around in wifly docs). Is it possible that the wifi is not storing the authentication mode correctly ? (see BOLD items below)
Thanks,
Jim
<4.00> set sys printlvl 4
AOK
<4.00> save
Storing in config
<4.00> reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
CMD
reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
CMD
set wlan auth 4
AOK
<4.00> get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=MIXED
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> save
Storing in config
<4.00> reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Thanks,
Jim
<4.00> set sys printlvl 4
AOK
<4.00> save
Storing in config
<4.00> reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
CMD
reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
CMD
set wlan auth 4
AOK
<4.00> get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=MIXED
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> save
Storing in config
<4.00> reboot
*Reboot*Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Auto-Assoc HOLT chan=0 mode=NONE FAILED
Re: wifi stopped working
It never did.
What auth mode do you have setup in your router??
I'd try using WPA2-PSK with AES encryption instead of mixed.
See if that works.
If you use command SCAN, do you see your network?
What auth mode do you have setup in your router??
I'd try using WPA2-PSK with AES encryption instead of mixed.
See if that works.
If you use command SCAN, do you see your network?
Roberto.
Re: wifi stopped working
Yes, it does see the network with scan.
According to the RA wifi docs, the command I issued: "set wlan auth 4" is supposed to enable WPA2-PSK, right?
Note in the log above you can see I issued that command but the "get w" command displays "mixed" as the authentication mode. I thought that was confusing ...
BTW my wireless router is set up as WPA2-PSK and AES
According to the RA wifi docs, the command I issued: "set wlan auth 4" is supposed to enable WPA2-PSK, right?
Note in the log above you can see I issued that command but the "get w" command displays "mixed" as the authentication mode. I thought that was confusing ...
BTW my wireless router is set up as WPA2-PSK and AES
Re: wifi stopped working
Any new devices on the network or in the house? I added a baby monitor and it caused all kinds of havoc.
Re: wifi stopped working
Make sure that the SSID and passphrase are exactly the same.
They are case sensitive and if you can, avoid any quote or space, or better, non alphanumeric characters.
They are case sensitive and if you can, avoid any quote or space, or better, non alphanumeric characters.
Roberto.
Re: wifi stopped working
Hi Roberto - I am not sure how to explain this. But it seems WPA2 is actually authentication mode 2? This does not correspond to either the RA wifi manual posted under support, or the wifly documentation. Both those documents say it is '4'. I'm not sure how it was ever working, or what changed. But I got it back up by setting authentication mode to 2, and this is for WPA2-PSK, AES. Go figure ...
Thanks for the help.
-jim
With a little experimentation:
<4.00> set w a 2
AOK
<4.00> get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> save
Storing in config
<4.00> reboot
*Reboot*CMD
get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> get i
IF=UP
DHCP=ON
IP=192.168.1.117:2000
NM=255.255.255.0
GW=192.168.1.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0
Thanks for the help.
-jim
With a little experimentation:
<4.00> set w a 2
AOK
<4.00> get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> save
Storing in config
<4.00> reboot
*Reboot*CMD
get w
SSID=HOLT
Chan=0
ExtAnt=0
Join=1
Auth=WPA2
Mask=0x1fff
Rate=12, 24 Mb
Linkmon-Infra=5
Linkmon-AP=3600
Passphrase=<snip>
EAP_Id=userid
EAP_User=peap-user
<4.00> get i
IF=UP
DHCP=ON
IP=192.168.1.117:2000
NM=255.255.255.0
GW=192.168.1.1
HOST=198.171.134.6:80
PROTO=TCP,
MTU=1524
FLAGS=0x6
TCPMODE=0x0
BACKUP=0.0.0.0