Date: Thu, 10 Aug 2006 21:32:22 -0600 From: Brett Glass <brett@lariat.net> To: Ganbold <ganbold@micom.mng.net> Cc: net@freebsd.org Subject: Re: Big PPTP server Message-ID: <7.0.1.0.2.20060810212047.073f0078@lariat.net> In-Reply-To: <44DBF2BB.5080202@micom.mng.net> References: <7.0.1.0.2.20060810201735.067258b0@lariat.net> <44DBF2BB.5080202@micom.mng.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:00 PM 8/10/2006, Ganbold wrote: >It will be much easier if you can write some script to generate >mpd config files. I'm generating config files such way for PPPoE. Is there a way to avoid having to generate them at all? It seems to me that it would be very easy for mpd to create netgraph nodes on the fly as it needed them. >Did you try Radius? This company hasn't been using a RADIUS server. They have an Active Directory server (yuck!), but I don't know if it would be useful for this purpose. By the way, a related problem I'm encountering is that mpd seems to want some options set before authentication when they need to be set afterward based on the user's identity. For example, while the user's IP can be set when the user is identified and authenticated (via mpd.secret), the IP at the host end of the PPP link can't. So, you run into situations where the IP assigned to the incoming PPP/PPTP user isn't on the same subnet as the one assigned to the host, which seems to cause routing problems. --Brett Glass
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7.0.1.0.2.20060810212047.073f0078>