NetBSD Problem Report #6968

Received: (qmail 13379 invoked from network); 8 Feb 1999 16:33:32 -0000
Message-Id: <199902081633.IAA03278@nooksack.ldc.cs.wwu.edu>
Date: Mon, 8 Feb 1999 08:33:00 -0800 (PST)
From: Lemm@stud-mailer.uni-marburg.de
To: gnats-bugs@gnats.netbsd.org
Subject: bootp reboots machine when confronted with non existant hostname
X-Send-Pr-Version: www-1.0

>Number:         6968
>Category:       bin
>Synopsis:       bootp reboots machine when confronted with non existant hostname
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          dead
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 08 08:35:00 +0000 1999
>Closed-Date:    Sat May 03 02:34:47 +0000 2008
>Last-Modified:  Sat May 03 02:34:47 +0000 2008
>Originator:     Thomas Lemm
>Release:        1.3.3
>Organization:
University of Marburg
>Environment:
No output but:

netbsd 1.3.3
pmax - machine (DEC personal Workstation 5000-25)

>Description:
The Machine serves as bootp server for various diskless clients already
without problem. To make it bootp server I enabled bootp services in 
/etc/inittab (It gives the bootp server root priorities and I left 
it that way) 

Then I wanted to add yet another diskless client:  
I added its ethernet address and various other info about the client
to /etc/bootptab and gave it a name that was not present in my 
/etc/hosts file and thus could not be resolved.

Then I started the diskless client. - The bootp server rebooted. 
In /var/log/messages there were lines from bootp inidicating the 
problem that the given host name was not known by the system,
followed by the reboot-message.
>How-To-Repeat:
Restart the diskless client
>Fix:
add the name and IP of the diskless client to the /etc/hosts file.


If you need more info about the bug and the machine please email.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: port-mips-maintainer->bin-bug-people 
Responsible-Changed-By: kleink 
Responsible-Changed-When: Tue Feb 8 07:43:33 PST 2000 
Responsible-Changed-Why:  
Category changed from port-mips to bin, which is appropriate. 
State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 28 Apr 2008 04:24:05 +0000
State-Changed-Why:
(1) have you seen this problem again with a more recent NetBSD?
(2) in order to figure out what might have happened we'll need more
    information. There's no plausible way bootpd itself could reboot
    a system; best guess is that either it did something bad to one of
    the network drivers, or send a bogus address to the other machine
    which then sent packets that caused a crash. When you say the
    "reboot message", do you mean a message from reboot(8) or shutdown(8),
    or just the first kernel messages from a fresh boot?


State-Changed-From-To: feedback->dead
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 03 May 2008 02:34:47 +0000
State-Changed-Why:
feedback mail bounced, and not enough information to even try reproducing.


>Unformatted:

Home	PR Database Search