I'm wondering if you're worrying about routing when you should be worrying about the port forward. Routing: can the server ping, say, 1.1.1.1? Can other hosts at various points on your LAN? If so, your routes are just fine. Also, where are your NAT points? There has to be one on the innermost box with a public address, but is there one between your 10. and 192. networks? Hopefully the public router is the only thing doing NAT. Port forward: have you inspected the inbound port forward settings on the router (the box with the public IP address, I've lost track). You need one mapping inbound TCP to ws-public-address:443 to ws-lan-address:443. Can you run a tcpdump on one of the routers in the chain to see what happens? My local firewall's a UNIX box so I can do this there to watch any traffic between an internal host and the outer world. ANd of course what others have been saying: traceroute does not tell you everything: various nodes may not respond as needed, and it certainly will not be passed through to your WS server inless the inbound rule is wide open (all traffic types), which would be a bad thing. Cheers, Cameron Simpson <cs@xxxxxxxxxx> _______________________________________________ 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
