From owner-freebsd-net Fri Apr 23 15:26:18 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 0E16F14CC6 for ; Fri, 23 Apr 1999 15:25:57 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA06146 for ; Fri, 23 Apr 1999 17:21:14 -0400 (EDT) Date: Fri, 23 Apr 1999 17:21:04 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: freebsd-net@freebsd.org Subject: ARP weirdness(?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a firewall box running 2.2.7 and ipfilter. On one ethernet interface I have real addresses and on the other I use 192.168.0.x. Everything was going great until yesterday. Someone plugged a machine into the dirty side of the network with the same 192.168.0 network address that my machine on the clean side of the firewall uses. For some reason the "intruder" box kept being recognized as "the" 192.168.0.2. Why is that? I would think that if you have two machines claiming the same address the one that is attached to the right network would win. Is there any way to lock this down? 'arp -s' doesn't seem to make it stick... Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message