On Sat, Mar 26, 2022 at 9:08 PM Tim via users <users@lists.fedoraproject.org> wrote:
On Sat, 2022-03-26 at 11:22 -0700, Jack Craig wrote:
> 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???

Things only respond to pings if allowed to.  Thanks to continual
hacking attempts, many admins turn off features they don't need, or
feel that someone else may exploit.

Pings (as things like traceroute generally use) only prove that
something responds to pings, they don't prove whether HTTP access to a
webserver works or not.  Likewise for any other service running.

Your ISP may be ignoring pings, many other services in between, and
even your own router.
 
but why can  i traceroute up to my side of the me<-->isp lan segment??

the att rtr knows of the public ip, why doesnt it get used? the mystery so far.

--

uname -rsvp
Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64

Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure