I got my new WHR-HP-G300N 2 days ago and i directly installed the DD-WRT firmware(v24sp2-14512) from Buffalo website .I am having a significant packet loss when pinging yahoo and google ,on both wired and wireless connection .
I switched back to the buffalo firmware (1.82) and no more packet loss .
I have noticed that a lot of other people are having the exact same problem but the support team @Buffalo don't have an answer for that .
I would like to hear an answer from their support team about this issue ,do they know already about it but they don't admit it ? Are they working on a fix for that ?
Since the firmware was written by DD-WRT and granted it is supported on this model, does not mean that we have access to the source or the ability to debug the firmware. Basically, if the issue is discovered/known then it is passed along to be included in a firmware revision as necessary. I didn't hear about this issue until just recently but I will pass it along to help ensure the problem is looked at before the next firmware release.
Thank you for your quick reply ,please keep us posted about the updated fix when available .
We are keeping the DD-WRT engineers informed of all issues with the FW. Please post as much information about issues, as you can, with details/screenshots.
If packet loss is happening, it should happen for all hosts (not just google and yahoo). What kind of internent connection are you using?
isso wrote:I got my new WHR-HP-G300N 2 days ago and i directly installed the DD-WRT firmware(v24sp2-14512) from Buffalo website .I am having a significant packet loss when pinging yahoo and google ,on both wired and wireless connection .
I switched back to the buffalo firmware (1.82) and no more packet loss .
I have noticed that a lot of other people are having the exact same problem but the support team @Buffalo don't have an answer for that .
I would like to hear an answer from their support team about this issue ,do they know already about it but they don't admit it ? Are they working on a fix for that ?
Hi Drmemory ,
I gave you Google and Yahoo as an example ,but the packet loss is for all internet address that are pingable .
I live in Canada and my ISP is Shaw cable with a motorola Surfboard SB5101.
I tried for the 2nd time to re-install DD-Wrt and i disable firewall but i had the exact same problem of packet loss when pinging internet addresses put no packet loss pinging the router (from wired and wireless connection).
Other than the packet loss ,i noticed also that the reply time fluctuate too much when pinging the router and internet addresses(using wired and wireless connection ) and it was too high ,for example reply time pinging yahoo is from 99 to 220 ms,pinging the router is 20ms.
Moreover the wireless signal constantly changing to the worst ,for example when i use Band Width 40 MHZ the connection on the laptop start at 270Mbps then keep dropping till it reaches 135Mbps .(i am using N wireless)
I switched back to the Buffalo Firmware and everything is working like normal ,no more packet loss and the reply time pinging yahoo is 60ms constant ,pinging the router is 2 ms.
But with Buffalo firmware ,using band width 20 ,the max connection speed is 65 Mbps and with Band Width 40 the Max connection speed is 150Mbps ,i don't know why i am not getting to 300 Mbps,i double check my wireless adapter to use auto(20/40).
I am seeing a very similar problem. I'm using the official DDWRT 14512 firmware on my WHR-HP-G300N, and most of the time it works very well. However, every few days our internet connection starts chugging and there is packet loss at the router. Restarting the router clears the issue up for a few more days, and then it comes back.
I'm considering reverting to the original Buffalo firmware, but I'd greatly prefer to continue using DDWRT.
BuffaloTech, what kind of data would help you diagnose this problem?
when the packet loss occurs how much free memory does the router have? could be memory leak issue.
It might be a leak. I haven't reproduced the problem lately, but here's my current memory usage after 81 hours uptime. Normal?
Mem: 25048K used, 4872K free, 0K shrd, 1904K buff, 5988K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 100% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.07 0.07 0.02 2/30 27755
PID PPID USER STAT VSZ %MEM %CPU COMMAND
1053 1 root S 6476 21.5 0.0 httpd -p 80
1075 1 root S 1884 6.2 0.0 httpd -S
...
Next day, the packet loss begins. Looks like httpd leaking it is.
Mem: 26692K used, 3228K free, 0K shrd, 1904K buff, 5996K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 100% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.06 0.02 0.00 1/30 10475
PID PPID USER STAT VSZ %MEM %CPU COMMAND
1053 1 root S 6896 22.9 0.0 httpd -p 80
My Packet loss begins after only 10 min of flashing DD-WRT .
Looks like there is no solution in the near future unless the Guys in DD-WRT start using the proper Atheros driver ,check their forums and you will notice that it is a common problem .
I am realy disappointed with all this crappy thing ,my only reason of buying a Buffalo router is to use DD-WRT after they officialy released DD-WRT firmware for their products .
Probably I should go back to my trusted Pfsense router .
Same experience. Some notes on what's going on (using 14512)
First off, it's intermittent packet loss across the board. It doesn't show up as readily in web surfing but I wouldn't expect it to. Packet loss tends to be noticable in surfing to your average user around the 30-50% loss mark. It's not that high. But I play games on my router and those require constant streams of traffic or you get noticable jerking and sometimes dropped audio from other players.
>ping -t yahoo.comPinging yahoo.com [67.195.160.76] with 32 bytes of data:Reply from 67.195.160.76: bytes=32 time=45ms TTL=46Reply from 67.195.160.76: bytes=32 time=54ms TTL=46Reply from 67.195.160.76: bytes=32 time=46ms TTL=46Reply from 67.195.160.76: bytes=32 time=45ms TTL=46Reply from 67.195.160.76: bytes=32 time=45ms TTL=46Request timed out.Request timed out.Request timed out.Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Reply from 67.195.160.76: bytes=32 time=47ms TTL=46Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Request timed out.Request timed out.Reply from 67.195.160.76: bytes=32 time=46ms TTL=46Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Reply from 67.195.160.76: bytes=32 time=45ms TTL=46Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Reply from 67.195.160.76: bytes=32 time=47ms TTL=46Reply from 67.195.160.76: bytes=32 time=47ms TTL=46Reply from 67.195.160.76: bytes=32 time=45ms TTL=46Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Reply from 67.195.160.76: bytes=32 time=51ms TTL=46Reply from 67.195.160.76: bytes=32 time=53ms TTL=46Reply from 67.195.160.76: bytes=32 time=48ms TTL=46Reply from 67.195.160.76: bytes=32 time=47ms TTL=46Reply from 67.195.160.76: bytes=32 time=49ms TTL=46Request timed out.Reply from 67.195.160.76: bytes=32 time=46ms TTL=46Reply from 67.195.160.76: bytes=32 time=44ms TTL=46Ping statistics for 67.195.160.76: Packets: Sent = 29, Received = 23, Lost = 6 (20% loss),Approximate round trip times in milli-seconds: Minimum = 44ms, Maximum = 54ms, Average = 46ms
Second, this is not a wireless issue. I'm on an ethernet port.
Third, there seems to be a related problem with the router under Buffalo's DD-WRT. Sometimes, after a reboot, the router is horribly slow in routing. In fact, looking at this now, I believe that in those cases where the router was nearly unresponsive, the packet loss was probably thought the roof. I'd sometimes get a complete page but, more often than not, I'd time out. A reboot fixed it most of the time.
I have a hypothesis but I'm not able to test it at present (I have it running and stable on 1.82). If someone finds this thread and you're using the Buffalo DD-WRT (not the one from DD-WRT itself) try this
Look on the back of your router (where the Ethernet ports are). There is a small switch at the end by the antennas labeled Router. It has Auto, Off and On. By default it's shipped on Auto (which, as I've come to find, is a bad thing). Using the Buffalo stock firmware this switch in Auto tells the router to figure out what kind of network it's on. Apparently it's rather stupid because I couldn't get it to work AT ALL with it set to that. By setting it to On I was able to specify what kind of network I'm using (for some reason all the Buffalo software is fixated on PPPoE and couldn't figure out I was on DHCP). In theory this shouldn't matter to DD-WRT but if it fixed the stock firmware I wonder if it would interfere with DD-WRT.
Just a thought.
I agree!
I just installed one and initially, it would barely connect. Based on another post I saw somewhere, I flipped the switch from AUTO to ON and things have gotten significantly better. There is still some packet loss, but generally much more tolerable.
When will be the packet loss issue fixed? When should we expect the next Buffalo branded DD-WRT firmware that will work without any issues? The only reason that I bought Buffalo was because of DD-WRT ...I start to regret my choice ...
When a new firmware update is posted it will be posted. The firmware is written by a 3rd party (DD-WRT) so we don't have control of when they're going to address the issues we submit.
Hello, to avoid creating one more thread i've decided to post in this one.
Like OP, i'm also having packet loss problem with WHR-HP-G300N i've purchased two months or so ago.
It came preloaded with svn revision-14512 DD-WRT software. After being left to run for a day or so, it started to make a noticeable packet loss. I tried to do some research on the intertubes and found out that upgrading to the latest (14998) solved this problem in many cases. It did help, but it did not solve the problem completely. Now the packet loss problem occurs, but at noticeably longer intervals, it had worked for me for 8 days without any problem, and it has als occured on the second day. So far i haven't noticed any correlation between packet loss issue (it always starts suddenly and noticeably) and my network usage, although higher network usage usually causes the problem to occur faster. I will try to switch to user-friendly firmware, but the main reason why i bought this one particular router was because of the DD-WRT software and it's abilities.
The packet loss occurs on all outside traffic, irrelevantly of the site i'm pinging, and it occurs directly after the router and ceases immediately after i reboot it (either by plugging it off and on by pulling the power plug or via web-interface "reboot" button) and usually is at 25-35% all across the path in traceroute diagram (using PingPlotter free version). Also replacing with my old router (which has its own problems, but packet loss isn't one of them) immediately solves the problem too.
I'd like to know, whether buffalo's (and/or DD-WRT's) developers are aware of this problem and whether they are doing something to fix this issue?
Thank you in advance.
I was able to fix this by changing the IP filter settings on the Admin Tab to:
No more packet loss!
I'm giving this a shot, too.
I was hitting 30-40% packet loss after about a week through my G300N (running the dd-wrt 14998 build) and was absolutely convinced that the issue was with Comcast until I tried a direct connection. Wireless and ethernet connections were equally hosed until I rebooted the buffalo, something I should have tried first.
In any case, I set a weekly scheduled reboot for the wee hours of Sunday morning to see if I can't keep it at bay. I'll go daily if I have to.
I gave the user-friendly FW (1.81) a shot, but a) couldn't pull off some of the port-forwarding/NAT loopback I need and b) couldn't figure out a way to configure wireless-N correctly. All the settings I tried consistently showed 54M/s with inssider. As soon as I put dd-wrt back on, boom, 1 channel + extension channel, just like I want. Very odd.The dd-wrt UI is a hell of a lot cleaner, too, though I much prefer the level of logging in the user-friendly version.
OK, I've had timeouts when pinging yahoo and google while using this router. It hasn't really affected my PC gaming much (if at all), so I've ignored it. But I recently started playing MAG on PS3 and it's been giving me huge issues with disconnects.
I have the router running in wifi-N, 20GHz, and channel was set to "auto". After changing the channel to a randomly-chosen number (7), I no longer have timeouts when pinging IPs. I don't even USE the wifi (it's there for my sister's laptop), but changing the wifi broadcast channel to static FIXED my timeouts on wired connections. How odd.
ping www.yahoo.com -t
Pinging any-fp.wa1.b.yahoo.com [67.195.160.76] with 32 bytes of data:
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=44ms TTL=54
Reply from 67.195.160.76: bytes=32 time=54ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=46ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=41ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=41ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=43ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=41ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=46ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=41ms TTL=54
Reply from 67.195.160.76: bytes=32 time=38ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
Reply from 67.195.160.76: bytes=32 time=39ms TTL=54
Reply from 67.195.160.76: bytes=32 time=40ms TTL=54
For whatever it's worth, I'm switching back to the user-friendly FW (1.82) for awhile. The oddball packet loss stuff was happening again on a more or less random basis with the 14998 build, and I got tired of having to power cycle the thing to clear it up. I managed to get the port forwarding/NAT stuff working as I need it to (NAT loopback turned out not to be a hard and fast requirement), PPTP is functioning and I'm finally seeing 300Mb/s wireless speeds.
I like the dd-wrt UI, plus a few of the management tools, but as a home-office worker, I have to have a rock-solid connection. As I mentioned, I prefer the logging of the usr-friendly stuff anyway. I'll give UF a run for a couple of weeks and see how it goes.
I was watching something similar here on a WHR-HP-GN (DD-WRT 14998)
The channel was constantly changing and the clients were getting disconnected.
Hi Qinby,
Just curious... how is your experience with the UF 1.82 firmware on the WRH-HP-G300N? I have the stock V24-SP2 build 14998 firmware and feel that wireless access is somewhat slow and has a low signal strength.
Thank you in advance for your reply.
Jon
Jon -
Sorry for the delay. My experience has been just fine. The connection to my ISP has been rock-solid, and am consistently getting 300M/s wireless speeds. The only issue I've run into is that, occasionally, various devices (my iPad) need to manually reconnect/reauthenticate with the password. I've adjusted the wireless encryption settings a little bit to see if that makes a difference. Otherwise, it's been great. I might be willing to give the dd-wrt build another shot, but not anytime soon and certainly not until/unless I see feedback that the performance issues have been ironed out. YMMV, of course, but I've been been happy with the UF firmware.
Something is seriously wrong with these devices/firmware. I purchased 4 of these units.. All 4 of them exibit the same problem as described.
Spent over 8 hours on the phone with support, purchased a spectrum analyzer and found nothing to cause an issue with wireless channels.
Even tried to remidy using this thread:
This did not solve the issue either.
Here is what I have found.
When I do a factory reset the unit works perfect.
However this is less than satisfactory as this has DHCP enabled and is setup with the wrong Subnet than my network.
I simply want to make this a wireless access point.
I've also experienced severe packet loss with this router and the provided DD-WRT firmware (May 2011 build). Extremely disappointed. I've flashed the "user-friendly" firmware and I'm hoping that helps.