From owner-freebsd-hackers Sun Oct 28 20:16:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 9F9E637B403; Sun, 28 Oct 2001 20:16:23 -0800 (PST) Received: from NDNM ([195.161.98.250]) by ns.morning.ru (8.11.5/8.11.5) with ESMTP id f9T4GLF22917; Mon, 29 Oct 2001 11:16:21 +0700 (KRAT) Date: Mon, 29 Oct 2001 11:16:54 +0700 From: Igor Podlesny X-Mailer: The Bat! (v1.53d) UNREG / CD5BF9353B3B7091 Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <136143454376.20011029111654@morning.ru> To: freebsd-hackers@FreeBSD.ORG Subject: ip_icmp.c's ancient bug-feature (fixed) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! Really micro patch :-) fixing odd behavior (well, in fact, I deem an error) of FreeBSD' ip_icmp.c. You might observe this bug doing traceroute while standing behind a GW's interface with several IP-addresses (aliases). In this case you always got ICMP.TIMXCEED (time exceeded) coming from IP-address which is the first on the interface, even if your box is not using this IP-address as its next-hop. Despite of the code selecting right IP-address for this purpose is working well it's being confused by wrong argument it is being given. This patch http://www.morning.ru/~poige/patchzone/ip_icmp.c.diff fixes namely this problem. P.S. It seems the same problem belongs to OpenBSD and, may be, for all *BSD derivatives. P.P.S. the PR is already sent, now waiting... -- Best regards, Igor. http://morning.ru/~poige To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message