Date: Mon, 3 Feb 1997 07:22:00 -0800 (PST) From: Christopher Warth <csw@gated.epigram.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/2647: changing existing route to -static crashes kernel Message-ID: <199702031522.HAA00264@gated.epigram.com> Resent-Message-ID: <199702032200.OAA23335@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2647
>Category: kern
>Synopsis: changing existing route to -static crashes kernel
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Feb 3 14:00:01 PST 1997
>Last-Modified:
>Originator: Christopher Warth
>Organization:
Epigram.com
>Release: FreeBSD 2.1-STABLE i386
>Environment:
2.1-STABLE running on a Dell 200Mhx pentium (model Dimension XPSPro 200 n).
2 x 3Com 3c595 Fast EtherLink III PCI
kernel option GATEWAY turned on
ipfilt 3.1.5 installed a s loadable module.
>Description:
Using the "change" command to add the "-static" flag to
an existing route on the local ethernet will always crash the machine.
In fact there are a great number of parameters to "route" that will
instantly crash the machine. This is the most repeatable example
though.
>How-To-Repeat:
Do a "netstat -rn" and choose a route to a machine on your
local network that has been resolved to a machine address. For
example on my local network I chose the following entry:
199.2.31.1 0:0:c:76:30:3d UHLW 1 0 vx0 76
Now change this route to be static.
route change 199.2.31.1 -static
Bang! machine crashes with a "page fault in kernel mode" error..
>Fix:
No workaround known. Perhaps a periodic ping would be enough
to keep this routing entry from expiring.
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702031522.HAA00264>