Le 19 mars 2013 à 05:49, Eugene M. Zheganin a écrit :
> You cannot do this with a pptp or l2tp, they just don't have that ability.
> Standard approach is either using remote pptp/l2tp peer as default gateway,
> or creating a sticky route on the client side.
Even if it’s not built-in the L2TP
Le 18 mars 2013 à 22:22, Yoann Gini a écrit :
>
> Le 18 mars 2013 à 21:48, Joe Holden a écrit :
>
>> You use something that can push configuration the client, like openvpn or
>> run dhcp over something
>
> Well, I really don’t understand.
>
> Fro
Le 18 mars 2013 à 21:48, Joe Holden a écrit :
> You use something that can push configuration the client, like openvpn or run
> dhcp over something
Well, I really don’t understand.
From my experience, with a Cisco VPN Concentrator or a OS X VPN Server or a
Windows VPN Server, you can set a L
Hi,
Le 18 mars 2013 à 18:23, Joe Holden a écrit :
> The radius entry tells the NAS (mpd in this case) to add a route towards the
> client, the route/ip will still need to be configured on the client side, do
> you see a correct entry on the NAS? (route -n get 10.42.0.0/23)
OK, that’s still no
Hi,
Thank you for your answer.
Le 18 mars 2013 à 01:54, Joe Holden a écrit :
> If you're using radius, see 'framed-route'... if not, see external auth
Well, that’s a unexpected answer, I will never think to set that information in
the Radius server instead of the VPN server…
That’s the only
clue about how to do that…
They have a « set iface route » option but this add the route on the server
side, I want the same to push route on the client side…
If someone can give my a clue…
Best regards,
Yoann Gini.
smime.p7s
Description: S/MIME cryptographic signature
