From gibbs@estienne.cs.berkeley.edu Mon Jan 2 23:56:00 1995 Received: from narnia.hip.berkeley.edu (narnia.HIP.Berkeley.EDU [136.152.64.57]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA11582 for ; Mon, 2 Jan 1995 23:55:58 -0800 Received: (from gibbs@localhost) by narnia.hip.berkeley.edu (8.6.9/8.6.9) id XAA00469; Mon, 2 Jan 1995 23:55:55 -0800 Message-Id: <199501030755.XAA00469@narnia.hip.berkeley.edu> Date: Mon, 2 Jan 1995 23:55:55 -0800 From: gibbs@estienne.cs.berkeley.edu Reply-To: gibbs@efreefall.cdrom.com To: FreeBSD-gnats-submit@freebsd.org Subject: Configuring a SLIP device with source = destination -> reboot. X-Send-Pr-Version: 3.2 >Number: 95 >Category: kern >Synopsis: Configuring a SLIP device with source = destination -> reboot. >Confidential: no >Severity: serious >Priority: low >Responsible: core >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 3 00:00:00 1995 >Closed-Date: Sat Jan 20 04:05:12 PST 1996 >Last-Modified: Sat Jan 20 04:06:13 PST 1996 >Originator: gibbs >Release: FreeBSD 2.1.0-Development i386 >Organization: >Environment: >Description: ifconfig sl0 inet 136.152.64.57 136.152.64.57 netmask 0xfffffe00 Dial provider Run slattach First access of the device causes reboot. I doubt anyone would WANT to do this, but I did it by mistake, and it shouldn't cause a reboot. Maybe this will point someone in the right direction for finding that infinite loop that DG talked about being the source of these strange reboots and the new routing code. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->closed State-Changed-By: mpp State-Changed-When: Sat Jan 20 04:05:12 PST 1996 State-Changed-Why: Fixed in -current (actually, this was fixed sometime last spring, give or take a couple of months). >Unformatted: