Assign Two 3proxy Ports to Two Outgoing IPs

To choose an exit IP explicitly, two fixed proxy endpoints can be easier to reason about than a rotation rule. With 3proxy, each service can have an outgoing source address.

After your existing user, authentication, and access-control settings, a service fragment can be:

socks -i127.0.0.1 -p1080 -e192.0.2.10
socks -i127.0.0.1 -p1081 -e192.0.2.11

These SOCKS listeners are local-only. Replace the documentation addresses with addresses provisioned on the server. Remote clients need an intended private listener and the appropriate network and authentication policy, not a casually opened wildcard listener.

The 3proxy reference distinguishes -i, the client-facing address, from -e, the service's outgoing source. A program chooses the first or second endpoint; this does not promise a different IP for every request.

Write down what each endpoint means

For example, port 1080 is intended to leave through address A and port 1081 through address B. That mapping makes surprising behavior easier to investigate than an undocumented pool.

The outward identity still depends on the network. A provider must permit the chosen source, and the route must return traffic correctly. If upstream NAT rewrites both sources to one public IP, websites see the translated address.

An existing browser connection can also retain its earlier path after a configuration edit. First establish that a new connection used the intended listener, then follow it to the final outward hop. Counting configured service ports alone does not count distinct public exits.