I've got 100% loss here but there may be something wrong somewhere
between me and the gw.
$ ping -c 100 -I vlan4
ampr.org
PING
ampr.org (44.0.0.1) from 44.46.15.10 vlan4: 56(84) bytes of data.
---
ampr.org ping statistics ---
100 packets transmitted, 0 received, 100% packet loss, time 101360ms
$ traceroute -i vlan4
ampr.org
traceroute to
ampr.org (44.0.0.1), 30 hops max, 60 byte packets
1 _gateway (44.46.15.1) 0.427 ms 0.388 ms 8009.632 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
On 11/6/20 5:45 PM, David Ranch via 44Net wrote:
I'm seeing 15% from Santa Clara, CA via Comcast Business down to UC
San Diego
--- 44.0.0.1 ping statistics ---
1000 packets transmitted, 846 received, *15% packet loss*, time 200520ms
rtt min/avg/max/mdev = 19.072/22.797/40.139/3.214 ms, ipg/ewma
200.721/23.792 ms
--
traceroute 169.228.34.84
traceroute to 169.228.34.84 (169.228.34.84), 30 hops max, 60 byte packets
2 96.120.94.97 (96.120.94.97) 16.065 ms 16.077 ms 20.434 ms
3 96.110.176.141 (96.110.176.141) 21.641 ms 21.599 ms 21.343 ms
4
be-232-rar01.santaclara.ca.sfba.comcast.net (162.151.78.253)
19.330 ms 19.582 ms 24.987 ms
5
be-39941-cs04.sunnyvale.ca.ibone.comcast.net (96.110.41.125)
26.364 ms
be-39911-cs01.sunnyvale.ca.ibone.comcast.net
(96.110.41.113) 24.905 ms
be-39931-cs03.sunnyvale.ca.ibone.comcast.net (96.110.41.121) 26.310 ms
6
be-1112-cr12.sunnyvale.ca.ibone.comcast.net (96.110.46.6) 25.659
ms *
be-1412-cr12.sunnyvale.ca.ibone.comcast.net (96.110.46.42)
17.409 ms
7 96.110.37.174 (96.110.37.174) 17.942 ms
be-301-cr01.9greatoaks.ca.ibone.comcast.net (96.110.37.170) 15.461 ms
96.110.37.174 (96.110.37.174) 15.387 ms
8
be-2411-pe11.9greatoaks.ca.ibone.comcast.net (96.110.32.254)
20.786 ms 20.041 ms 20.388 ms
9
ae-3.2011.rtsw.sunn.net.internet2.edu (162.252.69.141) 18.312 ms
18.809 ms 25.495 ms
10 198.71.47.75 (198.71.47.75) 26.374 ms 25.800 ms 25.158 ms
11
dc-lax-agg8--svl-agg8--100ge--2.cenic.net (137.164.11.20) 30.269
ms
lax-agg8--svl-agg8-100g-3.cenic.net (137.164.11.66) 30.610 ms
dc-lax-agg8--svl-agg8--100ge--2.cenic.net (137.164.11.20) 34.686 ms
12
dc-tus-agg8--lax-agg8-300g.cenic.net (137.164.11.83) 35.342 ms
24.021 ms 28.403 ms
13
dc-sdg-agg4--tus-agg8-300g.cenic.net (137.164.11.85) 25.676 ms
29.705 ms 28.813 ms
14
dc-ucsd-100ge--sdg-agg4.cenic.net (137.164.23.177) 29.832 ms
29.120 ms 31.159 ms
15
nodeb-core--mx0-40ge.ucsd.edu (132.239.254.161) 28.595 ms 28.808
ms 28.229 ms
16
sdsc-7710-7--bcore-vl2996-p2p.ucsd.edu (132.239.255.54) 30.836 ms
31.062 ms 31.372 ms
--David
KI6ZHD
On 11/05/2020 06:14 PM, Albert Lawson via 44Net wrote:
Good Evening Folks,
Is something going on with the gateway...????? I just noticed this
today:
---
ampr.org ping statistics ---
92 packets transmitted, 72 received, 21% packet loss, time 91427ms
rtt min/avg/max/mdev = 33.320/41.448/51.167/2.890 ms
As opposed to:
---
aa6hf.ampr.org ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99146ms
rtt min/avg/max/mdev = 47.409/56.381/70.304/4.552 ms
Pings to my commercial IP (from my network at work) are 100%.....but
pings to
ampr.org (from my network at work) are showing dropped
packets as well.
73's
-Albert
WB7AWL
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net --
Matthew Chambers, CBT, NR0Q
Owner/Engineer
M Chambers Communications Engineering LLC
PO BOX 855, Moberly, MO 65270
Mobile (660)415-5620
www.mchambersradio.com <https://www.mchambersradio.com>
--
The content of this email is confidential and intended for the
recipient
specified in message only. It is strictly forbidden to share
any part of
this message with any third party, without a written consent
of the
sender. If you received this message by mistake, please reply to
this
message and follow with its deletion, so that we can ensure such a
mistake
does not occur in the future.
Please do not print this email unless it is
necessary. Every unprinted email helps the environment.