From owner-freebsd-net@FreeBSD.ORG Fri Jul 11 17:23:38 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 DB70537B401; Fri, 11 Jul 2003 17:23:38 -0700 (PDT) Received: from mail.redlinenetworks.com (mail.redlinenetworks.com [216.136.145.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BF9143F85; Fri, 11 Jul 2003 17:23:38 -0700 (PDT) (envelope-from sreekanth@redlinenetworks.com) Received: from SREELAPTOP (dhcp-174.redlinenetworks.com [192.168.40.174]) h6C0NcV14482; Fri, 11 Jul 2003 17:23:38 -0700 (PDT) (envelope-from sreekanth@redlinenetworks.com) From: "Sreekanth" To: "'Wes Peters'" , "'Don Lewis'" Date: Fri, 11 Jul 2003 17:23:39 -0700 Message-ID: <000001c3480b$d8032230$ae28a8c0@SREELAPTOP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <200307111702.36633.wes@softweyr.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2003 00:23:39 -0000 That brings an interesting topic.If the Interface has not been assigned an IP address.The Interface is NOT initialized.So you cannot really use the interface.Ofcourse you can bypass this by hacking into driver.But do you want to do that is another questions. Just my 2 cents Sreekanth > -----Original Message----- > From: Wes Peters [mailto:wes@softweyr.com] > Sent: Friday, July 11, 2003 5:03 PM > To: Sreekanth; 'Don Lewis' > Cc: mgrooms@shrew.net; freebsd-net@freebsd.org > Subject: Re: broadcast udp packets ... > > > 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 > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.495 / Virus Database: 294 - Release Date: 6/30/2003 > >