From owner-freebsd-hackers  Thu Jun 12 09:37:33 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA06419
          for hackers-outgoing; Thu, 12 Jun 1997 09:37:33 -0700 (PDT)
Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06413
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 12 Jun 1997 09:37:19 -0700 (PDT)
Received: (from tinguely@localhost)
	by plains.NoDak.edu (8.8.5/8.8.5) id LAA11915;
	Thu, 12 Jun 1997 11:37:07 -0500 (CDT)
Date: Thu, 12 Jun 1997 11:37:07 -0500 (CDT)
From: Mark Tinguely <tinguely@plains.NoDak.edu>
Message-Id: <199706121637.LAA11915@plains.NoDak.edu>
To: root@bmccane.uit.net, tinguely@plains.NoDak.edu
Subject: Re: /var/run/natd.pid request
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>  Everything then talks fine both on the firewall machine, and from my work 
>  machine across the room, for 0-3 minutes.  After that, the logging on the 
>  console slows to a halt, and if I try to:
>
>  	ping prep.ai.mit.edu  (arbitrary choice 8)

I am using a really old (2400 baud) modem to play with this before we send
it home with a couple professors. I completely hung the PPP connection once,
but I figured it was the slow modem. I have been able to panic the NATD
machine a couple of times with 2400 baud modem when I downloading big files
(ftp or netscape bringing down an image). I can also replicate it by
connectioning the NATD machine to another FreeBSD machine (386) a null-modem
cable at only 9600 baud -- the 386 can't do much faster. It could be the
slow nature of lines I am using or in the null-modem case, it could be
due to the fact I was using 10.1.10/24 on the ed0 interface and 10.1.1/24
on the ppp0 interface.

I guess I will try to get newer equipment in and see if crashing problems
disappear.

--mark.