Re: network mystery!!??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Sun, Mar 27, 2022 at 2:41 AM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Tim:
>> Your ISP may be ignoring pings, many other services in between, and
>> even your own router.

Jack Craig:
> but why can  i traceroute up to my side of the me<-->isp lan
> segment??

Because some of the equipment responds, others don't.  If you look back
at your first posting (repasted below), you'll see there's some in the
middle that don't respond, either.  They don't stop the connection
going through past them, they just don't respond to pings.

  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 [142.254.236.209]
  3    12 ms    10 ms    11 ms  lag-63.tjngcaac01h.netops.charter.com [24.30.172.49]
  4    14 ms    13 ms    13 ms  lag-29.lsaicaev01r.netops.charter.com [72.129.18.240]
  5    12 ms    14 ms    11 ms  lag-26.lsancarc01r.netops.charter.com [72.129.17.0]
  6    19 ms    13 ms    14 ms  lag-16.lsancarc0yw-bcr00.netops.charter.com [66.109.6.102]
  7    25 ms    37 ms    42 ms  lag-3.pr2.lax10.netops.charter.com [107.14.19.41]
  8    17 ms    17 ms    17 ms  192.205.32.253
  9    22 ms    21 ms    21 ms  cr1.la2ca.ip.att.net [12.122.128.102]
 10    24 ms    25 ms    25 ms  12.122.158.41
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    23 ms    21 ms    23 ms  99.134.39.15
 14    25 ms    24 ms    26 ms  99.161.44.79
 15    44 ms    43 ms    43 ms  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



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

When it comes to things close to you, working backwards, inside your
LAN you have your own private IPs.  Your router will have its inside IP
and an outside IP given to it by your ISP (those you can easily find
out).  What your router first connects to at your ISP may have your-
side and their-side IPs.  There will be routes going through the
internals of the ISP through to their supplier.  And then there's all
the interconnects to more of the web.

For pings, and more to the point, HTTP traffic to your webserver, they
have to get through all of that.  I think you're just going to have to
talk to your ISP about why HTTP traffic doesn't get through.

Though do look through your router's settings again.  There may be
firewall or privacy options that block things.  And you would need to
set up forwarding/routing rules go pass HTTP through it to your
webserver.  Some routers have a DMZ zone feature (demilitarised zone),
where all traffic you haven't specifically set a rule up for can be
forwarded through to a specific LAN IP, or to a ethernet specific
socket on the router.  Beware, though, it's unfiltered and unprotected
by any firewall.  All the gumph on the internet trying to connect to
you will be allowed through it.

the test to change the server ip partially works; that is the srvr can see the world, but my access to the rest of my internal 10.0.0.0 is not accessible.

if i ad the 10.0.0./24 route to the routing for 108.220.213.121 could i not then get to internal and external networks??
 
default via 10.0.0.1 dev eno1 proto static metric 100
10.0.0.0/24 dev eno1 proto kernel scope link src 10.0.0.101 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

 
 
--

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@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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux