Date: Wed, 07 Jan 2009 10:28:46 -0500 From: Bruce Walker <bmw@wezel.com> To: Peter Steele <psteele@maxiscale.com> Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast Message-ID: <4964CA2E.5090708@wezel.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Steele wrote: > When our boxes are initially deployed, they have no IP addresses > assigned to them. Their ifconfig entry looks like this: > > ifconfig_lagg0="laggproto failover laggport nfe0 laggport nfe1" > > With this config, no IP is assigned to the lagg0 device, so the only way > to access the boxes is via a serial console. Peter, leaving aside the issue of FreeBSD limited broadcast, have you considered ZeroConf, and in particular the IPv4 Link-Level Addressing portion of it to meet your basic "get the boxes addressed" requirement? http://www.zeroconf.org/ http://files.zeroconf.org/rfc3927.txt I don't have any experience with the lagg device yet, so I don't know if that presents specific issues wrt ipv4ll code. -bmw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4964CA2E.5090708>