Messages

1

15.7 Legacy Series / Re: Binding an internal machines traffic to a specific external IP

« on: July 28, 2015, 10:23:44 am »

No. In my case no virtual IP was necessary. I've seen that WAN2 has 8 IP addresses. So they reported outgoing IP should be the one assigned to the network interface on WAN2.

My setup has a different need. I made it to differentiate traffic over 2 internet connections (like http traffic going over a "cheap" line). Only disadvantage I realized and couldn't solve until now is that this happens before routing. But that shouldn't be an issue in your setup.

2

15.7 Legacy Series / Re: Binding an internal machines traffic to a specific external IP

« on: July 28, 2015, 09:33:41 am »

I have done a similar setup which should work in your case too.

You need to add a LAN firewall rule where you specify the gateway (in your case the one of OPT1).

Interface: LAN
Source: IP of Server (LAN)
Destination: Any
Gateway: GW of OPT1

That should make the trick. Attached a screenshot to make it clearer. Hope this helps you.