>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
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        1.5.1 branch from 2001-05-24
>Organization:
Matthias Scheler                                  http://scheler.de/~matthias/
>Environment:
System: NetBSD colwyn.zhadum.de 1.5.1_BETA2 NetBSD 1.5.1_BETA2 (COLWYN) #0: Thu May 24 14:24:48 CEST 2001 tron@colwyn.zhadum.de:/src/sys/compile/COLWYN i386

>Description:
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		192.168.1.1	FDDI
			192.168.2.1	Ethernet

ULTRA 10		192.168.2.10	Ethernet

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

name-of-ultra10		domain.tld	192.168.1.1
					^^^^^^^^^^^

I could work arroud the problem by starting "rpc.bootparamd" with
"-r 192.168.2.1". 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.

>How-To-Repeat:
Use "rpc.bootparamd" on a multi homed NetBSD system and try to boot
Solaris installation from it.

>Fix:
None provided yet.

>Release-Note:
>Audit-Trail:
>Unformatted: