WZR-HP-G300NH with Buffalo branded DD-WRT: packets dropping

[Timmy]

Before the Buffalo branded DD-WRT came out I tried the latest release from DD-WRT and it exhibited packets dropping right out of the gate.  The problem went away when I reverted back to the 1.74.  After upgrading to the Buffalo DD-WRT today it had the same issue.  I am using Verizon DSL (PPPoE) and with no fancy configuration. Only with PPPoE/Wireless setup thats all!  With both Buffalo branded DD-WRT and DD-WRT firmware I kept a continuous ping to www.cisco.com and half of the ACKs were timed out.  Also, when I tried to open a webpage to www.cnn.com and it just never complete the download.  I also observed that if the ping reply was continuous for say 10 times it gets timed out right away when I tried to open webpage connection.

 

Does anyone there have these issues?  Also, with the 1.74 I am getting erratic wireless disconnects - the router log showing DEAUTH.  It AUTHs ok and then in a few seconds it will DEAUTHs again and the process repeats.  At times it will be good for an hour or so but at times it just exhibit this behavior for a long time.  (yeah...the signal strength is strong - max signal bars!)

 

Anyone out there using PPPoE (specifically Verizon) experienced this problem?  I had a feeling there is something wrong with the DD-WRT PPPoE module, and a problem with the 1.74 wireless module!

[perler]

Well… the PPPoE module… I suspect it has deep problems on DD-WRT: I am connecting here to a VDSL modem, plain Siemens make, which seems to be having no issues with either my Linksys WRT160N nor 1.74. When I'm on the official DD-WRT, I have like a stable connection for a couple of seconds, then the connection drops, and then… nothing, pressing reconnect, rebooting the router… to no avail… connect the modem to the Linksys… nada… rebooting the modem… bingo, all normal, reconnect the WZR… internet for a couple of seconds, until the modem hangs… so, well, logic might argue that the modem is to blame… but the freaking thing WORKS completely fine on 1.74 and the linksys… if it wasn't for the wireless disconnects on 1.74 or the lack of USB and Gigabit on the Linksys I would stay as far away as I could from DD-WRT… after about a year of back and forth, I think I am finally about to throw in the towel and get some other gear… :smileysad: 

[dnd108]

I have similar problems once I upgraded to Buffalo's official release of dd-wrt firmware. My latencies are high 700ms or more, sometimes I see period of 2-4ms latencies which is followed by a period of very high latencies, packets are dropping even when I ping it from a laptop that is just 5 feet away. My signal strenght is always very weak (-86 RSSI) even 5 ft from the router. I am not sure what to do next, but this is not working out for me.

 

 

[dnd108]

I called Buffalo tech support and first level support is utterly useless, they'll give you bogus answer that interference is a problem which you cannot verify unless you have a spectrum analyzer. 2nd level support was slightly more knowledgeable, but they gave me same bogus answer. When I asked why my old WRT54G gives me RSSI signal strength of -35 and WZR-HP-G300NH gives me pathetic RSSI signal strength of -83, 2nd level tech again blamed the interference. When I asked if WRT54G and WZR-HP-G300NH operate on same 2.4GHz frequencies, so why few days ago I had no interference on WRT54G and I had excellent signal strength, why is WZR-HP-G300NH is experiencing so much interference? Buffalo 2nd level tech had no answer. 2nd level tech mentioned that in Buffalo's dd-wrt firmware I can increase TX power to 35 and antenna gain to 70, which I did, but I got no improvement in signal strength. RSSI is still -83, but my transmit rate increased from 2 to 39.

 

Another problem is they whenever I download a file latencies increase so much that in some cases connection is dropped, but most of the times my latencies are like this.

 

64 bytes from 192.168.1.1: icmp_seq=220 ttl=64 time=184.577 ms
64 bytes from 192.168.1.1: icmp_seq=221 ttl=64 time=201.429 ms
64 bytes from 192.168.1.1: icmp_seq=222 ttl=64 time=1145.231 ms
64 bytes from 192.168.1.1: icmp_seq=223 ttl=64 time=161.345 ms
64 bytes from 192.168.1.1: icmp_seq=224 ttl=64 time=180.032 ms
64 bytes from 192.168.1.1: icmp_seq=225 ttl=64 time=303.078 ms
64 bytes from 192.168.1.1: icmp_seq=226 ttl=64 time=77.742 ms
64 bytes from 192.168.1.1: icmp_seq=227 ttl=64 time=1627.542 ms
64 bytes from 192.168.1.1: icmp_seq=228 ttl=64 time=627.099 ms
64 bytes from 192.168.1.1: icmp_seq=229 ttl=64 time=1726.530 ms
64 bytes from 192.168.1.1: icmp_seq=230 ttl=64 time=813.800 ms

 

I didn't get a feeling that Buffalo tech support knows how to troubleshoot this, they are asking me to RMA this unit which I will do, so we'll see what happens with the new unit.

[dnd108]

There is good thread on dd-wrt.com about Atheros wireless settings for those who are running Buffalo's dd-wrt firmware: http://www.dd-wrt.com/wiki/index.php/Atheros/ath_wireless_settings

 

Even after following instructions from the above page, my connection sthrenght and speed are just pathetic, below is the ping output while loading cnn.com page. It appears that any time there is slightest load on this routher, latencies go through the roof and the connection is dropped.

 

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=202.245 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=184.206 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=203.849 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=266.147 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=369.621 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=240.245 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=305.449 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=102.723 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=263.713 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=2162.414 ms
Request timeout for icmp_seq 19
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=3231.353 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=3245.548 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=2648.168 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1709.034 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=777.656 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=18.724 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.668 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=10.510 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=14.514 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=196.111 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=163.861 ms
^C