From owner-freebsd-isp Sat Oct 20 19:12: 2 2001 Delivered-To: freebsd-isp@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id CB52C37B401 for ; Sat, 20 Oct 2001 19:11:59 -0700 (PDT) Received: from veager.jwweeks.com ([65.14.122.116]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011021021159.QNVL571.femail4.sdc1.sfba.home.com@veager.jwweeks.com>; Sat, 20 Oct 2001 19:11:59 -0700 Date: Sat, 20 Oct 2001 22:11:58 -0400 (EDT) From: Jim Weeks X-Sender: jim@veager.jwweeks.com To: "Jonathan M. Slivko" Cc: freebsd-isp@FreeBSD.ORG Subject: RE: arplookup failed: In-Reply-To: <002401c159d4$63c1ab20$6501a8c0@sioux> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thats entirely possible. I think I did run trafshow which would do that, but I am pretty sure the machine has been rebooted since doing so. Promiscuous mode wouldn't survive a hot boot would it? -- Jim Weeks On Sat, 20 Oct 2001, Jonathan M. Slivko wrote: > Jim, > > What you may have done is you may have set your NIC card into > promiscuous mode, which tells the NIC card to intercept all packets on > that network, not just the ones meant for that particular machine. What > you may have seen could have been a result of that. -- Jonathan > > --------------------------------------------------- > Jonathan Slivko - 4EverMail.COM - www.4evermail.com > Web Hosting - Web Desgin - UNIX Shell Accounts > JSlivko@4evermail.com - Phone: (212) 663-1109 > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG] On Behalf Of Jim Weeks > Sent: Saturday, October 20, 2001 9:53 PM > To: freebsd-isp@freebsd.org > Subject: arplookup failed: > > Would someone please check me on this. I know this has been discussed > before and I want to make sure I understand correctly. > > I am receiving the following error, > > Oct 20 21:16:21 server /kernel: arplookup XXX.XXX.XXX.XXX failed: host > is > not on local network > > Indeed the server issuing the request is not on the same subnet. If I > understand arp correctly, the kernel is not able to respond to a mac > address not directly connected to the subnet of the responding machine. > > After looking at the results of "tcpdump -n -e -p arp", I see a lot of > traffic from several subnets. Should I be seeing arp requests other > than > those initiated by my default gateway or other machines on the same > subnet? > > Why would this machine be issuing request for interfaces connected to a > different subnet, and if it should, why isn't it directing the requests > to my default gateway? > > Am I correct in assuming that this is a routing problem and not > something > I can correct from my end? > > Thanks in advance, > > -- > Jim Weeks > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message