Hi, On Wed, Jun 19, 2013 at 06:00:27PM +0300, Athanasios Douitsis wrote: > I noticed that issuing the following command in the server config: > > push "route-ipv6 ::/0 2001:648:2000:ffae::1 15" > > does indeed make a windows client install that route, but it ignores the > metric:
True. There is no metric support for IPv6 routes today - half of it is
"because most operating systems don't actually support route metrics"
and the other half is "because I'm lazy and haven't found a problem
that needed metrics, and couldn't be tackled in a more robust way".
> Fwiw, I was able to workaround this problem by pushing two /1 routes,
> exactly like def1 does for IPv4. Like this:
>
> push "route-ipv6 ::/1 2001:648:2000:ffae::1"
> push "route-ipv6 8000::/1 2001:648:2000:ffae::1"
routing 2000::/3 is usually sufficient, as all globally routable IPv6
space is in there.
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
pgpMJtIUynDkX.pgp
Description: PGP signature
