NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ShieldsUp
Jan 15, 2020Aspirant
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
Jan 16, 2020Aspirant
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.
CrimpOn
Jan 16, 2020Guru - Experienced User
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?
- ShieldsUpJan 16, 2020Aspirant
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.