Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272574AbTHSQrL (ORCPT ); Tue, 19 Aug 2003 12:47:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272249AbTHSQrL (ORCPT ); Tue, 19 Aug 2003 12:47:11 -0400 Received: from zeus.kernel.org ([204.152.189.113]:53499 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id S276333AbTHSQ1z (ORCPT ); Tue, 19 Aug 2003 12:27:55 -0400 Message-ID: <070c01c36653$7f3c1ab0$c801a8c0@llewella> From: "Bas Bloemsaat" To: "Richard Underwood" , "'David S. Miller'" , "Stephan von Krawczynski" Cc: , , , , , , , , , , References: <353568DCBAE06148B70767C1B1A93E625EAB57@post.pc.aspectgroup.co.uk> Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices Date: Tue, 19 Aug 2003 15:11:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 629 Lines: 16 > The RFC I quoted (985) says the ARP packets generated by Linux > should be dropped. Sure, the RFC isn't a standard, but there ARE plenty of > implementations that obey it for perfectly valid security reasons. Same goes for 1180. It it doesn't define a standard either, but makes perfectly clear that any interface has it's own ARP, not one ARP for the entire system. Regards, Bas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/