Wifi Died 1.5.2 wrt54gl

Report wireless and/or network connectivity problems in this forum.

Moderator: Moderators

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: Wifi Died 1.5.2 wrt54gl

Post by mix »

1.3.9 will give you the old driver, it will also give you the linux 2.4 kernel. I don't know what you would gain by doing that and then upgrading to 1.4.5. I am pretty sure the restore saved configuration settings won't work between these versions either. If you find that the 1.3.9 firmware works better, you need to stick with it.
WRT54GL v1.1
Gargoyle 1.4.7

hnl_dk
Moderator
Posts: 408
Joined: Mon Aug 29, 2011 12:37 pm

Re: Wifi Died 1.5.2 wrt54gl

Post by hnl_dk »

It sounds like wrt54gl is using the b43 driver and that the old driver is working more stable.
as anyone tried using the b43legacy driver?
It should run more stable than b43 on old devices like the wrt54gl.
It would be cool if someone with this hardware could test the b34legacy driver.
Router: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4

Culex
Posts: 28
Joined: Sat Dec 25, 2010 5:38 am

Re: Wifi Died 1.5.2 wrt54gl

Post by Culex »

So far it's been over 20 hours and the wifi hasn't dropped. First time was after 15 hours and I'm not too picky since I got a script to automatically restart the wifi incase it locks up.

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: Wifi Died 1.5.2 wrt54gl

Post by mix »

b43legacy works on cards with a core revision of 4 or less. I am pretty sure all the WRT54GL's have core revision of 8 or 9. Mine is 9 at least.
WRT54GL v1.1
Gargoyle 1.4.7

hnl_dk
Moderator
Posts: 408
Joined: Mon Aug 29, 2011 12:37 pm

Re: Wifi Died 1.5.2 wrt54gl

Post by hnl_dk »

mix wrote:b43legacy works on cards with a core revision of 4 or less. I am pretty sure all the WRT54GL's have core revision of 8 or 9. Mine is 9 at least.

It is recommended for core revision <=4, but as it is an 2.6 version of the bcm43xx driver, that people recommend to go back to for stability, would it be nice to know if b34legacy could do the same trick as bcm43xx does.
If I had such a router, would I at least try to check it (it would always be possible to go back to b34).
Router: TL-WR1043ND - Gargoyle 1.5.4
AP: TL-WR1043ND - Gargoyle 1.5.4

Culex
Posts: 28
Joined: Sat Dec 25, 2010 5:38 am

Re: Wifi Died 1.5.2 wrt54gl

Post by Culex »

I'm not that picky really. The wireless monitor script seems to be working. After about 24 hours it happened again.

2012/01/09 08:28:15.59 M dnsmasq-dhcp[10108]: dhcpinform(br-lan) 192.168.1.140 00:21:63:d2:62:29
2012/01/09 08:28:15.59 M dnsmasq-dhcp[10108]: dhcpack(br-lan) 192.168.1.140 00:21:63:d2:62:29 dad-pc
2012/01/09 08:30:14.79 M crond[11167]: user root pid 30374 cmd /usr/bin/set_kernel_timezone >/dev/null 2>&1
2012/01/09 08:33:57.78 M sysinit: 192.168.1.2 dropped one
2012/01/09 08:34:17.82 M sysinit: 192.168.1.2 dropped two, restarting wireless.
2012/01/09 08:34:19.76 M kernel: device wlan0 left promiscuous mode
2012/01/09 08:34:19.76 M kernel: br-lan: port 2(wlan0) entering disabled state
2012/01/09 08:34:27.60 M kernel: b43-phy0: loading firmware version 410.2160 (2007-05-26 15:32:10)
2012/01/09 08:34:27.89 M kernel: b43-phy0: loading firmware version 410.2160 (2007-05-26 15:32:10)
2012/01/09 08:34:27.97 M kernel: device wlan0 entered promiscuous mode
2012/01/09 08:34:27.98 M kernel: br-lan: port 2(wlan0) entering forwarding state
2012/01/09 08:34:31.21 M hostapd: wlan0: sta 00:1e:e5:4d:7e:0d ieee 802.11: authenticated
2012/01/09 08:34:31.22 M hostapd: wlan0: sta 00:1e:e5:4d:7e:0d ieee 802.11: associated (aid 1)
2012/01/09 08:34:31.28 M hostapd: wlan0: sta 00:1e:e5:4d:7e:0d wpa: pairwise key handshake completed (rsn)
2012/01/09 08:34:33.09 M kernel: device wlan0 left promiscuous mode
2012/01/09 08:34:33.09 M kernel: br-lan: port 2(wlan0) entering disabled state
2012/01/09 08:34:34.10 M kernel: device wlan0 entered promiscuous mode
2012/01/09 08:34:34.10 M kernel: br-lan: port 2(wlan0) entering forwarding state
2012/01/09 08:34:34.89 M hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: authenticated
2012/01/09 08:34:35.09 M hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: associated (aid 2)
2012/01/09 08:34:35.14 M hostapd: wlan0: sta 00:21:63:d2:62:29 wpa: pairwise key handshake completed (rsn)
2012/01/09 08:34:35.47 M dnsmasq-dhcp[10108]: dhcprequest(br-lan) 192.168.1.140 00:21:63:d2:62:29
2012/01/09 08:34:35.47 M dnsmasq-dhcp[10108]: dhcpack(br-lan) 192.168.1.140 00:21:63:d2:62:29 dads-laptop


