Subject: bin/13197: rpc.bootparamd missbehaves on multi homed system
To: None <>
From: Matthias Scheler <>
List: netbsd-bugs
Date: 06/14/2001 02:24:03
>Number:         13197
>Category:       bin
>Synopsis:       rpc.bootparamd missbehaves on multi homed system
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 13 17:22:00 PDT 2001
>Release:        1.5.1 branch from 2001-05-24
Matthias Scheler                        
System: NetBSD 1.5.1_BETA2 NetBSD 1.5.1_BETA2 (COLWYN) #0: Thu May 24 14:24:48 CEST 2001 i386

When I tried to netboot a ULTRA10 with Solaris from a NetBSD server I got
several panics because the U10 couldn't mount the root partition. After
using the debugging mode of "rpc.bootparamd" I found out that it was
sending out the IP address of the wrong interface to the client as
router address. So the scenario looks like this:

NetBSD box	FDDI	Ethernet

ULTRA 10	Ethernet

And the NetBSD box answer the "whoami" request like this:

name-of-ultra10		domain.tld

I could work arroud the problem by starting "rpc.bootparamd" with
"-r". However, that doesn't work if there are net install
or net boot clients on both subnets. So "rpc.bootparamd" should be
fixed to recognize which of its IP address is local to the client.

Use "rpc.bootparamd" on a multi homed NetBSD system and try to boot
Solaris installation from it.

None provided yet.