From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 24 01:49:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E92F416A50D; Wed, 24 Nov 2004 01:49:20 +0000 (GMT) Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com [65.124.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DD4343D2D; Wed, 24 Nov 2004 01:49:20 +0000 (GMT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id B12B82F93F; Tue, 23 Nov 2004 20:49:19 -0500 (EST) Date: Tue, 23 Nov 2004 20:49:19 -0500 From: James To: Martin Eugen , freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20041124014919.GA9396@scylla.towardex.com> References: <966ba91e04112301052fed8d6b@mail.gmail.com> <20041123183646.GB733@empiric.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041123183646.GB733@empiric.icir.org> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Wed, 24 Nov 2004 13:26:03 +0000 Subject: Re: resolving routes externally X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 01:49:21 -0000 On Tue, Nov 23, 2004 at 10:36:46AM -0800, Bruce M Simpson wrote: [ snip ] > > If I understand correctly, you want the kernel to queue packets until > layer 2 address resolution is complete. Right now we don't do this. If > there is no route to a destination, packets will be dropped. The KAME ipv6 code does this for v6 neighbor discovery (which is not arp yes..). Martin, nd6_output() in netinet6/nd6.c should be helpful if you want to look. RFC requires routers to queue packets up during layer 2 resolution process (which is why in IPv6 when destination host is down you see !A with huge latency -- i.e. 3400ms due to queueing by the router[1]). If you are queueing however, make sure you use locking or check for any safety mechanisms as you may corrupt mbuf's that are flooding inbound. BTW Martin,, what is the purpose of this intent? Just curiousity of mine. [1]: Some hardware/ASIC based routers violate the RFC unfortunately. It's a little harder to implement there (see J vendor) -J -- James Jun TowardEX Technologies, Inc. Technical Lead Boston IPv4/IPv6 Web Hosting, Colocation and james@towardex.com Network design/consulting & configuration services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net