From owner-freebsd-bugs  Mon Jul  7 07:40:04 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA16093
          for bugs-outgoing; Mon, 7 Jul 1997 07:40:04 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA16086;
          Mon, 7 Jul 1997 07:40:01 -0700 (PDT)
Date: Mon, 7 Jul 1997 07:40:01 -0700 (PDT)
Message-Id: <199707071440.HAA16086@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: kern/4044: kernel crashes when ip_output() is called with a NULL route argument
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/4044; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: freebsd-gnats-submit@freebsd.org, terzis@cs.ucla.edu
Cc:  Subject: Re: kern/4044: kernel crashes when ip_output() is called with a NULL route argument
Date: Mon, 7 Jul 1997 00:20:10 PDT

 Two more things:
 
 1) It's a good idea to use "options DIAGNOSTIC" when writing network
 code; it enables extra checks, one of which is a "panic: no route".
 
 2) If you do any kind of packet/flow classification and have a data
 structure that might be associated with a single destination address,
 you should add a route to that data structure (like TCP and multicast
 tunnels do) and pass that to ip_output instead.
 
   Bill