From owner-freebsd-isp@FreeBSD.ORG  Fri Apr 25 09:58:59 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 106F337B401
	for <freebsd-isp@freebsd.org>; Fri, 25 Apr 2003 09:58:59 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [207.200.153.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 70A1B43FB1
	for <freebsd-isp@freebsd.org>; Fri, 25 Apr 2003 09:58:57 -0700 (PDT)
	(envelope-from tom@sdf.com)
Received: from tom (helo=localhost)
	by misery.sdf.com with local-esmtp (Exim 2.12 #1)
	id 1994xY-0003bj-00; Fri, 25 Apr 2003 08:17:56 -0700
Date: Fri, 25 Apr 2003 08:17:45 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: "Dave [Hawk-Systems]" <dave@hawk-systems.com>
In-Reply-To: <DBEIKNMKGOBGNDHAAKGNAEKDNAAB.dave@hawk-systems.com>
Message-ID: <Pine.BSF.4.05.10304250815330.216-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-isp@freebsd.org
Subject: RE: /kernel: arp messages
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2003 16:58:59 -0000


On Fri, 25 Apr 2003, Dave [Hawk-Systems] wrote:

> guess the error would help (long night)
> 
> /kernel: arp: 206.47.xxx.10 is on fxp0 but got reply from [insert mac address]
> on fxp1

  This means that fxp0 and fxp1 are connected to the same network segment.
You probably should not do that.  Either use separate network segments
(separate LANs or VLANs) or add the IP address from fxp1 to fxp0 and
disconnect fxp1.

Tom