The script checks every minute. The last computer to check was Dads-PC/Dads-Laptop and doesn't look like it wasn't authenticated before going down. There's a few minutes between the dhcp request and the detection which means it was still working... I don't know what to say as the logging isn't that detailed?

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: Wifi Died 1.5.2 wrt54gl

Post by mix »

You don't see any error messages of any kind then eh? Wireless just craps out?
WRT54GL v1.1
Gargoyle 1.4.7

Culex
Posts: 28
Joined: Sat Dec 25, 2010 5:38 am

Re: Wifi Died 1.5.2 wrt54gl

Post by Culex »

Yeah nothing. hostapd process is still running. Dont know if it gets killed and restarted using the command 'wifi'. If you notice in the logs the wifi gets reenabled only to get disabled and reenabled again a a few seconds later which is redundant. Would be nice if there was a way to get gdb in there?

Did see this in the logs, don't know if it's something related as wifi didn't cut out. It's the same laptop, the only difference between this and all other machines is it's using Vista instead of Windows 7. Perhaps there's a bug in the authentication causing wifi to die, will try WPA and see if the problem continues.

hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: authenticated
hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: associated (aid 2)
hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: associated (aid 2)
hostapd: wlan0: sta 00:21:63:d2:62:29 ieee 802.11: associated (aid 2)
hostapd: wlan0: sta 00:21:63:d2:62:29 wpa: received eapol-key 2/4 pairwise with unexpected replay counter
hostapd: wlan0: sta 00:21:63:d2:62:29 wpa: pairwise key handshake completed (rsn)
dnsmasq-dhcp[10108]: dhcpinform(br-lan) 192.168.1.140 00:21:63:d2:62:29
dnsmasq-dhcp[10108]: dhcpack(br-lan) 192.168.1.140 00:21:63:d2:62:29 dad-pc

Culex
Posts: 28
Joined: Sat Dec 25, 2010 5:38 am

Re: Wifi Died 1.5.2 wrt54gl

Post by Culex »

Changed Authentication to WPA TKIP, AES doesn't work period. No dice. Internet still cuts out. On occassion the router will actually panic and reboot. Turned out wireless was pretty unusable.

I could be watching Netflix for 2 hours, then restarting 10 times after trying to download a 64mb file because it would continually cut out. I've gone over to OpenWRT and test both bcrm-2.4 and brcm47xx.

mix
Posts: 292
Joined: Sun Feb 27, 2011 11:18 am

Re: Wifi Died 1.5.2 wrt54gl

Post by mix »

That sucks. I don't know what to say, mine is still working fine, uptime is 6 days. The only thing I have noticed is that I get the following error message in dmesg sometimes "TCP: time wait bucket table overflow", but this is probably some kernel setting that is set to low. Maybe a particular brand of wireless card on one of your clients is exposing and triggering a bug in the b43 driver. I guess if the wireless is failing in a high load situation, like many of the openwrt bugs seem to indicate, maybe you are just using more bandwidth than me so I never see it. Out of curiosity, how fast is your internet connection? What speed is your processor clocked at? Anyways, if you figure anything out please let us know. Gargoyle should be using basically the same exact wireless drivers as OpenWRT 10.03.1.

I'll continue to recommend Gargoyle 1.4.5 and WPA PSK (WPA TKIP) for wireless for the WRT54GL.
WRT54GL v1.1
Gargoyle 1.4.7

Post Reply