Hi, On Thu, Feb 09, 2012 at 03:49:11PM +1300, Michal Ludvig wrote: > I'm used to pushing route options to the clients with explicit metrics. > That works good for IPv4 with e.g.: > push "route 192.168.128.0 255.255.240.0 vpn_gateway 200" > > However route-ipv6 doesn't accept the 'vpn_gateway' keyword and > therefore I can't easily set a metric. I could indeed put the actual > server IP in there but that's less flexible, partly because I have this > routes section in a separate file included in multiple configs on the > same machine.
What are you trying to achieve?
> Can we have 'route-ipv6' accepting the same keywords as 'route' for
> consistency? Please :)
Someone needs to do the work. It's somewhere on my TODO list, but I
haven't seen a strong need yet, so other bits have been done earlier.
> BTW ideally, for even more consistency, modify 'route' (v4) to also
> accept "net/prefix" as well as the old-fashioned "net netmask". OpenVPN
> is one of the last programs where I still have to use netmasks instead
> of the more convenient prefixes. That'd be truly awesome :) (but not as
> important as the vpn_gateway support for route-ipv6 of course).
Someone would need to implement that, in a backwards-compatible fashion.
I'm not, as I don't work on legacy IP support anymore.
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
pgpalCJfynFss.pgp
Description: PGP signature
