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
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
Hi David,
David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/12 16:56, Jan Just Keijser wrote:
Hi Paul,
Paul Bakker wrote:
On 8-2-2012 15:53, Jan Just Keijser wrote:
Hi Paul,
I can't find why the client would use 'eth0' for the 'tun0'
network -
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'
Hi guys
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
