From owner-freebsd-net@FreeBSD.ORG Tue Jul 15 19:15:48 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEF3137B401 for ; Tue, 15 Jul 2003 19:15:48 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0405243F85 for ; Tue, 15 Jul 2003 19:15:48 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6G2Fln8098799; Tue, 15 Jul 2003 22:15:47 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6G2FlII098798; Tue, 15 Jul 2003 22:15:47 -0400 (EDT) (envelope-from barney) Date: Tue, 15 Jul 2003 22:15:47 -0400 From: Barney Wolff To: Wes Peters Message-ID: <20030716021546.GB98170@pit.databus.com> References: <200307151709.h6FH9UOW055742@hole.shrew.net> <200307151548.48778.wes@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307151548.48778.wes@softweyr.com> User-Agent: Mutt/1.4.1i cc: "freebsd-net@freebsd.org" cc: Matthew Grooms Subject: Re: broadcast udp packets ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 02:15:49 -0000 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.