G0-13-2-4.LSANCA-LCR-21.verizon-gni.net not allowing some routes.

[prof256]

If any verizon employee reads this have your network techs look at this machine.

I can get through to 209.93.110.200 but 208.93.110.200, 208.93.111.200, 208.93.111.100 and so on are unreachible.

:~$ tracepath -n 208.93.111.100
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 6.193ms
1: 192.168.1.1 0.855ms
2: 108.38.109.1 5.815ms asymm 3
3: 100.41.199.224 11.855ms !N
Resume: pmtu 1500
:~$ tracepath -n 208.93.111.200
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 0.921ms
1: 192.168.1.1 0.854ms
2: 108.38.109.1 6.025ms asymm 3
3: 100.41.199.224 10.961ms !N
Resume: pmtu 1500
:~$ tracepath -n 208.93.110.200
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 1.047ms
1: 192.168.1.1 1.037ms
2: 108.38.109.1 5.315ms asymm 3
3: 100.41.199.224 10.972ms !N
Resume: pmtu 1500
:~$ tracepath -n 208.93.112.200
1?: [LOCALHOST] pmtu 1500
1: 192.168.1.1 0.930ms
1: 192.168.1.1 0.854ms
2: 108.38.109.1 6.392ms asymm 3
3: 100.41.199.224 10.969ms
4: 130.81.199.38 9.479ms
^C

[Hubrisnxs]

Those two routers look like they are configured to deprioritize ICMP Pings. 

 

Do you have trace results, where traffic is not passing through them and onto other machines/networks?

 

 

[prof256]

Hubrisnxs,

   Thanks for the reply. It appears the machine has updated its routing table either by its self or by human intervention.

Prof256

P.S. Traceroute and Tracepath use UDP not ICMP (At least on linux environment) so that we get information from machines blocking ICMP. On Tracepath a line ending with "!N" indicates "network not reachable".  The line with !N is the end of all traffic going thought on that route.

[Hubrisnxs]

Great, glad it's working. and thank you for the info,  I do not play with Linux, so I was trying to relate that to what I normally see in an ms dos trace. 

I appreciate it, and have a good weekend out there.