NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Trouble with Port Forwarding on WNDR4300V2
WNDR4300V2 Firmware V1.0.0.56 I'm looking to connect a particular service that I'm running through a VM on a local FreeNAS box so I can manage it remotely. The service is working internally perfe...
> [...] I have noticed that my public IP address (71.78.X.X) which I can
> use various services look up (ping, nmap, google, etc.) is different
> from the IP address that is listed in the router (170.20.X.X), [...]Where "the IP address that is listed in the router" means the IP
address of the router's WAN/Internet interface (not its LAN interface)?"170.b.c.d" or "172.b.c.d"? (I'd bet on the latter; "170.20.c.d" is
a real-world address.) Whatever it really is, plug it into the form at:It appears that your ISP may be using carrier-grade NAT:
https://en.wikipedia.org/wiki/Carrier-grade_NAT
If so, then your router will not get a public WAN/Internet IP
address, and so you will not be able to make port forwarding work (from
the outside world).
The only solutions I know are: 1) to ask your ISP for a real public
address (for which they might charge more), or 2) to use a tunneling
service like the one mentioned in another thread (near the end):https://community.netgear.com/t5/x/x/m-p/1748431
On the bright side, with the possible exception of the "170 v. 172"
confusion, it's a rare treat around here to read a problem report which
includes a coherent, detailed problem description instead of a useless
mess. It's appreciated.
> [...] I have noticed that my public IP address (71.78.X.X) which I can
> use various services look up (ping, nmap, google, etc.) is different
> from the IP address that is listed in the router (170.20.X.X), [...]
Where "the IP address that is listed in the router" means the IP
address of the router's WAN/Internet interface (not its LAN interface)?
"170.b.c.d" or "172.b.c.d"? (I'd bet on the latter; "170.20.c.d" is
a real-world address.) Whatever it really is, plug it into the form at:
It appears that your ISP may be using carrier-grade NAT:
https://en.wikipedia.org/wiki/Carrier-grade_NAT
If so, then your router will not get a public WAN/Internet IP
address, and so you will not be able to make port forwarding work (from
the outside world).
The only solutions I know are: 1) to ask your ISP for a real public
address (for which they might charge more), or 2) to use a tunneling
service like the one mentioned in another thread (near the end):
https://community.netgear.com/t5/x/x/m-p/1748431
On the bright side, with the possible exception of the "170 v. 172"
confusion, it's a rare treat around here to read a problem report which
includes a coherent, detailed problem description instead of a useless
mess. It's appreciated.
Thank you for your comments.
I've been doing some research on Carrier Grade NAT and it does appear that path leads me to a dead-end. Prior to my DDNS route, I did contact my ISP and they do not provide Static IPs for accounts like mine. I may contact them further to see what other options they might offer I can better explain what I'm attempting to accomplish.
I will look at ngrok and see if that will be another path to take. Thanks for pointing out that prior thread.
I appreciate your kind comments about my description of my problem. As I've been learning more about working on servers and networks, it seems like that's the best way to get people to help you. The more information, the better the help.