datex wrote:Hi there,
I got the same problem.
I got 10 external IPs and I want to use one socks services, which has bind on "ANY EXTERNAL IP", how to set the socks serive to enable users to use different external IPs?
For example a user connect by 1.1.1.1 and the external IP is 1.1.1.1. And he can also connect by 1.1.1.2 and the external ip will be 1.1.1.2?
Now I set the gateway, and I fount if I set the source IP on "ANY IP", the external IP will be same one forever. And I dont want to use the external ips in rotation or pirority order.
And another fatal problem, if I set the source IP of gatways, the OS will crash into bluescreen when a user connect the service. How to solve this problem? The OS is windows2003 sever.
Thanks
When you make a connection on windows, windows chooses which local interface to use, based on the route table. So unless you tell WinGate to do something, the OS will choose which IP is used for a connection back out of WinGate, it has nothing to do with which interface the SOCKS client connected to WinGate on.
If you want connections made by clients to go out the same interface they connected to the SOCKS server on, you can do this in policy, for example in the ConnectRequest event, set
Session.Interface = Session.ClientInterfaceIp
That tells it to use the same interface for the outgoing connection.
Otherwise you could set up a different SOCKS server for each IP, bind it only to that IP, and set a gateway setting. If you only enter 1 gateway in the gateways tab, it doesn't matter which scheme you choose (failover or priority) since there's only one to choose.