Date: Thu, 8 Jan 2009 17:11:39 -0500 From: "Adrian Chadd" <adrian@freebsd.org> To: "Peter Steele" <psteele@maxiscale.com> Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast Message-ID: <d763ac660901081411l59120580yb4919a16b451e3ee@mail.gmail.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If this is all going over an L2 LAN, why not do the initial discovery and general configuration exchange over IPv6? :P Link layer network-scope addresses to the rescue. (think: just like apple wireless base stations and MacOSX hosts doing configuration do..) Adrian 2009/1/8 Peter Steele <psteele@maxiscale.com>: >> Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll >> check it out. > > ZeroConf is an interesting concept. Unfortunately it restricts IPs to > the 169.254/16 range and it is very likely some of our customers will > want to be able to configure our boxes to an IP range of their own > choosing. That's the biggest concern we have with this facility. It's > definitely attractive, but I don't think we can use unfortunately. > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660901081411l59120580yb4919a16b451e3ee>