[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Web openvpn.net

[Openvpn-users] one server-daemon, handling multiple clients

  • Subject: [Openvpn-users] one server-daemon, handling multiple clients
  • From: Chris Heinze <x@xxxxxxx>
  • Date: Fri, 24 Oct 2003 16:37:26 +0200


i'm currently using vtun, and would like to switch to openvpn because of the more sophisticated encryption functionality.

currently i have a vtund on a 'server', and multiple 'clients' that connect to this vtund. in the vtun-config every tunnel-setup has a name. in this way i have one vtund-server-config with multiple tunnel-setups listed. the vtund-server-config has only one tunnel-setup listed each. when the client connects to the server, the name/id of the tunnel-setup used is transmitted to the server, so the correct tunnel can be set up.
this is very handy, because there's just one daemon listening on just one port, spawning a new process for each new tunnel that is established. to add a new client, all that is needed on the server is to add a new section to the vtund config.

in production use (esp. when there are really a whole lot of tunnels) this is really a benefit over having to start a new and separate server process for each client, on a dedicated port for each tunnel and with a dedicated config.

i beleive it doesn't need too much of an effort to add such 'tunnel-ids' to openvpn (and i'm also sure it can be done without having to drop backward-compatibility), so i'm curious if that's something that has already been thought about, or maybe if there are any plans on implementing such a thing?


	Chris Heinze

____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users