From owner-freebsd-net@FreeBSD.ORG Wed Jul 9 00:19:52 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 0DD5E37B401 for ; Wed, 9 Jul 2003 00:19:52 -0700 (PDT) Received: from maillog.itri.org.tw (dnss.itri.org.tw [210.68.176.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA8CC43FCB for ; Wed, 9 Jul 2003 00:19:48 -0700 (PDT) (envelope-from mtlin1@ms36.hinet.net) Received: from mail.itri.org.tw (mail [140.96.157.2]) by maillog.itri.org.tw (8.11.6+Sun/8.11.6) with ESMTP id h696p3c00488; Wed, 9 Jul 2003 14:51:03 +0800 (CST) Received: from ms2.itri.org.tw ([140.96.151.157]) by mail.itri.org.tw (8.11.6+Sun/8.11.6) with ESMTP id h696jXF08976; Wed, 9 Jul 2003 14:45:34 +0800 (CST) Received: from mtlin ([140.96.254.153]) by ms2.itri.org.tw (Lotus Domino Release 5.0.11) with ESMTP id 2003070914493719:14589 ; Wed, 9 Jul 2003 14:49:37 +0800 Message-ID: <01cc01c345e5$ff91abf0$3c55608c@mtlin> From: "Morton Lin" To: "Bruce M Simpson" References: Date: Wed, 9 Jul 2003 14:47:37 +0800 MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MIMETrack: Itemize by SMTP Server on MS2/ITRI(Release 5.0.11 |July 24, 2002) at 2003-07-09 02:49:37 PM,2003-07-09 02:49:41 PM, Serialize complete at 2003-07-09 02:49:41 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="big5" cc: freebsd-net@freebsd.org Subject: Re: AODV RFC is now ratified X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Morton Lin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 07:19:52 -0000 Hi, Sir : I am very interesting in your post. Would you please give me some web pages or information about your brief FreeBSD Howto ? I had built a ad-hoc testbed by using CMU's Monarch DSR implementation. But it's buggy. In 802.11 environment our platform didn't work very well. And I had done simulation for DSR and AODV in OPNET. It seems the performance of AODV was better. Anyway, It's happy to see Perkins and folks make it. :-) PS : Do you ever think the possibility that those ad-hoc routing protocol stack running over Bluetooth environment ? Best Regards, Morton Lin. ----- Original Message ----- From: "Bruce M Simpson" Newsgroups: mailing.freebsd.net Sent: Tuesday, July 08, 2003 10:34 PM Subject: AODV RFC is now ratified > On Tue, Jul 08, 2003 at 08:13:03AM -0600, M. Warner Losh wrote: > > Cool! Hopefully this work will include fixing lucent cards too :-) > > Hail Eris. All hail Discordia. > > By the way, have you seen RFC 3561? It's just out. > > http://www.faqs.org/rfcs/rfc3561.html > Ad hoc On-Demand Distance Vector (AODV) Routing > > I'm putting together a brief FreeBSD HOWTO -- 'On-demand Routing with > XRESOLVE for Dummies' -- hinted at by fenestro. My technique is quite > simple, I create a CLONE+XRESOLVE route pointing to disc0 (to avoid > routing loops when ip forwarding is enabled) for the route(s) intended > to use the wireless cloud as a next-hop, then listen for RTM_RESOLVE > messages when the stack tries to use those route entries to clone routes > from. That then enables our hypothetical aodvd to issue RTM_CHANGE to > route the data to its peer. Seems pretty clean. > > We can of course tweak the net.inet.ip.rt* cache tunables to prevent > the stack getting swamped with stale wireless routes. > > I may not be able to get AODV all done on my own, but I may have a crack > at it - have a lot on my plate just now. > > BMS > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"