Hi, On Mon, May 14, 2012 at 12:12:07AM +0200, Arne Schwabe wrote: > Openvpn will show the following warning, if I enable tun-ipv6 in the > local config and not remote or vice versa: > > WARNING: 'tun-ipv6' is present in remote config but missing in local > config, remote='tun-ipv6'
If I remember correctly, if tun-ipv6 is not enabled on the client side,
the client will ignore pushed ipv6 ifconfig + routes.
So maybe the warning should not be tied to "tun-ipv6 is configured" but
to "the server pushed something that the local config will auto-ignore".
(Right now the warning is coming from the generic "compare the client
and server side config, and warn about differences" code - where it
might make sense to exclude this option, and add a specific warning
for those cases where it might cause surprises - namely: server with
IPv6, server pushing IPv6 options, client without tun-ipv6)
> >From my understanding a ipv6 capable tun interface is always capable of
> ipv4 only.
Yes. On some systems, extra work is needed to make the tun interface
handle IPv6 as well, and that's triggered by tun-ipv6 - but IPv4 will
always work.
> Even without explicitly stating "tun-ipv6" openvpn will happily
> configure the ipv6 options.
You're sure of that? This is what it shouldn't do, at least for pushed
options (it will accept the options but not use them).
But anyway. I need to go through the code again and figure out what
exactly tun-ipv6 is doing today *on which platform*, and maybe document
that better...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpFgbIJXFd9y.pgp
Description: PGP signature
