On Fri, Mar 25, 2022 at 8:16 PM Samuel Sieb <samuel@xxxxxxxx> wrote:
On 3/25/22 19:29, Jack Craig wrote:
> i have a networking mystery ; i hope someone might give me a clue.
>
> sample route, ...
>
> 10.0.0.101 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com>
> (internal IP) 2 packets transmitted, 2 received, 0% packet loss, time 1033ms
> 10.0.0.1 Blackhole-NH
> 2 packets transmitted, 2 received, 0% packet loss, time 1018ms
> 192.168.1.254 Blackhole-ATT 2
> packets transmitted, 2 received, 0% packet loss, time 1001ms
> 108.90.204.76 att subnet (local router) 2 packets
> transmitted, 2 received, 0% packet loss, time 1002ms
> 108.90.204.1 att subnet (remote GW) 2 packets
> transmitted, 2 received, 0% packet loss, time 1001ms
> 108.220.213.121 ws.linuxlighthouse.com <http://ws.linuxlighthouse.com>
> (public IP) 2 packets transmitted, 2 received, 0% packet loss, time 1001ms
> 108.220.213.126 linuxlighthouse (public GW) 2 packets
> transmitted, 2 received, 0% packet loss, time 1001ms
>
> now the mystery. where 108.220.213.121 is a publicly visible ip for the
> server, a remote traceroute is wonky!!
>
> consider the below traceroute, it reports hops up to 108.90.204.76,
> stopping there instead of doing one more hop
>
>
> 1 <1 ms <1 ms <1 ms Linksys35675 [192.168.1.1]
> 2 9 ms 8 ms 17 ms 142-254-236-209.inf.spectrum.com
> <http://142-254-236-209.inf.spectrum.com> [142.254.236.209]
> 3 12 ms 10 ms 11 ms lag-63.tjngcaac01h.netops.charter.com
[snip]
> 15 44 ms 43 ms 43 ms
> 108-90-204-76.lightspeed.mtryca.sbcglobal.net
> <http://108-90-204-76.lightspeed.mtryca.sbcglobal.net> [108.90.204.76]
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19
>
> could anyone shed some light on this mystery??
Your question and description are very confusing. Can you try again
with the details more organized?
What are you trying to traceroute to at the end? The route in the
traceroute doesn't match the "route" from earlier. I don't understand
what you think should be after that last hop.
ISPs don't always let traceroute requests go through depending on which
method you're using.
i had a remote friend try traceroute to 108.220.213.121 to show the trace stopping at 108.90.204.76.
i dont know why it stops short of my server???
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
