On Tue, Jul 15, 2003 at 03:48:48PM -0700, Wes Peters wrote: > > It's a broadcast, the socket isn't bound to an interface. ;^) > > The idea is, we have listener on each ethernet interface listening via a > bpf. The listener listens for an 'appliance discovery' packet which is > broadcast by the console application running on the admin's > workstation. When we receive this discovery packet, we're supposed to > reply back with a broadcast packet that says 'here I am' so the console > can get our MAC address. The console application does some special > h0h0 magic of it's own then sends us back another broadcast message > that has IP addresses for all 3 interfaces. > > It's a wonderful idea but it doesn't work. This seems in keeping with > the spirit of BOOTP, DHCP, et al, but is explicitly designed to assign > a permanent address to an appliance that cannot know it's boot address > when configured and cannot really predict which of the 3 interfaces it > might receive an address from.
I don't quite know why you need to reinvent bootp/dhcp, but adapting the isc-dhcp code would solve your problem without needing kernel mods. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
