WZR-HP-G300NH wi-fi connections suddenly stopping or freezing

[dfresh4130]

I purchased the WZR-HP-G300NH from newegg last week and have had it up and running for a little less than a week now.  I switched to the latest version of the user friendly firmware (1.76) mainly to test out the NAS and media server functionality.  Overall, it's been fine.  The only problem I've had is my wireless connections on my laptop and other devices (Sony SMP-N100) will suddenly stop.  If I try to ping the router I get timeouts.  My PC connected via ethernet has no issues accessing the internet and I am able to get to the router console with no problems.  Sometimes I've had to power cycle the router to get my connection back and other times it's as simple as letting windows disconnect and reconnect to the wireless network.  I'm running a mixed mode of b/g/n with it set at 40MHz, WPA/WPA2 mixed mode and TKIP/AES mixed mode.  Can anyone confirm if they've had any issues like this or possible solutions?  Thanks

[kamiller42]

Stand in line. There are other threads describing the same problem. My router suddenly exhibiting this. I am using DD-WRT, but we've seen non-DD-WRT users having the same problem. It seems the number of people experiencing this is growing by every week.

 

Buffalo has said nothing about this issue and provided no solution.

[kd4das]

Mine started doing this a few days ago, too. It seems to happen every couple of days so far -- very annoying. I'm on the stock 1.76 firmware.

[darrinbutts]

Yes, I've been waiting for a fix for this, and I suspect that none will come.

 

Since you just purchased this, I would recommend you return it if you can.  Neither of the 2 buffalo firmwares fix this issue, and Buffalo support is non-responsive, and this issue has been in existence for at least a year now.  I may try OpenWrt (unsupported) or buy an Asus RT-N16 which uses a different chipset, and has good reviews.

[kamiller42]

My guess is the WZR is a discontinued product. It's receiving no attention from Buffalo because they are busy working on spring product introductions to sell at near MSRP during summer and at sale prices by Christmas.

 

I have bought many routers, one being a cheapy from Frys. They have all worked better than the WZR. Major letdown of a product and likely to be my first and last Buffalo product.

[drmemory]

Details about the setup you are using - missed packets, compared to number of packets received, and more.

we can't help without the full information. "Disconnecting" is not enough infomation - there are many possible reasons for disconnecting.

[m4p]

I was thinking of purchasing a WZR-HP-G300NH, but after reading this thread, I think I'll wait and see if there is a fix for this before purchasing.  I really hope they fix it because I have had good luck with Buffalo products, but I will buy another brand if this issue isn't fixed.

[kamiller42]

For me, it's not an issue of error packets. The whole wireless stack crashes. When it goes down, nothing can connect. It is no longer broadcasting SSID. It's dead. No wireless device can connect. All wired devices still work however.

 

if it helps, I have 21 TX errors and 0 RX errors currently and wireless services are up and running.

 

Is there a log in DD-WRT I can paste here?

[drmemory]

you have 21Tx errors compared to how many Tx's total (10000 Txs and 21 errors isn't much, but 100 Tx and 21 errors is)? The DDWRT log is very long and detailed. I would go through it and find where something unusual is being logged and post it with up to about 5-10 lines right before the unusual part happened.

[kd4das]

 

Here's part of a logfile on mine from today. Wireless stopped sometime between 9 a.m. and noon. After it dies, there's no SSID being transmitted and wireless devices don't see the network, even though the wireless LED is lit up on the device. Mine just started doing this within the last week, and nothing changed in the configuration otherwise. 

2011/02/23 15:57:53 AUTH wl0: AUTH: Updating group key

2011/02/23 15:57:48 NTP SUCCESS: set time : Wed Feb 23 15:57:48 2011

2011/02/23 15:48:50 DHCPS sending ACK to 192.168.11.5

2011/02/23 15:06:20 DHCPS sending ACK to 192.168.11.7

2011/02/23 14:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 13:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 12:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 11:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 10:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 10:06:30 AUTH ath0: STA 00:22:2r:34:b0:f1 IEEE 802.11: deassociated

2011/02/23 10:06:30 AUTH ath0: STA 00:22:2r:34:b0:f1 IEEE 802.11: deauthenticated due to local deauth request

2011/02/23 10:06:29 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 10:06:29 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 10:06:29 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 10:06:29 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 10:06:28 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 10:06:06 AUTH ath0: STA 00:22:2r:34:b0:f1 IEEE 802.11: deassociated

2011/02/23 10:05:55 AUTH ath0: STA 71:1a:04:c7:ca:3d IEEE 802.11: deassociated

2011/02/23 09:54:47 DHCPS Request incoming from G2-Laptop(len:12)

2011/02/23 09:53:37 AUTH wl0: AUTH: WPA/WPA2 - Group Key handshake successful: 00:22:2r:34:b0:f1

2011/02/23 09:53:37 AUTH wl0: AUTH: WPA/WPA2 - Group Key handshake successful: 71:1a:04:c7:ca:3d

2011/02/23 09:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 09:45:42 DHCPS Request incoming from G2-Laptop(len:12)

2011/02/23 09:42:15 DHCPS Request incoming from G2-Laptop(len:12)

2011/02/23 09:41:45 DHCPS sending ACK to 192.168.11.4

2011/02/23 09:41:45 DHCPS Request incoming from G2-Laptop(len:12)

2011/02/23 09:41:42 AUTH wl0: AUTH: PSK authentication successful: 71:1a:04:c7:ca:3d

2011/02/23 09:41:42 WIRELESS ath0: had associated successfully : 71:1a:04:c7:ca:3d

2011/02/23 09:13:07 AUTH ath0: STA 71:1a:04:c7:ca:3d IEEE 802.11: deassociated

2011/02/23 09:08:37 DHCPS sending ACK to 192.168.11.9

2011/02/23 09:08:37 DHCPS sending OFFER of 192.168.11.9

2011/02/23 09:08:37 DHCPS sending OFFER of 192.168.11.9

2011/02/23 09:08:35 AUTH wl0: AUTH: PSK authentication successful: 00:22:2r:34:b0:f1

2011/02/23 09:08:35 WIRELESS ath0: had associated successfully : 00:22:2r:34:b0:f1

2011/02/23 08:53:37 AUTH wl0: AUTH: WPA/WPA2 - Group Key handshake successful: 71:1a:04:c7:ca:3d

2011/02/23 08:53:37 AUTH wl0: AUTH: Updating group key

2011/02/23 15:57:53 AUTH wl0: AUTH: Updating group key

 

[simboo]

add me up to this...

 

wifi had been acting weird for about 2 weeks now. Running DD-WRT.

 

I need to disconnect the router and reconnect to get it to work for a short while. Wired computers are not affected, only wifi...

 

Looks like I'm getting a new router tomorrow...

 

Shame on you Buffalo, this was a great router until it started to crash the wifi for no reason. I have 3 computers that rely on this.

 

*How about give us some details so we can help,  kd4das is giving detailed logs-drmemory*

[racingsnake]

I have just bought and installed a WZR-HP-G300NH and am also experiencing a problem with wireless sessions. Frustratingly, most devices in the house connect reliably and with no problem (Windows XP Toshiba, Ubuntu netbook, iPod Touch, mobile handset etc). The only one which has an issue is a Lenovo Thinkpad (Windows XP Professional). As others have reported on this thread, the wireless connection is sometimes established correctly and works for a while. Then it drops.

 

I have tried with WPA, WPA2, mixed mode, AES and TKIP. I'm not prepared to degrade the crypto any further and fall back to WEP or unencrypted, because that is not a workable configuration going forward. However, I suspect the crypto is not the issue.

 

Looking at the network connection and the Airstation logs, what seems to happen is that the DHCP server (or the laptop, not sure which) suddenly and randomly decides it doesn't like that IP address any more. Despite apparently successful REQUEST/ACK messages between the laptop and the router, there is then a "deassociated" message, followed by a "workstation had associated successfully" message. The router then sends several OFFER messages with the expected IP address, the laptop sends REQUESTs, and neither of them completes the protocol.

 

Here is a sample of the log file:

 

=============================================

Date Time Type Log Content

2011/02/24 10:35:34	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:34	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:26	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:26	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:23	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:23	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:23	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:23	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:16	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:16	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:12	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:35:12	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:35:08	AUTH	wl0: AUTH: WPA/WPA2 - Group Key handshake successful: 00:21:6a:11:1e:7c
2011/02/24 10:35:08	AUTH	wl0: AUTH: PSK authentication successful: 00:21:6a:11:1e:7c
2011/02/24 10:35:08	WIRELESS	ath0: had associated successfully : 00:21:6a:11:1e:7c
2011/02/24 10:34:17	AUTH	ath0: STA 00:21:6a:11:1e:7c IEEE 802.11: deassociated
2011/02/24 10:31:52	AUTH	wl0: AUTH: PSK authentication successful: 00:21:6a:11:1e:7c
2011/02/24 10:31:52	WIRELESS	ath0: had associated successfully : 00:21:6a:11:1e:7c
2011/02/24 10:31:52	AUTH	ath0: STA 00:21:6a:11:1e:7c IEEE 802.11: deassociated
2011/02/24 10:31:45	DHCPS	sending ACK to 192.168.2.42
2011/02/24 10:31:45	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:31:42	DHCPS	sending ACK to 192.168.2.42
2011/02/24 10:31:42	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:31:42	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:31:42	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:31:40	AUTH	wl0: AUTH: PSK authentication successful: 00:21:6a:11:1e:7c
2011/02/24 10:31:39	WIRELESS	ath0: had associated successfully : 00:21:6a:11:1e:7c
2011/02/24 10:28:16	AUTH	ath0: STA 00:21:6a:11:1e:7c IEEE 802.11: deassociated
2011/02/24 10:26:52	DHCPS	sending ACK to 192.168.2.42
2011/02/24 10:26:52	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:26:49	DHCPS	sending ACK to 192.168.2.42
2011/02/24 10:26:49	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:26:49	DHCPS	sending OFFER of 192.168.2.42 wiltonem4621r
2011/02/24 10:26:49	DHCPS	Request incoming from wiltonem4621r(len:13)
2011/02/24 10:26:47	AUTH	wl0: AUTH: PSK authentication successful: 00:21:6a:11:1e:7c
2011/02/24 10:26:47	WIRELESS	ath0: had associated successfully : 00:21:6a:11:1e:7c
2011/02/24 10:26:43	AUTH	ath0: STA 00:26:b0:39:87:3a IEEE 802.11: deassociated
2011/02/24 10:26:13	DHCPS	max_leases value (256) not sane, setting to 64 instead
2011/02/24 10:26:13	DHCPS	udhcpd (v0.9.9-pre) started

 

=============================================

 

I can't waste working time on this; I'm falling back to the previous (Belkin) router. If Buffalo or the forum can provide an answer and a fix, I'll try it. If not, the router will be coming back to Buffalo very soon. Shame that this was my first Buffalo experience.

[Jotin]

The only thing I can suggest really is a firmware flash and restore to factory defaults. Besides that it would have to be either a fault in your router's hard ware or an envirmental issue that is causing the drop outs. For Racingsnake, if it is just one pc that is having the issue when numorous otherdevices can connect I'm thinking it would be the one device that has the issue. I would try resetting the router and leaving everything default and see if that device can connect. If it cannot try removing encryption and then try seeing if it can. If it still cannot, try either another network in your area or another router if you have a spare one and see if the problem persists. 

[drmemory]

Have you tried giving the laptop a static IP, other that .42 (in case another machine is trying to grab that IP) and specifying in the router that only that laptop gets the static IP?

[Madnick]

I have had the same issue using static IP:s only in my network, so I'm pretty sure it's not a question of that.

TX/RX errors I don't believe in, since mine did it with Buffalo DD-WRT 14998 with absolutely zero TX/RX errors. Millions of packets transmitted...

One "fix" is the community test build 16144. It restarts the radio automatically when it crashes, at least on mine.

Makes the life a little bit easyer, although isn't really a fix.

 

If you Buffalo people say you are not aware of this bug or hardware issue in this WZR-HP-G300NH, then go and buy one for your self and see.