We have an unusual public network setup. We have a total of 3 interfaces.
Interface 1: has a public 209.44.60.253/30 network
Interface 2: has a public 209.44.70.XX/24 network.
Interface 3: is our private network.
Interface 1 is connected to our ISP routers. Interface two is connected to a switch with public servers with a public IP...they are not natted.
Essentially, our "block" of pulbic ip's are routed to the second interface by the first public interface that is on a different routable public ip. Thats the way the ISP gave us this block...i know..its weird. This does work fine for servers on the switch connected to Interface 2.
Interface 1 and 2 act like a pure router and do not NAt between each other.
Now we have a server in the internal network we need to nat a 209.44.70.XX IP to the internal server. But the normal NAT rule does work. If we create a new secondary IP on interface 2, and then create a simply DNAT to send that to an internal IP it does not work. We have no spare IP's on the primary Interface 1 as it's subnet is a single IP.
Its like the astaro doesn't like to route the traffic to the second interface, and then NAT it to the third interface.
Anybody see a way around this? With logging turned on for the rule, I do see the initial NAT rule get processed, but no traffic after that.
-Tim
This thread was automatically locked due to age.
