|
|
James Yonan <jim@xxxxxxxxx> said: >There have also been requests for an OpenVPN mode to handle multiple clients >from a single thread, while only using a single port and a single tun/tap >interface (rather than multiple OpenVPN processes for each tunnel, each with >their own port and tun/tap interface). I have some problems with this >approach -- essentially you need to implement a number of functions inside of >OpenVPN which are now covered by the OS, violating the principle of modularity >and minimalism which has guided OpenVPN's development process thus far. [...] FWIW, I heartily agree with this view. There's enough unstable bloatware for Unix already. I even doubt whether the forking server is such a big win - these idle daemons don't really eat lot of important resources (swapspace comes at ~$50 for a 40Gig drive ;-)), and as I'm generating client keys+config file+custom installer anyway, I don't really care about having to specify a different port per client. At best, it could be a political win because uninformed firewall admins in larger companies are more likely to open a single port than a range. -- Cees de Groot http://www.tric.nl <cg@xxxxxxx> tric, the new way helpdesk/ticketing software, VoIP/CTI, web applications, custom development ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |