From owner-freebsd-bugs  Mon Feb  3 16:40:08 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA02188
          for bugs-outgoing; Mon, 3 Feb 1997 16:40:08 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA02178;
          Mon, 3 Feb 1997 16:40:03 -0800 (PST)
Date: Mon, 3 Feb 1997 16:40:03 -0800 (PST)
Message-Id: <199702040040.QAA02178@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: kern/2647: changing existing route to -static crashes kernel 
Reply-To: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/2647; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: csw@gated.epigram.com
Cc: FreeBSD-gnats@freebsd.org, fenner@parc.xerox.com
Subject: Re: kern/2647: changing existing route to -static crashes kernel 
Date: Mon, 3 Feb 1997 16:21:59 PST

 >	Using the "change" command to add the "-static" flag to
 >  	an existing route on the local ethernet will always crash the machine.
 
 The "change" interface is not very well fleshed out.  I think it pretty much 
 only works for changing gateways, metrics or locks; so even if it didn't panic 
 it wouldn't accomplish what you want.
 
 To accomplish what you appear to want to do, you could try
 
 arp -s 199.2.31.1 0:0:c:76:30:3d perm
 
 (although I don't know why you'd want to do that, if it's dynamically 
 discoverable once, it's presumably dynamically discoverable again when it's 
 needed...)
 
   Bill