From owner-freebsd-net@FreeBSD.ORG Thu Oct 23 11:47:34 2003 Return-Path: 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 EE5C516A4B3 for ; Thu, 23 Oct 2003 11:47:34 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 522BA43F3F for ; Thu, 23 Oct 2003 11:47:34 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id 7E96472DA0; Thu, 23 Oct 2003 11:41:01 -0700 (PDT) From: Wes Peters Organization: Softweyr To: Charles Swiger , net@freebsd.org Date: Thu, 23 Oct 2003 11:45:04 -0700 User-Agent: KMail/1.5.4 References: <109F1559-0586-11D8-92E1-003065ABFD92@mac.com> In-Reply-To: <109F1559-0586-11D8-92E1-003065ABFD92@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310231145.04241.wes@softweyr.com> Subject: Re: Help Broadcasting a UDP packet on the LAN:URGENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2003 18:47:35 -0000 On Thursday 23 October 2003 11:23 am, Charles Swiger wrote: > On Thursday, October 23, 2003, at 11:52 AM, Barney Wolff wrote: > > On Thu, Oct 23, 2003 at 01:55:55AM -0700, Wes Peters wrote: > > [ ... ] > > > What are you going to do when IPv6 comes into more general use, since > > it has no broadcast address? > > Are you asking what a IPv4-to-IPv6 translator (like gif?) should do, or > are you worried about the case of a machine configured for IPv6 only > and not for IPv4? I expect that most people will be using IPv4 for > quite some time; we don't have to do something for the IPv6-only case > to still have this be useful. Porting broadcast applications to IPv6 requires re-thinking the problem, because IPv6 sheds some of the problems of IPv4 and introduces a few of it's own. Address assignment, for instance, is much less a problem in IPv6, but not having the addresses centrally managed (by either a program or a human) introduces it's own difficulties. > > The whole VLAN thing is nasty, but I'd say that the general issue is > > does the box itself have a virtual interface on the VLAN, or is it > > merely switching on it. If the former, you send packets and process > > received packets up the stack. If the latter, you just do what any > > switch/bridge would do, because "you" (ie, higher layers) are not > > really > > on that layer-3 network. > > The all-ones broadcast is supposed to go to all physically connected > network segments, regardless of whether a particular interface is > ifconfig'ured with an IP that is part of a particular layer-3 subnet. > You should be able to send the broadcast packet out from an interface > which is up but does not have an IPv4 address assigned, right? So long as it IS configured with the IPv4 protocol, I'd say yes. Ditto for VLANs. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com