From owner-freebsd-net@FreeBSD.ORG  Fri Jul 11 17:02:39 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 EF37F37B401; Fri, 11 Jul 2003 17:02:39 -0700 (PDT)
Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 826C843F75; Fri, 11 Jul 2003 17:02:39 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from salty.rapid.stbernard.com (corp-2.ipinc.com [199.245.188.2])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 062291B314; Fri, 11 Jul 2003 17:02:37 -0700 (PDT)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr.com
To: "Sreekanth" <sreekanth@redlinenetworks.com>,
	"'Don Lewis'" <truckman@freebsd.org>
Date: Fri, 11 Jul 2003 17:02:36 -0700
User-Agent: KMail/1.5.2
References: <000001c347f2$6c2ca9f0$ae28a8c0@SREELAPTOP>
In-Reply-To: <000001c347f2$6c2ca9f0$ae28a8c0@SREELAPTOP>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307111702.36633.wes@softweyr.com>
cc: freebsd-net@freebsd.org
cc: mgrooms@shrew.net
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: Sat, 12 Jul 2003 00:02:40 -0000

On Friday 11 July 2003 14:21, Sreekanth wrote:
> Couldn't it be done just by executing the following command ?
> #route add 255.255.255.255 -net 255.255.255.255 -ifp [primary
> interface]
>
> I know it is kind of crude but it works in my case :-)

In our case, it's being run before *any* interface has an IP address, so 
the routing table is completely empty.  Yes, it's obviously part of a 
device discovery phase, and we could do some special ethernet level 
h0h0magic but we don't want to, we want broadcasting to work. ;^)

-- 
         "Where am I, and what am I doing in this handbasket?"

Wes Peters                                              wes@softweyr.com