Reply

Re: Trouble with Port Forwarding on WNDR4300V2

aweissmeister
Aspirant

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 perfectly. This is my first time doing any sort of port forwarding so I'm in a new space and willing to learn. 

 

I've created a no-ip.com account (not a mynetgear.com account) and have connected to my router. I've confirmed that when I ping redacted.ddns.net, the correct public IP address appears. When I visit that address in a browser, I get the result in the attached image.

 

However, 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), which is of course different from my local network in which I use for my various VMs (192.168.X.X).

 

When I visit 170.20.X.X:9000 I do indeed get the service and I am able to login and use it as expected. So now I'm just way confused. The IP address that no-ip.com and the rest of the world sees is one  thing, and the IP address the router displays is another, and is the IP address that works. When I am not connected to my home's internet, that same IP address does not work. So it seems like there is something fishy going on that is way over my head. 

Model: WNDR4300v2|N750 Wireless Dual Band Gigabit Router
Message 1 of 3

Accepted Solutions
antinode
Guru

Re: Trouble with Port Forwarding on WNDR4300V2

> [...] 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:

 

      https://whois.arin.net/

 

   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.

View solution in original post

Message 2 of 3

All Replies
antinode
Guru

Re: Trouble with Port Forwarding on WNDR4300V2

> [...] 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:

 

      https://whois.arin.net/

 

   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.

View solution in original post

Message 2 of 3
aweissmeister
Aspirant

Re: Trouble with Port Forwarding on WNDR4300V2

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. 

Message 3 of 3
Discussion stats
  • 2 replies
  • 602 views
  • 1 kudo
  • 2 in conversation
Announcements

Orbi WiFi 6E