Hi,
On Thu, Mar 11, 2010 at 05:42:07PM -0500, Stefan Monnier wrote:
> >> Let's not add more complexity to openvpn itself, I'd be much happier if
> > You just don't understand.
> > The complexity *WILL* be in OpenVPN, if we decide to support
> > "route-gateway dhcp" for non-Windows platforms.
>
> I'm not sure what "route-gateway dhcp" does, so maybe that's part of the
> reason why we disagree.
In that case it might be helpful to read the mail from James Yonan that
started this thread.
> I thought the discussion was about how to make
> DHCP work over an OpenVPN bridge (i.e. a TAP device) under systems like
> GNU/Linux. On those systems, the only thing you need to do is to make
> sure that things like ifplugd correctly receive the info about when the
> tunnel goes up and down.
This is the trivial bit.
[..]
> I find the effort would be better spent on working with other people
> trying to make sure that ifplugd/NetworkManager/distributions/... make
> this setup as troublefree as possible. E.g. make sure that ifplugd
> works well with tap devices (e.g. that it tries to handle them by
> default) and that NetworkManager can easily use OpenVPN and correctly
> (re)starts dhcp clients for the corresponding tap devices.
The world is a bit larger than "Linux distributions having ifplugd".
OpenVPN runs on Linux, 5 different *BSD variants, Solaris, MacOS X
and Window - and it's not OpenVPN's job to fix the local equivalent of
ifplugd on each of these systems. OpenVPN's aim is to provide an
easy-to-use VPN environment for people that do not want to endlessly
fiddle with operating system settings.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
