From owner-freebsd-hackers  Mon Dec  2 14:19:15 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA17816
          for hackers-outgoing; Mon, 2 Dec 1996 14:19:15 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17808
          for <hackers@FreeBSD.org>; Mon, 2 Dec 1996 14:19:08 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA17664; Tue, 3 Dec 1996 09:19:25 +1100 (EST)
Date: Tue, 3 Dec 1996 09:19:24 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: hackers@FreeBSD.org
Subject: Re: Bizarro bug in 2.1.6 that's had me stumped for ages...
In-Reply-To: <336.849531953@time.cdrom.com>
Message-ID: <Pine.BSF.3.91.961203091602.1605k-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 2 Dec 1996, Jordan K. Hubbard wrote:

> I kept hoping that this was just me somehow, but after looking and
> looking for some sort of misconfiguration and still banging into this
> one, I thought I'd finally ask.
> 
> I have a gateway machine with an SMC8216 ethernet card in it and an
> ISDN TA hanging off a standard 16550 serial port.  It works just
> peachy, 99.9% of the time, except after I've really exercised it in
> some way (seems to happen most frequently after a make world though
> this could just be the sheerest coincidence).  The symptom is that
> it's suddenly unable to talk to its SLIP interface directly, e.g.:
> 
> root@whisker-> ifconfig -a
> ..
> sl0: flags=9011<UP,POINTOPOINT,LINK0,MULTICAST> mtu 552
>         inet 204.216.27.194 --> 204.216.27.193 netmask 0xfffffff0 
> 
> root@whisker-> ping 204.216.27.193
> PING 204.216.27.193 (204.216.27.193): 56 data bytes
> <zilch, nada, zip>

This has happened to me.  You may remember I posted a month ago about 
"arpresolve: can't allocate llinfo for ..." errs.  Do you get these 
errors in your log file?  It occurs for me only on CSLIP interfaces which 
are gateways to other networks or subnets - never on a host-only cslip 
link, and never on a ppp link.  Are you running gated?  

Danny