Interesting-
I also have a wzr-hp-g300nh which doesn't appear to have any problem when
using it, but has lots of drops on the bridge

[email protected]:~# uptime
 10:37:20 up 54 days,  4:18,  load average: 0.00, 0.01, 0.04

 ATTITUDE ADJUSTMENT (bleeding edge, r29844) ----------
[email protected]:~# dmesg | grep -i wzr
[    0.000000] Kernel command line:  board=WZR-HP-G300NH
console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.090000] MIPS: machine is Buffalo WZR-HP-G300NH
[email protected]:~#


[email protected]:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:1D:73:B4:A9:3B
          inet addr:192.168.15.254  Bcast:192.168.15.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:55750098 errors:0 dropped:2566262 overruns:0 frame:0
          TX packets:137978578 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5050975487 (4.7 GiB)  TX bytes:199036431689 (185.3 GiB)


however not on any physical devices:
[email protected]:~# ifconfig | grep dropped
          RX packets:55750270 errors:0 dropped:2566350 overruns:0 frame:0
<-- br-lan -->
          TX packets:137978585 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:49758824 errors:0 dropped:8 overruns:92496 frame:0
          TX packets:128751680 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:49758611 errors:0 dropped:0 overruns:0 frame:0
          TX packets:128751679 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:158955224 errors:0 dropped:1 overruns:0 frame:0
          TX packets:49567093 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:275 errors:0 dropped:0 overruns:0 frame:0
          TX packets:275 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:32941 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          RX packets:23258608 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32326640 errors:0 dropped:0 overruns:0 carrier:0
[email protected]:~#


it would be interesting to know why these packets are dropping.





On Tue, Nov 19, 2013 at 9:40 AM, Ben West <[email protected]> wrote:

> FWIW, I run Attitude Adjustment on 2 wzr-hp-g300nh2's and on one
> wzr-hp-g300nh, not the same but similar to your device.
>
> The wzr-hp-g300nh does indeed show a large quantity of packet drops on its
> internal LAN, and I've found no root cause.  Likewise, I stopped using the
> unit's wifi interface entirely (in lieu of just using wired routing), due
> to wifi traffic periodically causing the internal LAN, both wired and
> wireless, to randomly freeze for 30 seconds.
>
> On the wzr-hp-g300hn:
>
> root@bluenoses:~# ifconfig
> br-lan    Link encap:Ethernet  HWaddr 00:24:A5:XX:XX:XX
>           inet addr:192.168.30.1  Bcast:192.168.30.255  Mask:255.255.255.0
>           inet6 addr: .../64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3858492 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3750366 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1601390703 (1.4 GiB)  TX bytes:2301356709 (2.1 GiB)
>
> eth0      Link encap:Ethernet  HWaddr 00:24:A5:XX:XX:XX
>           inet6 addr: .../64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3875718 errors:0 dropped:17064 overruns:61354 frame:0
>           TX packets:3750374 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1671882526 (1.5 GiB)  TX bytes:2316359834 (2.1 GiB)
>           Interrupt:4
>
> eth0.1    Link encap:Ethernet  HWaddr 00:24:A5:XX:XX:XX
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3858492 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3750366 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1601390703 (1.4 GiB)  TX bytes:2301356709 (2.1 GiB)
>
> eth1      Link encap:Ethernet  HWaddr 00:24:A5:XX:XX:XY
>           inet addr:XXX.XXX.XXX.XXX  Bcast:96.35.187.123
> Mask:255.255.255.252
>           inet6 addr: .../64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:3752454 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:3822563 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:5
>           RX bytes:2302722406 (2.1 GiB)  TX bytes:1648496594 (1.5 GiB)
>           Interrupt:5
> ...
>
> root@bluenoses:~# cat /etc/openwrt_release
> DISTRIB_ID="OpenWrt"
> DISTRIB_RELEASE="Attitude Adjustment"
> DISTRIB_REVISION="r36528"
> DISTRIB_CODENAME="attitude_adjustment"
> DISTRIB_TARGET="ar71xx/generic"
> DISTRIB_DESCRIPTION="OpenWrt Attitude Adjustment 12.09"
>
> My guess is that the wzr-hp-g300nh is defective, and/or OpenWRT support
> for it is not 100%.  The packet loss is not adversely affecting my usage,
> and I will replace the unit with something else when opportunity allows.
>
> On Tue, Nov 19, 2013 at 11:22 AM, camden lindsay <
> [email protected]> wrote:
>
>> Hello-
>> I recently had a problem with a router, and found it to most likely be
>> the hardware
>>
>> Long story short, i copied the image from that router  (dd /dev/mtdblock5
>> then mtd write) directly onto an identical router and the problems did not
>> follow - which indcate hardware was most likely the problem.
>>
>> I recently was struggling with wifi stability issues on my wzr-hp-ag300h.
>>  Before a software update, it was pretty bad, then after upgrading to trunk
>> it was mostly unusable.
>>
>>  I updated to trunk because I knew a lot of driver advancement had been
>> made, and was hoping it would help my wireless problems.
>>
>> After hours of troubleshooting, I started looking at wireshark, and saw a
>> lot of [TCP ACKed unseen segment], [TCP Previous segment not
>> captured], [TCP ACKed unseen segment], [TCP Dup ACK 61#1] and [TCP
>> Out-Of-Order] that would imply large amounts of packet loss.
>>
>> A check with MTR indicated icmp loss to a machine on my local wired
>> network, the loss coming and going but averaging 20-35% over 160 pings or
>> so.
>>
>> This occured on both 2.4 and 5.2 GHz.  On this device, I believe they are
>> physically different chips.
>>
>> No usual logs showed up in dmesg or syslog.
>>
>> I don't remember the interface statistics showing anything that seemed
>> wonky (unusual number of errors/packets marked as dropped/etc).
>>
>> I'd like to learn more how to look into what may be causing this issue.
>>
>> Is there any kind of additional debugging people can recommend?
>>
>> thank you
>> Camden
>>
>>
>> _______________________________________________
>> openwrt-users mailing list
>> [email protected]
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>>
>>
>
>
> --
> Ben West
> http://gowasabi.net
> [email protected]
> 314-246-9434
>
> _______________________________________________
> openwrt-users mailing list
> [email protected]
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>
>
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to