From owner-freebsd-net@FreeBSD.ORG  Wed Jul  2 00:19:30 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 C47B337B404
	for <freebsd-net@freebsd.org>; Wed,  2 Jul 2003 00:19:30 -0700 (PDT)
Received: from mailman.research.att.com (H-135-207-24-32.research.att.com
	[135.207.24.32])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D6D1843FA3
	for <freebsd-net@freebsd.org>; Wed,  2 Jul 2003 00:19:29 -0700 (PDT)
	(envelope-from fenner@research.att.com)
Received: from unixmail.research.att.com (unixmail.research.att.com
	[135.207.26.71])h627Cu3j030951;	Wed, 2 Jul 2003 03:12:56 -0400
Received: from windsor.research.att.com (windsor.research.att.com
	[135.207.26.46])h627HZXs020163;	Wed, 2 Jul 2003 03:17:35 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id h627JSB02890;
	Wed, 2 Jul 2003 00:19:28 -0700 (PDT)
Message-Id: <200307020719.h627JSB02890@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: mgrooms@shrew.net
Date: Wed, 2 Jul 2003 00:19:27 -0700
Versions: dmail (solaris) 2.5a/makemail 2.9d
cc: freebsd-net@freebsd.org
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 <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: Wed, 02 Jul 2003 07:19:31 -0000


The short answer is no, you can't, in_pcb turns 255.255.255.255 into
the "primary" interface's broadcast address.

I doubt this is actually useful behavior, but that's not what you
asked =)

  Bill