From owner-freebsd-hackers  Tue Feb 21 12:07:39 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA14633 for hackers-outgoing; Tue, 21 Feb 1995 12:07:39 -0800
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA14626 for <hackers@FreeBSD.org>; Tue, 21 Feb 1995 12:07:37 -0800
Received: by halloran-eldar.lcs.mit.edu; id AA06058; Tue, 21 Feb 1995 15:07:04 -0500
Date: Tue, 21 Feb 1995 15:07:04 -0500
From: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu>
Message-Id: <9502212007.AA06058@halloran-eldar.lcs.mit.edu>
To: Tom Samplonius <tom@haven.uniserve.com>
Cc: hackers@FreeBSD.org
Subject: "route" crashes kernel...
In-Reply-To: <Pine.BSF.3.91.950220221644.10908A-100000@haven.uniserve.com>
References: <Pine.BSF.3.91.950220221644.10908A-100000@haven.uniserve.com>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

<<On Mon, 20 Feb 1995 22:18:57 -0800 (PST), Tom Samplonius <tom@haven.uniserve.com> said:

>   I'm using the 950210 snapshot, and I've found that doing:

>   route add 198.53.215.253 -link sl0

> consistently causes a "Page fault while in kernel mode" error. 

There are a number of bugs in the routing code which cause panics when
a gateway is not supplied for a route.  The supported way to express
what you have written here is:

	route add -inet 198.53.215.253 ip-address-of-sl0

`-link sl0' doesn't make much sense as a destination.  Perhaps you
meant to say:

	route add -inet 198.53.215.253 -interface ip-address-of-sl0

which would mean that the other end of sl0 has an alias address.

In any case, you are correct that this is a bug; the kernel should not
panic even upon erroneous routing commands.

-GAWollman