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
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.
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.
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.
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.
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.
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.
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?
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.
2011/02/23 15:57:53 AUTH wl0: AUTH: Updating group key
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*
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:
=============================================
| 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.
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.
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?
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.
The forums including here, DD-WRT forums as well as OpenWRT forums are filled with people trying to get this router to work without dropped Wifi connections, and the only way I've seen people solve it is to buy a different router.
There are two kind of wireless drops...
This thread is about #2.
There was a suggestion to reset defaults. I have telneted to the router and erased nvram. It's still crashing.
Mine is now going on two days without wifi shutting down daily. I simply downgraded the firmware from 1.76 to 1.74. So far, so good.
I don't know if this helps but I help me...
My Wireless connection kept resetting ever hour putting my computer into a local network connection only..I would get a yellow ! icon on my wireless connection on my windows 7 laptop taskbar. All I needed to do is disconnect and reconnect to the router and it would work perfectly. I decided to mess around with the router settings and after a few minutes I noticed a rekey interval setting in wireless-config->basic(11n-g-b) was set to 60 minutes I changed that to 0 so it will never reset my key and It's works.
I also had a problem connecting to the router's web config page with a wireless connection(it work great with wire access) so I noticed a setting under muticast control called snooping.The definetion of snooping is "Snooping observes multicast control packets like IGMP to control unnecessary packet transfer to wired and wireless port."..By enabling this it now seems to work great I have no complaints about this router at all..I love all the nice features this has..media server and bittorrent...
I hope this helps someone other then me...
kd4das wrote:Mine is now going on two days without wifi shutting down daily. I simply downgraded the firmware from 1.76 to 1.74. So far, so good.
I've successfully been running 1.74 without as well without issue. The only problem with this router using buffalo is you have to reboot every change, no internal loopback if your trying to test an internet site and the menus are slow.
I think I found a partial solution around Buffalo's bug of the crashing wifi driver. It's been working the past week or so.
I schedule a cron job to reset the ath0 wireless interface. (This is better than a cron job to reset the router.) As a bonus, I issue a command to juice the signal to maximum power, something I can't achieve through the web interface. The only downside is if you reset your router, the power won't be reset until the cron job runs.
Here's my cron job... just past into the cron section in under Administration/Management,,,
00 04 * * * root ifconfig ath0 down
01 04 * * * root ifconfig ath0 up
02 04 * * * root iwconfig ath0 txpower 100mW
I have it turning off at 0400, back on at 0401, and powered up at 0402. It's likely they can run in sequence at 0400, but I haven't tried it. I issue the command to go to 100mW, but my router achieves maxes 79mW.
>>> The only downside is if you reset your router, the power won't be reset until the cron job runs.
Why don't you put it in the startup script (under DD-WRT Admin->command) ?
Good idea. Will do.
To be honest, I didn't put much thought into it because I don't reset often. I just added. Thanks.