From owner-freebsd-hackers  Sat Jun  1 08:31:17 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA08906
          for hackers-outgoing; Sat, 1 Jun 1996 08:31:17 -0700 (PDT)
Received: from etinc.com (etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA08856;
          Sat, 1 Jun 1996 08:31:05 -0700 (PDT)
Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA00235; Sat, 1 Jun 1996 11:34:15 -0400
Date: Sat, 1 Jun 1996 11:34:15 -0400
Message-Id: <199606011534.LAA00235@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Version 2.0.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: hackers@freebsd.org
From: dennis@etinc.com (Dennis)
Subject: Nasty Routing BUG in 2.1R
Cc: freebsd-isp@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've encountered a nasty, easily reproducable bug in 2.1R that causes
a panic. The following sequence:

route add 200.11.1.17 200.11.1.3

/* where 200.11.1.17 is inactive or doesnt exist  and 200.11.1.3 is
   another FreeBSD router/host on the network. It  creates a route entry
   Dest=200.11.1.17 GW=200.11.1.3 */

ping -c 1 200.11.1.17

/* This generates a re-direct which changes the route entry to 
    Dest=200.11.1.17 GW=200.11.1.17. This seems quite wrong....
    the entry should be either deleted or resolved */

route delete 200.11.1.17

/* This causes a panic in the function rtfree(). If you dont delete the route
     then the host address is unreachable (you get an arpresolve error).
*/

Dennis
----------------------------------------------------------------------------
Emerging Technologies, Inc.      http://www.etinc.com

Synchronous Communications Cards and Routers For
Discriminating Tastes. 56k to T1 and beyond. Frame
Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD 
and LINUX