Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Casper Gripenberg <casper.gripenberg@kotiportti.fi>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Bug in bridge or netfilter code (REJECT + incorrect MAC)?
Date: Wed, 02 Apr 2008 13:06:05 +0200	[thread overview]
Message-ID: <47F3689D.9040308@trash.net> (raw)
In-Reply-To: <47F3666E.4020103@kotiportti.fi>

Casper Gripenberg wrote:
> Patrick McHardy wrote:
>> Casper Gripenberg wrote:
>>> [...]
>>> https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=531
>>
>> I'm wondering, why does your client care about the source MAC
>> address of the REJECT packet? Or is there another switch in
>> between that does MAC filtering?
> 
> Yes..there is a switch or router between the Linux bridge
> and the computer that is supposed to receive the REJECT
> packet.
> 
> The packet stops at this router, because presumably it's
> doing some sort of MAC spoof filtering, or it just doesn't
> understand what is happening when the MAC of the source IP
> suddenly changes.
> 
> 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.


  reply	other threads:[~2008-04-02 11:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 17:34 Bug in bridge or netfilter code (REJECT + incorrect MAC)? Casper Gripenberg
2008-04-02 10:43 ` Patrick McHardy
2008-04-02 10:56   ` Casper Gripenberg
2008-04-02 11:06     ` Patrick McHardy [this message]
2008-04-02 11:15       ` Jan Engelhardt
2008-04-02 11:18         ` Patrick McHardy
2008-04-24  3:47         ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47F3689D.9040308@trash.net \
    --to=kaber@trash.net \
    --cc=casper.gripenberg@kotiportti.fi \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox