NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RS700 - passing L2TP traffic to internal server
[NOTE: I am preconfiguring an RS700 on my local LAN so I can send it to a remote family member. Hence, the "external" address of the RS700 is a private address (192.168.3.155); the LAN/internal addre...
I greatly appreciate the help everyone!
Following StephenB's comment about trying to forward Port 5000 (and 5001 for https administration), I neither worked. Doubtful that it would be a Netgear bug, I went down the path of starting from scratch with the network connectivity. The issue (please don't kill me) is that I had the Synology server connected (via ethernet) to both the 192.168.3.x and 192.168.10.x networks (multiple ethernet ports in the Synology). Once I disconnected the 192.168.3.x ethernet, everything worked as expected.
Thanks for your help! Apologies if this is a rookie mistake...
The port forwarding only works for traffic coming from outside the network. The "192.168.3.151" and the RS700 WAN IP "192.168.3.155" are on the same private subnet, the RS700 sees it as internal traffic and won’t forward it to the Synology NAS (192.168.10.5).
The "192.168.3.151" and the RS700 WAN IP "192.168.3.155" are on the same private subnet,the RS700 sees it as internal traffic
Not the case. 192.168.3.155 is the WAN address of the RS700, and the .151 client is sending the traffic to the RS700 WAN ethernet port. So this is external traffic as far as the RS700 is concerned.
However on same subnet which doesn't work from what I'm getting from NG.
However on same subnet which doesn't work from what I'm getting from NG.
I forward ports from my ISP router to my Orbi, and then forward them in the Orbi to the destination client. While slightly different from omane's situation, the source IP address of the traffic coming in through from the ISP router still has the same subnet as the Orbi WAN address (192.168.1.x in my case).
Are you sure that NG understands omane's full setup? If they are correct, this would be a REALLY bad bug. In a normal network configuration the WAN subnet can include the entire ISP. So if you (for example) were forwarding FTP ports to the NAS, you would be unable to use FTP remotely from any of your neighbors' networks. Even worse if you can't double-forward if you have to double-NAT.
Their assertion can be easily tested with the Synology by forwarding TCP port 5000 to port 5000 of the NAS, and then seeing if https://192.168.3.155:5000 reaches the Synology management interface.
Waiting for more feedback.