Yoann Gini wrote:
Le 18 mars 2013 à 21:48, Joe Holden <li...@rewt.org.uk> 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 L2TP VPN service with some remote config to
send to the client (DNS servers, domain name, routing information [like what it
for the private network and what is for the public one], and so on).
It supposed to be built-in the VPN client and server. On others platform, I
don’t need to use a setup based on SSL VPN like OpenVPN and it’s not the DHCP
who handle that kind of client config but the built-in mechanisms in the VPN
Server (that’s the case for L2TP and PPTP).
I’m quite surprised to be front of a so difficult problem here. Routes sends to
the clients are something like the 101 VPN course…
How do you handle your routing table on your VPN systems with mpd5 without
having to push routes from your concentrators ?
Best regards,
Y.
Cisco et al don't use plain l2tp/pptp - they allow the remote
configuration of client routing.. traditional ppp doesn't allow the
ability to push configuration to the clients outside of IP/dns/netbios
etc, IPsec for example has this ability but straight ppp does not.
You will probably be better off by doing IPsec over L2TP as it should
cover what you need
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
