On Fri, Mar 25, 2022 at 8:25 PM Ed Greshko <ed.gres...@greshko.com> wrote:
> On 26/03/2022 10:29, Jack Craig wrote: > > > > > > > > i have a networking mystery ; i hope someone might give me a clue. > > > > i am working to restore a web server to internet access that is failing > after att update > > the att older modem (pace 5238ac) with arris BGW210-700. > > > > i have a static ip from att in the range 108.220.213.0/255.255.255.248 < > http://108.220.213.0/255.255.255.248>, 108.220.213.121 is the external ip > for the server. > > > > the bgw210-700 is the primary router/modem and is connected to a 3rd > party router, netgear nighthawk, > > > > the internal 10.0.0.0/ <http://10.0.0.0/> connects to the netgear > nighthawk > > > > ATT's broadband configuration is > > > > Blackhole-ATT (wireless name) > > > > Broadband connection source DSL > > Broadband connection up > > Broadband network type lightspeed > > Broadband ipv4 address 108.90.204.76 > > Broadband gateway address 108.90.204.1 > > > > > > outbound packets from the server (WS), are routed from the 10.0.0.1 > nighthawk to the ATT router to the internet. > > > > the 108.90.204.0 network routing from the att router to the att's > gateway. .76 is the router, .1 is the GW. > > > > 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 > > > Sounds like 108.90.204.76 is missing routes. I'm assuming that > 108.220.213.121 previously answered pings > and originally was the final destination of an external traceroute. > i was not seeing a way to add att rtr to have new routes. > > [egreshko@meimei ~]$ traceroute 108.220.213.121 > traceroute to 108.220.213.121 (108.220.213.121), 30 hops max, 60 byte > packets > 1 _gateway (192.168.1.1) 0.434 ms 0.728 ms 0.681 ms > 2 * * * > 3 tpdt-3308.hinet.net (168.95.82.198) 23.574 ms 23.530 ms 23.451 ms > 4 tpdb-3031.hinet.net (220.128.1.102) 7.827 ms > 220-128-1-50.hinet-ip.hinet.net (220.128.1.50) 7.210 ms > tpdt-3032.hinet.net (220.128.27.94) 7.386 ms > 5 r4102-s2.tp.hinet.net (220.128.7.69) 7.123 ms r4102-s2.tp.hinet.net > (220.128.14.93) 7.296 ms r4102-s2.tp.hinet.net (220.128.13.93) 7.252 ms > 6 r4002-s2.tp.hinet.net (220.128.6.85) 7.538 ms r4002-s2.tp.hinet.net > (220.128.6.81) 6.710 ms 6.656 ms > 7 pa-r32.us.hinet.net (202.39.91.29) 133.962 ms 132.083 ms 132.075 ms > 8 32.141.85.13 (32.141.85.13) 133.458 ms 133.358 ms 133.297 ms > 9 12.123.242.38 (12.123.242.38) 138.066 ms 137.303 ms 139.959 ms > 10 12.122.149.225 (12.122.149.225) 143.022 ms 137.567 ms 137.573 ms > 11 12.122.158.25 (12.122.158.25) 138.446 ms 137.435 ms 138.346 ms > 12 * * * > 13 99.134.39.24 (99.134.39.24) 136.686 ms 136.506 ms * > 14 99.134.39.11 (99.134.39.11) 136.191 ms 136.211 ms 136.066 ms > 15 99.161.44.77 (99.161.44.77) 137.461 ms 137.438 ms 138.025 ms > 16 108-90-204-76.lightspeed.mtryca.sbcglobal.net (108.90.204.76) 157.627 > ms 157.580 ms 157.980 ms > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > Remember if a server that should be visible externally, but isn't. Then > outbound requests/replies will also fail. > my server is pingable at 10.0.0.101 & 108.220.213.121. this with & without firewalld > > -- > Did 황준호 die? > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 >
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
