From mpp@mpp.com  Tue Apr 11 02:47:58 1995
Received: from mpp.com (dialup-2-150.gw.umn.edu [134.84.101.150])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA17645
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 11 Apr 1995 02:47:55 -0700
Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id EAA00290; Tue, 11 Apr 1995 04:46:56 -0500
Message-Id: <199504110946.EAA00290@mpp.com>
Date: Tue, 11 Apr 1995 04:46:56 -0500
From: pritc003@maroon.tc.umn.edu
Reply-To: pritc003@maroon.tc.umn.edu
To: FreeBSD-gnats-submit@freebsd.org
Subject: Incorrect routes can cause system to reset
X-Send-Pr-Version: 3.2

>Number:         332
>Category:       kern
>Synopsis:       Incorrect routes can cause system to reset
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 11 02:50:00 1995
>Closed-Date:    Sat Jul 8 18:56:24 MET DST 1995
>Last-Modified:
>Originator:     Mike Pritchard
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
>Environment:

System configured with 1 SLIP interface and 1 PPP interface.  IPFIREWALL
and MROUTING are configured.  No other network devices are configured
or present.

>Description:

Under certain conditions, an incorrect routing setup can cause the
system to reset (no panic, a reset just like you hit the reset button).
Any attempt to communicate with the newtwork (ping, netstat -r, telnet,
whatever) when this route setup exists will cause the machine to reset.

I also saw this when running with the 2.0R system when I was initially
setting up my machine, but forgot about it until just now when I screwed 
something up in a config file tonight and caused it to happen again.

>How-To-Repeat:


(the SLIP interface is NOT connected, and does not need to be to
duplicate the problem)

# ifconfig sl0
sl0: flags=c011<POINTOPOINT,LINK2,MULTICAST> mtu 552
	inet 172.16.0.1 --> 128.101.118.21 netmask 0xffffff00 
# netstat -rn
Routing tables

Internet:
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]

Right after a fresh reboot, the routing table looks like:
# netstat -rn
Routing tables

Internet:
Destination      Gateway            Flags     Refs     Use     Netif Expire
127.0.0.1        127.0.0.1          UH          0        0       lo0
128.101.118.21   172.16.0.1         UH          0       15       sl0
172.16.0.1       127.0.0.1          UH          0        0       lo0
224              172.16.0.1         US          0        0       sl0

I did the following to change the above routes into the routes that cause
the problem:

route delete 128.101.118.21 172.16.0.1
route add default 128.101.118.21

>Fix:
	
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Sat Jul 8 18:56:24 MET DST 1995 
State-Changed-Why:  
From mpp@legarto.minn.net (Mike Pritchard): 

Another of my own PRs.  This is fixed in -current.  I think rev 1.22  
of sys/net/route.c was the change that fixed this. 

>Unformatted:



