Date: Thu, 8 Jan 2009 14:39:07 -0800 From: "Peter Steele" <psteele@maxiscale.com> To: "Adrian Chadd" <adrian@freebsd.org> Cc: freebsd-net@freebsd.org Subject: RE: Having problems with limited broadcast Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> In-Reply-To: <d763ac660901081411l59120580yb4919a16b451e3ee@mail.gmail.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> <d763ac660901081411l59120580yb4919a16b451e3ee@mail.gmail.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..) It's really a matter of time. We didn't anticipate limited broadcast being broken in FreeBSD and we're scrambling to come up with a solution. To be quite frank I haven't done anything with IPv6 before so it would be more research to get up to speed on this option. It seems our best option is scapy, which unfortunately I also haven't used before...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9>