From owner-freebsd-bugs Tue Jul 7 07:19:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02829 for freebsd-bugs-outgoing; Tue, 7 Jul 1998 07:19:45 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02821 for ; Tue, 7 Jul 1998 07:19:41 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id HAA24496; Tue, 7 Jul 1998 07:14:33 -0700 (PDT) Message-Id: <199807071414.HAA24496@implode.root.com> To: Samuel S Thomas cc: Poul-Henning Kamp , freebsd-bugs@FreeBSD.ORG Subject: Re: kern/7191: FreeBSD 2.2.6 generates Source-route prohibited when not routing In-reply-to: Your message of "Tue, 07 Jul 1998 13:09:18 -0000." <19980707130918.F13836@lart.net> From: David Greenman Reply-To: dg@root.com Date: Tue, 07 Jul 1998 07:14:33 -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> It happened to me some years ago... >> >> Could also be a defect card of course. > >defect card would not excuse the kernel generating ICMP messages without >verifying destination address. this is clearly a layer 2(TCP/IP 4-layer >model) or layer 3 (7-layer OSI model) problem. No, it's not that clear. First of all, since the IP source/destination of the packets is never that of the intermediate routers one can't compare against that. The problem is that the machine is seeing the packets in the first place. FreeBSD, and all other Unixes that I know about, only verify the destination MAC address as being 'this host' when the interface is put into promiscuous mode. Otherwise it assumes that the hardware is properly filtering the packets. For whatever reason, the interface is passing packets that it should not be passing and there is no way to tell the difference between that and a machine deliberating sending the packets to the host as if to be routed. It is probably a bug that source route IP options are processed at all when a machine isn't configured for IP forwarding. While fixing this would supress your warnings, it wouldn't fix the real problem which is why the machine is seeing the packets in the first place. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message