Since my OpenVPN server is running on the main router, it has the same IP as the gateway and there is no need to route the server-side LAN gateway to the VPN client subnet. Push "route 255.255.255.255" - no change, remote client can access local servers via LAN IP but not WAN IP. I also attempted to 'advertise' my WAN IP: NAT loopback enables a user on the trusted or optional networks to connect to a public server with the public IP address or domain name of the server, if the server is on the same physical Firebox interface. Im asking here, how can I disable NAT Loopback to perform testing, and then re-enable it afterward Currently, NAT loopback does NOT appear to be working correctly. Push "route 192.168.0.0 255.255.255.0" - no change, remote client can access local servers via LAN IP but not WAN IP. In later versions, Merlin v388.22 to be specific, on the RT-AX88u router, there is no NAT acceleration option/setting, nor is there any ability to enable/disable NAT Loopback. I followed the advice in the article posted about 'advertising' my home subnet in the server-side configuration with the following: If the client attempts to use the WAN IP via NAT Loopback to access local servers then they cannot connect. Navigate to Manage Rules NAT Policies submenu. Like I mentioned before, the remote clients have no trouble accessing everything on my home network as long as the LAN IP is used. Loopback Policy using WAN Interfaces IP Address Login to the SonicWall management GUI. The datagram sent by this host would look like this: IPsrc:192.168.1.4, IPdst:IPnat, Proto:TCP PortSrc: 50243, PortDst: 80 So, a new entry would be added to the NAT table: 192.168.1. Thanks for the reply however this situation is a little different. The loopback problem comes when trying to connect to (80.53.56.67,80) from an internal host, such as host A 192.168.1.4 with port 60000. HOWTO: Expanding the scope of the VPN to include additional machines
0 Comments
Leave a Reply. |