I think the problem here is that the public IP address is not one of the router's interface IP address but rather the IP address of the other device that receives the fibre connection (I think that one is called openreach). I also tried on another protocol than http and another port than 80 in case this was causing a problem due to the admin interface of the router, but same issue with ssh, the query times out when reaching for my public IP from inside the network. But none of them have needed NAT Loopback so Ive never had to. This allows Squad servers to be hosted and played. Hello everyone Ive set up several Edgerouters for my clients, and theyve been rock solid. The Plex KB indicates that this has to be enabled to work with SONOS, enables sonos to access Plex from inside the network, while still allowing PLEX to work outside the house. NAT loopback, aka Hairpinning, is a communication configuration that allows an IP to be mapped internally. How do I get NAT Loopback to work on the AX6000 (this is when you can access your port-forwarded ('virtual') servers from within the network - contacting will get you to the computer set up as the web server, even from inside your local network) With my previous Archer router, I had to disable 'NAT Booster' and it all worked. I have already established that DNS resolution works as I'm getting my public IP back from the name resolution, what isn't working is the routing of the query through the router. KB says the R8900 supports NAT Loopback but that is all it say nothing about setting it up. There's only 2 things that can go wrong, DNS resolution and routing. You can add a loopback NAT to your Cisco router, so that when going to the public address, it never gets to the ZTE: iptables -t nat -A PREROUTING -i br0 -s 192.168.2.0/24 -d -p tcp -dport 80 -j DNAT -to-destination 192.168.2.x This is prerouting, so the first step.host) recives the forwarded packet it answers to its own loopback device. Am not using DNS, to test the NAT loopback, I am entering my public IP address in the browser, does it work for you when entering the IP address rather than server name. 8 NAT Port: 80 The corresponding firewall rule on WAN should pass tcp port 80.
0 Comments
Leave a Reply. |