From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next] arp: Ignore packets with an all zero sender
 mac address
Date: Fri, 03 Nov 2017 21:19:49 +0900 (KST)
Message-ID: <20171103.211949.776819501386263401.davem@davemloft.net>
References: <887efd3fea68d2499edcc6afb35d5fe4341d93a7.1508939295.git.echaudro@redhat.com>
        <20171027.224818.1467938250125086766.davem@davemloft.net>
        <cf78d039-acf2-76d1-becf-2672e63f2da3@redhat.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org
To: echaudro@redhat.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:41752 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1755995AbdKCMTz (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 3 Nov 2017 08:19:55 -0400
In-Reply-To: <cf78d039-acf2-76d1-becf-2672e63f2da3@redhat.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Eelco Chaudron <echaudro@redhat.com>
Date: Fri, 3 Nov 2017 11:39:04 +0100

> Looking for any mentioning of an all-zero MAC address being invalid,
> the only reference I could find was in the original first Xerox Wire
> Specification. The IEEE specifications do not mention this at all, and
> according to it, the all-zero address is a valid MA-L address assigned
> to Xerox.
> 
> Looking at the packet more, it might be an attempt to do an unARP (RFC
> 1868) but forgot to implement to set the Hardware Address Length to
> zero.
> 
> I'm sure adding an arptables entry can be used to solve this instead,
> in case the offending device cannot be fixed.
> 
> Please ignore this patch...

Ok, thanks for looking more deeply into this.