Date: Mon, 18 Mar 2013 17:23:09 +0000 From: Joe Holden <lists@rewt.org.uk> To: Yoann Gini <yoann.gini@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: mpd5 and multiple route to send to clients Message-ID: <51474D7D.2030107@rewt.org.uk> In-Reply-To: <DA89EA18-0F70-4051-9368-5383F96E8D00@gmail.com> References: <9EC8E2D3-A52B-4FF1-B840-3D962DF8D917@gmail.com> <514665CD.80809@rewt.org.uk> <DA89EA18-0F70-4051-9368-5383F96E8D00@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yoann Gini wrote: > Hi, > > Thank you for your answer. > > Le 18 mars 2013 à 01:54, Joe Holden <lists@rewt.org.uk> 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 way to do that with mpd5 ? For example, on OS X Server we use vpnd who is able to manage route by itself… > > Nevertheless, I try your recommendations and on the users file of my FreeRadius config I’ve that config: > > DEFAULT Auth-Type := ldap > Framed-Protocol = PPP, > Framed-Route = "10.42.0.0/23 10.42.1.1 1", > Fall-Through = 1 > > Based on what I’ve seen on different examples. It don’t work. I can’t see this route on my client. What’s wrong with my setup? > 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) > Y.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51474D7D.2030107>