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' ke
Hi,
On Thu, Feb 09, 2012 at 10:44:15PM +1300, Michal Ludvig wrote:
> >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_g
On 02/09/2012 09:20 PM, Gert Doering wrote:
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
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' ke
