Date: Tue, 04 Feb 1997 19:44:57 +0100 From: Eivind Eklund <eivind@dimaga.com> To: Charles Mott <cmott@srv.net> Cc: Brian Somers <brian@awfulhak.demon.co.uk>, Ari Suutari <ari.suutari@ps.carel.fi>, hackers@freebsd.org, brian@utell.co.uk Subject: Re: Single socket version of natd Message-ID: <3.0.32.19970204194456.00bbae30@dimaga.com>
next in thread | raw e-mail | index | archive | help
At 10:53 AM 2/4/97 -0700, Charles Mott wrote: >On Tue, 4 Feb 1997, Eivind Eklund wrote: > >> And all the other really nescessary code-changes are done - everything is >> changed to ANSI style, and integrated with PPP from -current patched with >> #ifdef's to make it compile and work on all versions from 2.1.0 to >> -current, with an extra command 'alias' that set alias options. > >Do the alias options default the way they have in the past, or does the >user have to explicitly set them? They default the same way, yeah. I'll drop the source at you later tonight. >Can packet aliasing be enabled a ppp command as well as the -alias >command line option? Yep. >If so, is this a good idea? My concern here is that users be able to use the >same ppp.conf file with and without packet aliasing. My concern is that I should be able to make all users on the LAN (all of them have access to setting up a PPP connection) remember to enable aliasing. If I had not wanted it in all cases, I'd just drop putting the command in the config file. Nothing lost in my case, at least. However, a way of giving the user 100% control again might be to add a -noalias keyword to completely block packet aliasing. This would take one more bit from mode in IIJ-PPP, though. Besides, as an admin I'm not certain I would want the users to have that control. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.32.19970204194456.00bbae30>