From owner-freebsd-net@FreeBSD.ORG  Fri Apr 11 00:11:08 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 34F6C37B401; Fri, 11 Apr 2003 00:11:08 -0700 (PDT)
Received: from cow.home.mshindo.net (203.60.138.210.bn.2iij.net
	[210.138.60.203])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E090443F75; Fri, 11 Apr 2003 00:11:04 -0700 (PDT)
	(envelope-from mshindo@mshindo.net)
Received: from localhost ([210.196.142.99])
	by cow.home.mshindo.net (8.12.6/8.12.6) with ESMTP id h3B7ECkF077118;
	Fri, 11 Apr 2003 16:14:14 +0900 (JST)
	(envelope-from mshindo@mshindo.net)
Date: Fri, 11 Apr 2003 16:10:56 +0900 (JST)
Message-Id: <20030411.161056.71083042.mshindo@mshindo.net>
To: oppermann@pipeline.ch
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <3E942121.7A3647EB@pipeline.ch>
References: <3E942121.7A3647EB@pipeline.ch>
X-Mailer: Mew version 4.0.51 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: tmm@freebsd.org
cc: freebsd-net@freebsd.org
Subject: Re: Bug in ARP requests
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2003 07:11:08 -0000

Hi,

From: Andre Oppermann <oppermann@pipeline.ch>
Subject: Bug in ARP requests
Date: Wed, 09 Apr 2003 15:33:21 +0200

> I got hit by this pretty hard when I connected a FreeBSD/Zebra box
> to AMSIX. Appearently the Cisco and Juniper boxes don't answer to
> broken ARP requests if the target hardware address field is not set
> to NULL but filled with random memory junk. While debugging this we
> got really confused by the tcpdumps... Ethereal saved the day because
> it has a much nicer display than tcpdump.

I also came accross this problem when I was testing the equipment
(wireless access point, in fact) made by the company I currently work
for. At that time, I thought that it was specific my company's
equipment, but now I'm amezed to know that there are so many
networking equipments that don't accept such a bogus ARP Request.

BTW, tcpdump prints out the target hardware address in ARP Request if
it isn't all zero and that made me realized that the problem was
caused by FreeBSD's ARP request. tcpdump saved a day for me:-)