From owner-freebsd-hackers  Tue Feb  4 11:33:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA07043
          for hackers-outgoing; Tue, 4 Feb 1997 11:33:48 -0800 (PST)
Received: from darkstar (dialin2.anlw.anl.gov [141.221.252.102])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07038
          for <hackers@freebsd.org>; Tue, 4 Feb 1997 11:33:42 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id MAA09041; Tue, 4 Feb 1997 12:33:17 -0700
Date: Tue, 4 Feb 1997 12:33:16 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: Eivind Eklund <eivind@dimaga.com>
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 
In-Reply-To: <3.0.32.19970204194456.00bbae30@dimaga.com>
Message-ID: <Pine.BSF.3.91.970204115817.9014A-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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.
> 

I agree that a -noalias keyword is a not a good idea. 

The way Eivind is doing things sounds good to me.  The "out-of-the-box" 
software for home users will be simple to set up and have standard
defaults that do not typically have to be changed, but there will also be
a level of control that an admin wants. 


Charles Mott