Hi, On Sun, Sep 13, 2015 at 11:11:48AM +0200, Arne Schwabe wrote: > Am 11.09.15 um 17:33 schrieb Gert Doering: > > Add "ipv6" and "!ipv4" sub-options to "--redirect-gateway" option. > > > > This is done in the same way as in the OpenVPN 3 code base, so > > "--redirect-gateway ipv6" will redirect both IPv4 and IPv6 - if you > > want v6-only, use "--redirect-gateway ipv6 !ipv4". > > Current 2.3 code will exit with an error on seeing the ipv6 keyword.
True. This inconsistency has been there since 3 introduced the keyword...
> Reading the source code this is equivalent to
>
> redirect-gateway
> route-ipv6 ::/3
> route-ipv6 2000::/4
> route-ipv6 3000::/4
> route-ipv6 fc00::/7
>
> which also works in 2.3. What do we offer as config advice for users?
Right now, pushing "route-ipv6 2000::/3" or the equivalent of the above.
What about adding this part of the patch set to 2.3? It does not need
the "discover and redirect gateway for IPv6" infrastructure - as it
basically is just a macro anyway..
> (It is good that this works otherwise my code will break configs that
> use a remote ipv6-enabled-server)
>
> Also the documentation is slightly wrong.
What's wrong?
> Sidenote: What about IPv6 multicast?
Right now, our IPv6 multicast support is pretty much non-existing, both
link-local or "routed wide area". I have not personally run into any
issues that needed IPv6 multicast support, and can't remember any open
trac tickets, so I'm not sure what we'd need...
(Our IPv4 multicast support is also fairly limited - if a packet hits
the p2mp server, it is replicated to all clients, and that's it. No
IGMP, PIM, or anything more smart... for IPv4, there *is* a trac ticket,
but is classified as "wish list")
Extra Side-Note: link-local address support is also not there today.
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
pgpR4BZEq3sfF.pgp
Description: PGP signature
