From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: Bug in bridge or netfilter code (REJECT + incorrect MAC)? Date: Thu, 24 Apr 2008 05:47:48 +0200 Message-ID: <481002E4.9020902@trash.net> References: <47F2723D.2080509@kotiportti.fi> <47F36349.8050400@trash.net> <47F3666E.4020103@kotiportti.fi> <47F3689D.9040308@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Casper Gripenberg , netfilter-devel@vger.kernel.org To: Jan Engelhardt Return-path: Received: from stinky.trash.net ([213.144.137.162]:55727 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753599AbYDXDrn (ORCPT ); Wed, 23 Apr 2008 23:47:43 -0400 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Jan Engelhardt wrote: > > On Wednesday 2008-04-02 13:06, Patrick McHardy wrote: >>> >>> The router is my ISP's internet router, which I do not >>> control. But I doubt the router is doing anything wrong >>> though. The weirdness is more on the Linux side.. >> >> Sure, for full transparency the packets should ideally use >> the original source MAC address. I'll see if I can come >> up with a patch for this. > > The problem is an interesting one. REJECT itself does not fill > in the MAC address, and probably should not try (there is more > than just Ethernet). Yet the routing code is so deeply buried > that drawing a seam through the entire call chain seems intrusive. > Well, I didn't find a good way to fix this. Casper, please open a bug report at bugzilla.netfilter.org so this doesn't get lost. Thanks.