Re: 60+% ping packet loss on Pi3 under -current and stable-13

In reply to: Mark Millard : "Re: 60+% ping packet loss on Pi3 under -current and stable-13"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: bob prohaska <fbsd_at_www.zefox.net>
Date: Tue, 03 May 2022 02:34:45 UTC
On Mon, May 02, 2022 at 11:45:21AM -0700, Mark Millard wrote:
> I just saw something odd when trying to test again.
> 
> I did not manage to capture the earlier display updates
> but when it first connected it had a list of "(waiting
> for reply)" lines from 17. to 27. with www.zefox.org
> at 28. That range got shorter in steps but fairly
> rapidly. Before the 18. to 28. showed up it sat at
> 17. (waiting for reply) for a while.
> 
> I finally captured it with www.zefox.org at 20. :
> 
>                                      My traceroute  [v0.95]
> amd64_ZFS (192.168.1.120) -> www.zefox.org (50.1.20.28)                2022-05-02T11:36:06-0700
> Keys:  Help   Display mode   Restart statistics   Order of fields   quit
>                                                        Packets               Pings
>  Host                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
>  1. 192.168.1.1                                       0.0%    30    0.2   0.8   0.2   1.5   0.4
>  2. 172.30.26.66                                      0.0%    30   69.5  70.0  42.1 138.0  19.7
>  3. 68.85.243.77                                      0.0%    30   38.8  49.3  38.8  61.5   6.7
>  4. 24.124.129.106                                    0.0%    30   64.0  52.2  10.1 109.4  14.7
>  5. 96.216.60.165                                     0.0%    30   62.6  47.6  17.3  62.6  12.0
>  6. 68.85.243.197                                     0.0%    29   66.9  55.0  28.4  78.3  10.5
>  7. be-36241-cs04.seattle.wa.ibone.comcast.net        0.0%    29   68.9  57.8  28.6 122.3  14.9
>  8. be-2412-pe12.seattle.wa.ibone.comcast.net         0.0%    29   65.7  57.8  49.5 120.7  13.5
>  9. (waiting for reply)
> 10. be2075.ccr21.sfo01.atlas.cogentco.com             0.0%    29   78.6  74.3  63.7 135.2  15.4
> 11. be2379.ccr31.sjc04.atlas.cogentco.com             0.0%    29   83.0  74.0  62.1 153.8  20.6
> 12. 38.104.141.82                                     0.0%    29  106.6  78.3  62.0 168.3  25.7
> 13. 0.xe-0-3-0.scrm-gw1.scrmca01.sonic.net            0.0%    29   83.7  73.4  58.9 134.8  13.5
> 14. 0.xe-0-0-0.cr1.scrmca13.sonic.net                 0.0%    29   60.6  72.0  50.8 135.6  14.3
> 15. gig1-1-1.gw.wscrca11.sonic.net                    0.0%    29  104.8  75.1  44.2 136.7  18.8
> 16. gig1-1-1.gw.davsca11.sonic.net                    0.0%    29   85.4  73.8  48.2 136.3  14.4
> 17. (waiting for reply)
> 18. (waiting for reply)
> 19. (waiting for reply)
> 20. www.zefox.org                                    86.2%    29  160.4 144.9 102.1 160.5  28.6
> 
> www.zefox.org ended up at 17. and stayed there
> once it got there.
> 
> I've no clue if this observation is of any use.
> 

It's consistent with my observations of keyboard interaction vis ssh.
Input sometimes stop echoing for tens of seconds, then all goes through
after the pause. Maybe this really has little or nothing to do with the
network, it's just that all my interaction with the two machines is via
the network. Neither has had a console and keyboard since I got the Pi4.

Thanks for bringing your observations to the discussion!

bob prohaska