On Fri, Jul 24, 2026 at 10:13 PM David Schwartz via PLUG-discuss < [email protected]> wrote:
> I just tried a traceroute to my previous host and got the same problem: > > > traceroute webhostingworld.net > traceroute to webhostingworld.net (184.154.212.196), 64 hops max, 40 byte > packets > 1 192.168.0.1 (192.168.0.1) 1.395 ms 1.158 ms 0.898 ms > 2 ip70-171-233-2.tc.ph.cox.net (70.171.233.2) 2.793 ms 2.995 ms > ip70-171-233-3.tc.ph.cox.net (70.171.233.3) 1.739 ms > 3 100.120.101.106 (100.120.101.106) 4.021 ms 3.672 ms 3.059 ms > 4 100.120.100.80 (100.120.100.80) 2.645 ms 1.301 ms 2.070 ms > 5 * * * > 6 * * * > 7 *^C > /Users/thetoolwiz > > > It’s the steps in between, and the fact that one particular IP, 100.120.100.80 [1], seems to be blocking traffic. but your traceroute shows the 100.x.x.x devices responded so why do you think they are blocking your ip traffic? [1] The 100.x.y.z is CGNAT (Carrier Grade NAT) i.e. private IP space for ISPs, Global scale network infrastructure providers (Tailscale) etc. I have found 'traceroute' not that useful - not because it is a bad tool but because many nodes in the path do not respond and it fails. Try tcptraceroute / tcptraceroute6 to your destination host and port e.g. ' www.example.org 443' Let us know what you discover as the root cause of the intermittent failures -- Arun Khan
--------------------------------------------------- PLUG-discuss mailing list: [email protected] To subscribe, unsubscribe, or to change your mail settings: https://lists.phxlinux.org/mailman/listinfo/plug-discuss
