On Tue, Oct 30, 2001 at 01:40:27PM -0500, Logan Bowers wrote:
> You need to set your broadcast address to 255.255.255.255 on you server
> machine.  If you look at the tcpdump, the bootparm requests are being
> sent there.  

This sounds more like a hack than a solution.
The interface has the right broadcast configured and I need to keep
this for not breaking rwhod & co.
255.255.255.255 is an implied broadcast for every ip machine.
If that is disabled per default there should be a knob to reenable.

But in fact the ip itself works fine:
ticso@cicely21# ping 255.255.255.255
PING 255.255.255.255 (255.255.255.255): 56 data bytes
64 bytes from 10.1.1.23: icmp_seq=0 ttl=255 time=1.446 ms
64 bytes from 10.1.1.22: icmp_seq=0 DUP! ttl=255 time=4.254 ms
64 bytes from 10.1.1.9: icmp_seq=0 DUP! ttl=255 time=5.932 ms
64 bytes from 10.1.1.24: icmp_seq=0 DUP! ttl=255 time=7.181 ms
64 bytes from 10.1.1.43: icmp_seq=0 DUP! ttl=255 time=8.451 ms
[...]

From what I see is that either bootparamd or rpcbind are failing
to handle these IPs.

-- 
B.Walter              COSMO-Project         http://www.cosmo-project.de
ticso@cicely.de         Usergroup           info@cosmo-project.de