I have 4 sites that have the same subnet (192.168.20.0/24) but with a One-to-One nat network setup. For example Site 1 (Internal: 192.168.20.0/24 NAT: 10.168.1.0/24). On a server in the 192.168.20.0/24 network, I can ping the NAT of the same server. (ex: Server = 192.168.20.20, NAT = 10.168.1.20). Is there a way to prevent a local IP to ping it’s own NAT IP but still allow remote sites to communicate to the server?
For the outbound policy I do have it setup to route all internal traffic to the Fusionhub.
Seems unlikely since for the 1:1 NAT to work the local 192.168.20.0 subnet needs to be able to communicate with the local NAT range (ie 192.168.1.0).
With expert mode turned on and this rule dragged above the line?
What is the problem with this actually? What isn’t working?
Expert mode is working fine. I’m attaching a table. How can I prevent the NAT IP from coming into the fusionhub and looping back to the same site. Such as I don’t want NAT IP: 10.168.1.200 (local ip: 192.168.20.200) from being able to RDP to NAT IP: 10.168.1.150 (192.168.20.150). I could put a rule in the fusionhub, peplink router or firewall to prevent that but is there a setting that I might have missed?
