From owner-freebsd-net@FreeBSD.ORG  Thu Jan  8 22:39:12 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0102D106570C
	for <freebsd-net@freebsd.org>; Thu,  8 Jan 2009 22:39:12 +0000 (UTC)
	(envelope-from psteele@maxiscale.com)
Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136])
	by mx1.freebsd.org (Postfix) with ESMTP id D0D7F8FC2F
	for <freebsd-net@freebsd.org>; Thu,  8 Jan 2009 22:39:11 +0000 (UTC)
	(envelope-from psteele@maxiscale.com)
X-ASG-Debug-ID: 1231454349-57d300010000-QdxwpM
X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi
Received: from polaris.maxiscale.com (localhost [127.0.0.1])
	by arcturus.maxiscale.com (Spam Firewall) with ESMTP
	id 78424366C0; Thu,  8 Jan 2009 14:39:09 -0800 (PST)
Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by
	arcturus.maxiscale.com with ESMTP id XHExhZgw8FYpbsN9;
	Thu, 08 Jan 2009 14:39:09 -0800 (PST)
X-ASG-Whitelist: Client
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-ASG-Orig-Subj: RE: Having problems with limited broadcast
Date: Thu, 8 Jan 2009 14:39:07 -0800
Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com>
In-Reply-To: <d763ac660901081411l59120580yb4919a16b451e3ee@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Having problems with limited broadcast
Thread-Index: Aclx3hWiEudBfLJiRHilVcw/tD/C1gAAzApQ
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>
From: "Peter Steele" <psteele@maxiscale.com>
To: "Adrian Chadd" <adrian@freebsd.org>
X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24]
X-Barracuda-Start-Time: 1231454349
X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com
Cc: freebsd-net@freebsd.org
Subject: RE: Having problems with limited broadcast
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2009 22:39:12 -0000

>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...