Date: Wed, 18 Aug 1999 12:02:03 -0700 (PDT)
From: colle@krtkg1.rug.ac.be
To: freebsd-gnats-submit@freebsd.org
Subject: kern/13232: panic("rtfree"); when sending bootp requests to machine
Message-ID: <19990818190203.7D5EF157EF@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 13232
>Category: kern
>Synopsis: panic("rtfree"); when sending bootp requests to machine
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Aug 18 12:10:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Christophe Colle
>Release: 3.2-RELEASE.
>Organization:
>Environment:
FreeBSD portable.is.cool 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Sun Aug 15 20:59:50 CEST 1999 root@portable.is.cool:/usr/src/sys/compile/PORTABLE i386
>Description:
Machine crashes when sending bootp-packets to a machine,
without a defaultroute and where the entry for the bootpclient
is not complete (incomplete in the sense that the hostname could not
be resolved to a valid ip-address)
>How-To-Repeat:
1) enable bootp-service in /etc/inetd
2) create the following /etc/bootptab
mopie:ha=0000e8543231:bf=init:dn=test.net:ds=192.168.1.1:rp=/usr/path:sa=192.168.1.1
3) make sure 'mopie' cannot be resolved
4) delete default route: route delete default
5) let bootpclient mopie send some bootprequests
and enjoy the core ;-)
I've seen the same behavior for FreeBD-2.2.6 and FreeBSD-4.0-19990307-SNAP
>Fix:
temporary fix: add a default route, or make sure you don't mistype
hostnames ;-)
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990818190203.7D5EF157EF>