From owner-freebsd-questions@FreeBSD.ORG Wed Nov 26 21:45:24 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33B8916A4CE for ; Wed, 26 Nov 2003 21:45:24 -0800 (PST) Received: from dragoncrest.jasnetworks.net (dragoncrest.jasnetworks.net [65.194.254.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 358B043F3F for ; Wed, 26 Nov 2003 21:45:23 -0800 (PST) (envelope-from dragoncrest@voyager.net) Received: from works.voyager.net (works.jasnetworks.net [192.168.0.5]) hAR0xRZ9027588; Thu, 27 Nov 2003 00:59:27 GMT (envelope-from dragoncrest@voyager.net) Message-Id: <5.2.0.9.2.20031127005418.00ac0250@pop.voyager.net> X-Sender: dragoncrest@pop.voyager.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 27 Nov 2003 00:55:19 -0500 To: jesse@wingnet.net, freebsd-questions@freebsd.org From: Dragoncrest In-Reply-To: References: <44oev5mbo3.fsf@be-well.ilk.org> <200311241505.hAOF5kd48312@skippyii.compar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: RE: Arplookup error. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 05:45:24 -0000 >I'd like to know this too. I have a FreeBSD 4.8-RELEASE box that exhibits the >same symptoms. The addresses it complains about belong to a colo box on our >network and a cisco router. That's a big Ditto for me too. I got the same problem on one of my bsd workstations up at work too, but only when accessing either of our two Oracle servers. So yeah, I'd love to know the resolution to this too if someone finds one. :)