Messages in this thread | | | Date | Fri, 13 Nov 2009 11:25:25 -0500 | Subject | Re: large packet loss take2 2.6.31.x | From | Caleb Cushing <> |
| |
> So I assume it's your only network device on this box and according > to these reports it's 192.168.1.3 with 192.168.1.1 as the gateway, > and your only change is kernel on this 192.168.1.3 box, right?
yes, and semi obviously that router is my box (LinkSys wrt 54gl openwrt kamikaze 8.09.1.
> Since the loss is seen on the first hop already, it seems it should be > enough to query 192.168.1.1 only - did you try this? If so, does this > happen from the beginning of the test or after many loops? Could you > try to repeat this wireshark dump with more data than before (but just > to be sure there are a few unanswered pings). If possible it would be > nice to have wireshark or tcpdump data from 192.168.1.1 too, while > pinged from 192.168.1.3. Please, send it gzipped to bugzilla only plus > ifconfig eth0 before and after the test (and let us know here).
same bug? or new bug? I can see what I can do to get a tcpdump from the router. yes I tried that, I can tell within the first 10 pings. I should say I don't notice it on every kernel boot, it's ~80% of reboots (but that's pulled from my behind). but I haven't noticed it on gfa31221 at all. it's reproducible in 31.6 too (arch just added that).
> Btw, mtr has text reporting too (--report). Larger things send to > bugzilla only.
didn't know that, although I should have guessed (or rtfm), thanks.
-- Caleb Cushing
http://xenoterracide.blogspot.com
| |