From owner-freebsd-net@FreeBSD.ORG Sun Jan 16 02:45:06 2005 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 6C21B16A4CF for ; Sun, 16 Jan 2005 02:45:06 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 090D743D39 for ; Sun, 16 Jan 2005 02:45:06 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-208-232.ny325.east.verizon.net [68.160.208.232]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0G2iv5U065962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jan 2005 21:44:58 -0500 (EST) Message-ID: <41E9D59E.2040504@mac.com> Date: Sat, 15 Jan 2005 21:46:54 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julien Lesaint References: <20050116014706.GD28728@titoon.net> In-Reply-To: <20050116014706.GD28728@titoon.net> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: freebsd-net@freebsd.org Subject: Re: ttl-exceeded sourced by arrival interface ? 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: Sun, 16 Jan 2005 02:45:06 -0000 Julien Lesaint wrote: > Quick reminder: in the case the route to the packet's source is not the > interface this packet arrived on, do we have a way to source ICMP errors > (ttl-exceeded) with the original interface's IP address ? Yes. Use IPFW's fwd mechanism, or even set a host route for the source IP address pointing to whichever interface you please. > Currently the box is sending ttl-exceeded with the IP address of the > interface the route to the sender is pointing at. That's what the routing table is supposed to do, yes. -- -Chuck