Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272697AbTG1HSm (ORCPT ); Mon, 28 Jul 2003 03:18:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272701AbTG1HSm (ORCPT ); Mon, 28 Jul 2003 03:18:42 -0400 Received: from smtpzilla1.xs4all.nl ([194.109.127.137]:27406 "EHLO smtpzilla1.xs4all.nl") by vger.kernel.org with ESMTP id S272697AbTG1HSl (ORCPT ); Mon, 28 Jul 2003 03:18:41 -0400 Message-ID: <01a601c354da$9710cc10$cd01a8c0@llewella> From: "Bas Bloemsaat" To: "Ben Greear" , "David S. Miller" , "Carlos Velasco" , , References: <20030727151234.6e2aa57e.davem@redhat.com> <3F248AE5.4000204@candelatech.com> Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices Date: Mon, 28 Jul 2003 09:33:46 +0200 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: 1169 Lines: 29 Hi all, > > Not a bug. This behavior is on purpose. First of all I'm sorry I rubbed some old sores. I didn't know the behaviour was on purpose, and I did google for it. Could have saved my weekend, had I known. > >Bas's problem can be solved by him giving a "preferred source" > >to each of his IPV4 routes and setting the "arpfilter" sysctl > >variable for his devices to "1". > > Yes, it's another approach to solve his problem. But he must play with routing. Routing isn't solving anything here, it's too dynamic. Only one of the devices has a fixed IP, and handles a link to the outside, among others. The other is on DHCP: addresses can change without warning. Both are on the same ethernet segment. I've looked at the hidden patch, and it's capable of doing this right. I do think this has to be solved at the device layer. It's quite counter intuitive the way it is now. My vote goes to hidden. 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/