* Jason Iannone
But the clever budget conscious among us have deployed router links
over provided MPLS based L2 services as critical infrastructure. We
have an invisible WAN. In the absence of L1 PM statistics, how do we
validate service over other networks? 802.3ag and y.1731 attempt to
answe
no issues here in Houston on gpon from 397412.
3356 has been doing an insane amount of icmp and traceroute filtering on their
routers as of late, but the resolver IPs continue to respond with no issues.
Based on RTT I assume I am going up to Dallas... may be an issue with the
resolvers that are
Seems like these IPs not responding to ping is not unusual, as per
https://www.reddit.com/r/sysadmin/comments/11syv2e/google_dns__dropping_pings_like_crazy_today/
"Google has stated multiple times before as has Level3/CenturyLink/Lumen
that 4.2.2.1 and 8.8.8.8 should not be used for ping check
Dan,
Thanks! I had never read that before. But that makes sense.
-mel
On Jan 12, 2025, at 8:22 PM, Daniel Sterling wrote:
Seems like these IPs not responding to ping is not unusual, as per
https://www.reddit.com/r/sysadmin/comments/11syv2e/google_dns__dropping_pings_like_crazy_today/
Working from ATT route server
rvi...@route-server.ip.att.net> ping 4.2.2.1
PING 4.2.2.1 (4.2.2.1): 56 data bytes
64 bytes from 4.2.2.1: icmp_seq=0 ttl=54 time=8.661 ms
64 bytes from 4.2.2.1: icmp_seq=1 ttl=54 time=9.291 ms
64 bytes from 4.2.2.1: icmp_seq=2 ttl=54 time=9.401 ms
^C
--- 4.2.2.1 p
I noticed that Level3 open DNS 4.2.2.1 and 4.2.2.2 stopped responding to ping
today. They are responding to DNS queries however.
Does anyone know if this filtering is going to be permanent?
-mel beckman
O:\>ping 4.2.2.1
Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=44ms TTL=56
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=38ms TTL=56
Ping statistics for 4.2.2.1:
Packets: Sent = 4, Recei
Hi
I have a few passes for the upcoming NANOG meeting left, in which I would
like to share with people who might need assistance to attend meetings(i.e
students, academic or non profit), PM me if you are one of those people.
--
--
Kind regards.
Lu
Still not pinging from Frontier, Lumen, AT&T, or Verizon networks
-mel
On Jan 12, 2025, at 4:13 PM, Jerry Cloe wrote:
O:\>ping 4.2.2.1
Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=36ms TTL=56
Reply from 4.2.2.1: bytes=32 time=44ms TTL=56
Reply from 4.2.2.1: byte
9 matches
Mail list logo
