From owner-freebsd-questions Fri May 19 6:20:29 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id B9D7D37BDAA for ; Fri, 19 May 2000 06:20:19 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id JAA13103; Fri, 19 May 2000 09:20:41 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000519091911.00ad2b70@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 19 May 2000 09:23:53 -0400 To: Omachonu Ogali From: John Subject: Re: 4.0-Stable Kernel Error? Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: References: <4.3.1.2.20000519085332.00acec50@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi all, > > > > Since upgrading to 4.0-Stable, I've been getting a sporadic error message > > in /var/log/messages that shows up as follows: > > > > May 18 12:55:17 merlin /kernel: arp: unknown hardware address format > (0x0800) > > > > It's showed up 3 times in the past 36 or so hours, but not at any point in > > time that I can narrow it down to occurring near/after/during any specific > > system event. > > > > Any idea what would be causing the error and how to go about fixing it? > >This is a network related message, have you added any other devices to >the LAN your NIC card is connected to? Survey all your networking >equipment to make sure they're functioning properly, I had a faulty 3C509 >once that would put illegitimate ARP packets on the wire... I haven't added any network hardware. Other than upgrading from 3.4-Stable to 4.0-Stable, the only changes I made were within the kernel, since, according to the upgrade procedure, it was stated that a new kernel should be made from the new GENERIC. I did so, and the only real differences between my old and new kernel files is that previously I defined all devices (da0, da1, d2, sa0, cd0, fxp0, fxp1), and now I have it simply as da, sa, cd, and fxp. I did also notice that my DNS was having trouble identifying my windows box (which is sitting at 192.168.1.2) - kept saying that it couldn't ID it and that it might be faked. I finally fixed that by adding an entry for it in the local zone file. But still, that seemed odd since it was working just fine about a week ago (on 3.4-stable). When I get a chance I can try swapping out the ethernet cards to see if one is bad. Does any of that help? Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message