I am trying to implement the following chain:

Client -> OpenVPN -> Socks -> WWW

The situation is complicated by multiple copies of OpenVPN on the server, which listen to different ports. Each instance has its own private ip network for clients, say 192.168.0.0

The result is:

Client 1 -> OpenVPN 1 ( 192.168.1.0 ) -> Socks 1 -> WWW

Client 2 -> OpenVPN 2 ( 192.168.2.0 ) -> Socks 2 -> WWW

There were attempts using firewall to route traffic through the incoming port, but they were not crowned with success.

  • one
    security.stackexchange.com/questions/31030/… - I hope to help you. See the answer from LSerni - the person painted everything quite clear. - 0-Level UNIX Monk
  • one
    Especially here: This is done through the routing rules for the client. For example, you might receive address 192.168.42.17/24 on VPN1, and address 192.168.77.13/24 on VPN2. If you tried to link with .42.33, you would go through it. and further ... - 0-Level UNIX Monk

0