From owner-freebsd-net@freebsd.org  Sat Oct 17 12:47:41 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01E2AA17C80
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat, 17 Oct 2015 12:47:41 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E2E311A0F
 for <freebsd-net@FreeBSD.org>; Sat, 17 Oct 2015 12:47:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9HCleL9063138
 for <freebsd-net@FreeBSD.org>; Sat, 17 Oct 2015 12:47:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 166285] [arp] FreeBSD v8.1 REL p8 arp: unknown hardware address
 format (0x0fff)
Date: Sat, 17 Oct 2015 12:47:41 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: melifaro@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc bug_status
Message-ID: <bug-166285-2472-Whw5szzrGd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-166285-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-166285-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2015 12:47:41 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166285

Alexander V. Chernikov <melifaro@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |melifaro@FreeBSD.org
             Status|In Progress                 |Open

--- Comment #2 from Alexander V. Chernikov <melifaro@FreeBSD.org> ---
Most probably, that was triggered by some other device in network generating
such "strange" arp  packets. It should be possible to find those packets by
doing something like "tcpdump -i XXX -lnevs100 arp" (where XXX is the interface
name) and looking for ethertype value (and source mac address). While it is
questionable if FreeBSD should yell on invalid arp packets instead of silently
ignoring them, this is not a (FreeBSD) bug. I'd like to close this PR if there
are no other questions/comments.

-- 
You are receiving this mail because:
You are the assignee for the bug.