James Yonan wrote: > On Fri, 25 Nov 2005, Nielsen wrote: >>As it is openvpn has no way to allow the kernel to dynamically choose >>a source port for it's connections. If you have two openvpn client >>processes on the same machine both you have to configure lport to >>different ports manually. This patch allows you to specify '--lport 0' >>and get the behaviour of normal programs, where the source port is >>dynamically chosen. > > How is this different from simply using --nobind to allocate a dynamic > port #?
The issue I ran into was that I did want to bind to an address (in order to make the packets come from a specific interface) but not to a specific port (as in some cases I needed to run multiple openvpn processes on a single interface). Cheers, Nate
