From owner-freebsd-isp  Fri Sep 12 11:36:05 1997
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA27244
          for isp-outgoing; Fri, 12 Sep 1997 11:36:05 -0700 (PDT)
Received: from marlin.exis.net (root@marlin.exis.net [205.252.72.102])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA27222
          for <freebsd-isp@FreeBSD.ORG>; Fri, 12 Sep 1997 11:35:51 -0700 (PDT)
Received: from sailfish.exis.net (sailfish.exis.net [205.252.72.104])
	by marlin.exis.net (8.8.4/8.8.5) with SMTP id OAA21770;
	Fri, 12 Sep 1997 14:36:08 -0400
Date: Fri, 12 Sep 1997 14:34:14 -0400 (EDT)
From: Stefan Molnar <stefan@exis.net>
To: Richard Hodges <rh@alpine.net>
cc: lashby@texramp.net, freebsd-isp@FreeBSD.ORG
Subject: Re: NAT for dialups?
In-Reply-To: <Pine.BSF.3.91.970912101757.28083E-100000@oak.alpine.net>
Message-ID: <Pine.LNX.3.95.970912143204.17581D-100000@sailfish.exis.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> I did a quick test with ether/ether on a 486/100 with 2.2.2  It
> worked surprisingly well.  I tested web, ftp, irc, news, realaudio,
> and MS file & print services.  FTP pooped out around 400K/second,
> about half what it should be (CPU utilization: around 30%), but
> normal web browsing seemed as good (or better!) than before.

Also someone might need to checkout gaming, via Kahn, and Kali.  
Too bad that I do not have enough time for gaming to test 
natd ether/ether.

Stefan