From owner-freebsd-net Sat Oct 9 22:25:52 1999 Delivered-To: freebsd-net@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 9F08014D7F for ; Sat, 9 Oct 1999 22:24:38 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 11aBUL-0002ML-00; Sun, 10 Oct 1999 01:25:41 -0400 To: Mohit Aron Cc: freebsd-net@freebsd.org From: "Gary Palmer" Subject: Re: arp errors on machines with two interfaces In-reply-to: Your message of "Sat, 09 Oct 1999 11:50:51 CDT." <199910091650.LAA08261@cs.rice.edu> Date: Sun, 10 Oct 1999 01:25:38 -0400 Message-ID: <9072.939533138@noop.colo.erols.net> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mohit Aron wrote in message ID <199910091650.LAA08261@cs.rice.edu>: > I don't have control over the hardware. But here's a possibility - > wouldn't it be better if this error message generation in FreeBSD is > turned off if the packet is an arp broadcast ? Like I showed in my > earlier mail, the problem only happens due to arp broadcasts. Turning it off for ARP broadcasts would defeat the purpose of the message, which is to alert the user to a broken network layout, or someone attempting to steal your traffic. I'd much rather you fix your network layout (e.g. by putting the RFC1918 network on a seperate VLAN on the switch) rather than trying to change FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message