From owner-freebsd-questions Thu Nov 14 15:03:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15380 for questions-outgoing; Thu, 14 Nov 1996 15:03:08 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA15353 for ; Thu, 14 Nov 1996 15:02:57 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id PAA00752 for ; Thu, 14 Nov 1996 15:02:46 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14924(6)>; Thu, 14 Nov 1996 15:00:56 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177557>; Thu, 14 Nov 1996 15:00:52 -0800 X-Mailer: exmh version 1.6.7 5/3/96 To: Seppo Kallio cc: freebsd-questions@freebsd.org Subject: Re: arp info overwritten In-reply-to: Your message of "Thu, 14 Nov 1996 04:20:01 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Nov 1996 15:00:51 PST From: Bill Fenner Message-Id: <96Nov14.150052pst.177557@crevenia.parc.xerox.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message you write: >3. Can I dissable this overwriting somehow? How? You can build a new kernel with arp overwriting disabled; in sys/netinet/if_ether.c, change the "log(LOG_INFO, "arp info overwritten..." into "goto out". This is probably the wrong thing to do. >This problem and error message appears only in the FreeBSD nodes, not in >Solaris, Linux, HP/UX etc. as far as I know. FWIW, most other OS's allow this operation and simply don't warn about it, so the only thing different about your FreeBSD box and anyone else's is that you're logging it. If the router is sufficiently misconfigured, it might be ARP'ing for the address and then sending a redirect when you send it traffic. Can you run "tcpdump -p icmp" and see if you are getting redirects from whatever IP address maps to 0:0:c:15:e7:d? There's a bug relating to such redirects that might be biting you. Bill