Running a proxy server for multiple physical IPs

[frostfiretulsa]

Hi Guys,

First off, I may be overlooking something simple, as I am new to the whole proxy server thing. Please forgive me if this is a dumb question.

I have a dedicated server with (currently) 64 IPs spread out on 3 physical NICs.

I have installed Wingate and set it up to allow proxy access via all of those IPs for registered users.

So far, that works. To explain my problem, lets imagine I have the following IPs:

10.5.5.1
10.5.5.2
10.5.5.3

On a single NIC. If I connect to 10.5.5.1 and visit a IP checking website, my IP does show up as 10.5.5.1 ... but if I connect to the 10.5.5.2 address, my IP also shows up as 10.5.5.1. I assume because that is the first IP on the physical adapter on the server.

Now my question is how do I make each IP use itself as an external IP when using them as a proxy? Hopefully that makes sense.

Please let me know anything that might help...

Thanks!

Dave

[adrien]

Hi Dave

by default when WinGate makes a connection to a site, it lets the OS choose what the source IP (local IP) should be for the connection. So I think normally the OS chooses the first IP associated with a route that matches the destination.

WinGate does allow you to override this, in the gateways tab, if you select "use all specified connections in rotation" and add an entry, you can specify specify which local IP to bind to before making that connection.

This can also be overridden in flow-chart policy by assigning a new value to Session.Interface

e.g. you could do something like (in policy in an expression evaluator)

Session.Interface = Session.ClientInterfaceIp

This then would set the outgoing connection to bind to the same interface the connection was received on. I'd do this in the ClientConnect event for the WWW proxy.

Regards

Adrien de Croy

[adrien]

Hi

actually depending on your license, you should not even need to use a flow-chart policy. You can assign a jscript or luascript item to the event (WWW Proxy: ClientConnect) directly in the events panel (WinGate > Control Panel > Events).

It should not be necessary to enter anything on the gateways tab in the proxy either.

Regards

Adrien