Virtual IP NAT not applying

Started by mauzilla, October 07, 2022, 04:34:33 PM

Previous topic - Next topic
I have the following:

- WAN IP 129.232.150.165
- My ISP is routing a 129.232.150.168/29 through the WAN gateway 129.232.150.165
- I want to setup 1:1 NAT so that traffic between 129.232.150.170 and an internal IP on a different interface (fibreLAN) with IP 10.1.31.2

I have:

1) Created a virtual IP, I am however not sure if I need to individually add all the IP's from my virtual IP range (129.232.150.169 - 129.232.150.174) or if I can add the entire range as a virtual IP (thus 129.232.150.168 / 29) - If individually, should I then set my IP as a /32 or do I leave each individual virtual IP still within the /29?

2) My next step is to setup a 1:1 nat - I am however not sure if I have my following iterms correct:

- In my case, must the external network be the actual IP address I wish to forward from the WAN side (for example 129.232.150.170?)
- Or must the source IP be 129.232.150.170 or must this be the internal / private IP on the fibre side
- Lastly, the destination, should this me the fibre IP or must this be set as "any" (I got this from a youtube channel)
- AFter setting up the NAT, is there still any reason to add additional firewall rules for individual services? If so, what would be the source / destination network?

I have tried a number of options but I simply cannot get it working. I am expecting to ping for example 129.232.150.170 and have it ping the internal host, but no luck.



I have come no closer to a resolution I am afraid :( Port forwarding works perfectly, I am able to successfully use port forwarding to forward traffic from a routed IP by my ISP back to an internal VLAN IP - When I however add a 1:1, nothing happens. Looking at the firewall logs, I can see the traffic is hitting the firewall (so the actual routed IP works as expected), but it's either not recognizing my 1:1 or I am missing additional rules.

Any ideas?