From owner-freebsd-net@FreeBSD.ORG Thu Dec 9 04:02:54 2004 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 9CA1116A4CE; Thu, 9 Dec 2004 04:02:54 +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 75FA243D46; Thu, 9 Dec 2004 04:02:54 +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 EA1682F946; Wed, 8 Dec 2004 23:02:53 -0500 (EST) Date: Wed, 8 Dec 2004 23:02:53 -0500 From: James To: Andre Oppermann , Michal Mertl , freebsd-net@freebsd.org, Robert Watson Message-ID: <20041209040253.GA2417@scylla.towardex.com> References: <41B714DA.6090505@traveller.cz> <41B71553.278B66A4@freebsd.org> <20041209022107.GB691@empiric.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209022107.GB691@empiric.icir.org> User-Agent: Mutt/1.4.1i Subject: Re: New ICMP limits 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, 09 Dec 2004 04:02:54 -0000 On Wed, Dec 08, 2004 at 06:21:07PM -0800, Bruce M Simpson wrote: > On Wed, Dec 08, 2004 at 03:53:07PM +0100, Andre Oppermann wrote: > > I'll take care of this but I'm busy right now. Look into it later this week. > > Thanks for looking into this, this is one of the items which came up on > the TODO lists of three separate projects (TowardEX's, XORP's, and the > Network Junta's). If you aren't able to look at it let us know so someone > else can step up to the mic. > > Of course, the sooner we can remove ARP's special meaning from RTF_REJECT, > the better - that would let us implement RTF_REJECT in the fastforwarding > path without further worry. When we have routing table cleaned up (e.g. remove arp off of it), I'll look into getting out some patch for installing /32 host routes for all receive-adjacent addresses. This way we don't have to run a hash lookup at ip_fastforward() to find out whether address belongs to us. We can simply either route it to lo0 as a receive-path (like in Cisco GSR/7500 rcvpath and Juniper loopback path) or send it to a separate input handling routine with packet filtering before returning to ip_input. Unless ofcourse, someone already has it made up and ready to go -- in that case there is no need ;) Thanks, -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