All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Damien Thébault" <damien.thebault@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Wrong ethernet headers after double postrouting fix
Date: Thu, 13 Dec 2007 17:55:10 +0100	[thread overview]
Message-ID: <476163EE.7040307@trash.net> (raw)
In-Reply-To: <9a4a382a0712130733g21dd4390w9f457bed7ad19777@mail.gmail.com>

Damien Thébault wrote:
> On Dec 13, 2007 9:41 AM, Patrick McHardy <kaber@trash.net> wrote:
>> Could you try this patch please?
>>
>>
>> diff --git a/include/linux/netfilter_bridge.h b/include/linux/netfilter_bridge.h
>> index 533ee35..499aa93 100644
>> --- a/include/linux/netfilter_bridge.h
>> +++ b/include/linux/netfilter_bridge.h
>> @@ -50,7 +50,8 @@ enum nf_br_hook_priorities {
>>  extern int nf_bridge_copy_header(struct sk_buff *skb);
>>  static inline int nf_bridge_maybe_copy_header(struct sk_buff *skb)
>>  {
>> -       if (skb->nf_bridge)
>> +       if (skb->nf_bridge &&
>> +           skb->nf_bridge->mask & (BRNF_BRIDGED | BRNF_BRIDGED_DNAT))
>>                 return nf_bridge_copy_header(skb);
>>         return 0;
>>  }
>>
>>
> 
> I tried it and it successfully solves this problem. Everything is fine now.


Thanks a lot for testing.
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2007-12-13 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  8:05 Wrong ethernet headers after double postrouting fix Damien Thébault
2007-12-13  8:41 ` Patrick McHardy
2007-12-13 15:33   ` Damien Thébault
2007-12-13 16:55     ` Patrick McHardy [this message]

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=476163EE.7040307@trash.net \
    --to=kaber@trash.net \
    --cc=damien.thebault@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.