Hi, On Wed, Aug 17, 2016 at 12:54:20PM +0100, debbie10t wrote: > So I re-state my original question in a more appropriate way: > > _Why_ does --ifconfig-noexec *not* effect IPv6 ?
It *does*. The only place in OpenVPN where this flag is checked is
in init.c:
Windows and Android:
/* do ifconfig */
if (!c->options.ifconfig_noexec
&& ifconfig_order () == IFCONFIG_BEFORE_TUN_OPEN)
{
/* guess actual tun/tap unit number that will be returned
by open_tun */
const char *guess = guess_tuntap_dev (c->options.dev,
c->options.dev_type,
c->options.dev_node,
&gc);
do_ifconfig (c->c1.tuntap, guess, TUN_MTU_SIZE (&c->c2.frame), c->c2.e
s);
}
all other platforms:
/* do ifconfig */
if (!c->options.ifconfig_noexec
&& ifconfig_order () == IFCONFIG_AFTER_TUN_OPEN)
{
do_ifconfig (c->c1.tuntap, c->c1.tuntap->actual_name, TUN_MTU_SIZE (&c
->c2.frame), c->c2.es);
}
... but as you can see, there is no "do_ifconfig_ipv4()" inside the
clause, and "do_ifconfig_ipv6()" outside. do_ifconfig() does IPv4
and IPv6 (tun.c) - if if it is not called for IPv4, there is nothing
else in the code that would do ifconfig for IPv6.
> The point here is that using --ifconfig-noexec & --up
> for IPv4 you manually configure everything
> for IPv6 you *must* --pull-filter ignore "ifconfig-ipv6 "
> because --ifconfig-noexec has *no* effect on IPv6
Please show a log file that shows
- incoming push message
- that IPv4 is not ifconfig'ed
- but IPv6 is
(I'm not saying our code has no bugs, but I cannot see a way how this
could ever happen)
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
signature.asc
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
