If I'm reading this thread correctly, your original setup was as follows: ----- - 108.90.204.76/24 -> gw: 108.90.204.1 / arris BGW210-700 \ - 192.168.1.254/24 (Blackhole-ATT WiFi network) - 108.220.213.126/29 - 108.220.213.121/29 -> gw: 108.220.213.126 / netgear nighthawk \ - 10.0.0.1/24 - 10.0.0.101/24 -> gw: 10.0.0.1 / ws.linuxlighthouse.com ----- That configuration is completely reasonable. You shouldn't need to try to use bridge mode, or IP Passthrough, or any other rewiring of the network. > 10.0.0.101 ws.linuxlighthouse.com (internal IP) 2 packets transmitted, 2 received, 0% packet loss, time 1033ms You initially provided some address ping information, but didn't specify which device was gathering that information. That may be relevant information, because only a device in the 10.0.0.0/24 network should have been able to reach all of those addresses. I'm assuming that the information was gathered from within 10.0.0.0/24. > consider the below traceroute, it reports hops up to 108.90.204.76, stopping there instead of doing one more hop For problems of this sort, I generally consider several possibilities: 1: The Arris firewall is not allowing traffic into your network from the public. 2: The Netgear firewall is not allowing ICMP (ping) from the public. 3: The Netgear is configured to redirect (forward) 108.220.213.121 to your server, but the NAT isn't working correctly. 4: Your Arris modem and Nighthawk router both have addresses in 108.220.213.120/29 set up, but ATT isn't routing that network to you, and outbound traffic is NATed by the Arris modem. I think we can discount #1 and #4, since we can ping 108.220.213.126 from the public, but we can also test those things: You should be able to connect a laptop directly to the Arris modem, and configure the laptop with the IP address 108.220.213.122, netmask 255.255.255.248, gateway 108.220.213.126. (DNS: 8.8.8.8 if you don't have another preference.) Once connected, the laptop should have public internet access. You should be able to access https://www.whatismyip.com/, and your public IPv4 address as seen by that page should be 108.220.213.122. Someone outside of your network should be able to ping and traceroute to that address. #2 and #3 are harder to test, but if you can verify that another device is fully functional on another address, then you can at least focus your attention on the Nighthawk configuration. At that point, I'd turn off any IP forwarding or DNAT settings you'd configured on the Nighthawk, and try to turn off the firewall. With the firewall off, you should be able to ping and tracroute to the Nighthawk from outside. Next you can try to get any port forwards working, and finally you can turn the firewall back on and see if NAT still works. _______________________________________________ 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
