From owner-freebsd-isp Sat Feb 1 23:46:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA06946 for isp-outgoing; Sat, 1 Feb 1997 23:46:32 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA06938 for ; Sat, 1 Feb 1997 23:46:26 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id SAA21406; Sun, 2 Feb 1997 18:48:56 +1100 (EST) Date: Sun, 2 Feb 1997 18:48:55 +1100 (EST) From: "Daniel O'Callaghan" To: steve cc: FreeBSD-isp@freebsd.org Subject: Re: sliplogin troubles - routing problem? In-Reply-To: <1.5.4.16.19970202004240.10ff154e@idirect.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 1 Feb 1997, steve wrote: > The problem has shifted: I removed the arp lines in slipup and slipdown. > Now, upon establishing a connection, I can ping the world, dig, ftp, surf, > anything, for about 2 min 57 sec! Then, even if in the middle of an ftp > transfer, poof, 0 communication, I can't even see a host on my own net, not > even the oher side of the slip. Are you or the other end running routed or gated? A three minute timeout sounds like a RIP expiry time. If you are running gated or routed the sl* interfaces must be marked as passive, i.e. don't expect information from the remote gateway, just assume they are working. Otherwise, gated/routed will expect the other end to continually annouce its presence, and if it doesn't, the route will be marked for deletion after 1 minute silence and deleted after a further two minutes of silence. Danny