NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Help Needed: Port Forwarding
Hi All, I'm having issues with port forwarding, scanner tool shows ports are closed/filtered. Here is my setup... Physical Setup AT&T Gateway BRGW10 Orbi RBR50 Router Connected to AT&T Ga...
ShieldsUp wrote:
I attempted to scan for open ports using pentest-tools.com and ipfingerprints.com. pentest-tools advises that the "host seems down" and ipfingerprints advises the ports in this range are filtered.
Assuming that the service is up and running, are you able to access it from a computer on the local LAN?
When you access pentest-toos and ipfingerprints, do they show your public IP address as the same as the Orbi WAN IP?
When you do a trace route from a computer on the local LAN to some known IP, such as Google's DNS 8.8.8.8, the first router should be the Orbi's private IP (usually 192.168.1.1), is the second router a public IP address?
Ah, good idea on the local test. I am unable to test at the moment, but will do so later this evening.
Yes, both sites show the same IP as my Orbi WAN IP and AT&T Broadband IP.
When tracert to 8.8.8.8, the first hop is the Orbi's private IP (10.0.0.1 in this case) and second hop is ATT GW's private IP (192.168.1.254). From there, my ISP and then onwards.
ShieldsUp wrote:Ah, good idea on the local test. I am unable to test at the moment, but will do so later this evening.
Yes, both sites show the same IP as my Orbi WAN IP and AT&T Broadband IP.
When tracert to 8.8.8.8, the first hop is the Orbi's private IP (10.0.0.1 in this case) and second hop is ATT GW's private IP (192.168.1.254). From there, my ISP and then onwards.
I think this is the problem. The gateway is NATing (is that a word?), which absolutely kills port forwarding. To verify, the WAN side of the Orbi probably has a 192.168 IP address, correct?
FURRYe38 Right, the port remaining open without anything accessing it is definitely not good security. I thought this was the reason Port Triggering was created. In any case, I will test again this evening while the local device is attempting to actively listen.
CrimpOn I'll consider it a word (network address translating) :smileytongue: The WAN side of the Orbi is showing my public IP. It is the same public IP on my ATT GW.
On the ATT GW, it is assigning 192.168.1.64 - 192.168.1.253. However, I see it is assigning the Orbi the same public IP above.