From owner-freebsd-bugs Tue Apr 11 09:59:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA23137 for bugs-outgoing; Tue, 11 Apr 1995 09:59:39 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA23131 for ; Tue, 11 Apr 1995 09:59:37 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA05366; Tue, 11 Apr 1995 12:59:19 -0400 Date: Tue, 11 Apr 1995 12:59:19 -0400 From: Garrett Wollman Message-Id: <9504111659.AA05366@halloran-eldar.lcs.mit.edu> To: pritc003@maroon.tc.umn.edu Cc: freebsd-bugs@freefall.cdrom.com Subject: kern/332: Incorrect routes can cause system to reset In-Reply-To: <199504110950.CAA17668@freefall.cdrom.com> References: <199504110946.EAA00290@mpp.com> <199504110950.CAA17668@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < Destination Gateway Flags Refs Use Netif Expire > default 128.101.118.21 UGSc 0 0 sl0 > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > 172.16.0.1 127.0.0.1 UH 0 0 lo0 > 224 172.16.0.1 US 0 0 sl0 > # ping freebsd.org > [machine resets here] Your problem here is very simple: you have specified a gateway (128.101.118.21) for which there is no route. When something attempts to use the default route, it must first find a route for the gateway. The only route that matches is the default route! This results in bottomless mutual recursion. The answer is to NEVER perform this step: > route delete 128.101.118.21 172.16.0.1 I am also working on code which should be able to detect this situation and avoid the problem entirely. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant