From owner-freebsd-hackers Mon Dec 2 17:43:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28344 for hackers-outgoing; Mon, 2 Dec 1996 17:43:10 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA28334 for ; Mon, 2 Dec 1996 17:43:06 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id RAA07126; Mon, 2 Dec 1996 17:42:56 -0800 (PST) To: Bill Fenner cc: hackers@freebsd.org Subject: Re: Bizarro bug in 2.1.6 that's had me stumped for ages... In-reply-to: Your message of "Mon, 02 Dec 1996 17:32:26 PST." <96Dec2.173236pst.2310@tibia-235.parc.xerox.com> Date: Mon, 02 Dec 1996 17:42:56 -0800 Message-ID: <7122.849577376@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does "ifconfig sl0 down; ifconfig sl0 up" help, or do you have to kill > and restart slattach? I have to kill and restart slattach. I tried the down/up trick too. :-( > Does "ifconfig sl0 delete; ifconfig sl0 address rmtaddr" help? I haven't tried that. I will give it a shot next time it goes tango-uniform on me. > When you're experiencing the problem, what do packets going out the > line sourced from your machine look like? (e.g. tcpdump -n -i sl0 icmp; > ping somehost). They apparently don't even *try* to go out the interface! :( It's apparently something farther up the line saying "no, it's dead, let it rest in peace." Jordan