From: Bradley King <bking@freesurf.fr>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Linux 2.6.12 REDIRECT bug?
Date: Tue, 28 Jun 2005 11:24:13 +0200 [thread overview]
Message-ID: <42C1173D.7010802@freesurf.fr> (raw)
In-Reply-To: <Pine.LNX.4.62.0506231428220.3964@kaber.coreworks.de>
Didn't hear back from anyone, this did indeed work.....(I don't need a
response, but feared the message didn't arrive)
Thanks,
Brad
Patrick McHardy wrote:
> On Wed, 22 Jun 2005, Bradley King wrote:
>
>> [1.] One line summary of the problem:
>> the iptables REDIRECT kernel module seems to fail with kernel 2.6.12
>>
>> [2.] Full description of the problem/report:
>> Have been running previous 2.6.x versions w/o problems A command like:
>> iptables -t nat -A PREROUTING -i br0 -p tcp --dport 80 -j REDIRECT
>> --to-port 8080
>> (used to redirect intranet traffic through a NAT/MASQUERADE firewall
>> short circuits traffic (port 8080 see's no activity at all)
>> I tried DNAT with the same results
>> Note that the inferface is a bridge interface with an Ethernet and
>> Wifi interface bridged togeter
>
>
> Does this patch help?
>
> Regards
> Patrick
>
>------------------------------------------------------------------------
>
>diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
>--- a/net/ipv4/ip_output.c
>+++ b/net/ipv4/ip_output.c
>@@ -188,7 +188,12 @@ static inline int ip_finish_output2(stru
> skb = skb2;
> }
>
>- nf_reset(skb);
>+#ifdef CONFIG_BRIDGE_NETFILTER
>+ /* bridge-netfilter defers calling some IP hooks to the bridge layer and
>+ * still needs the conntrack reference */
>+ if (skb->nf_bridge == NULL)
>+#endif
>+ nf_reset(skb);
>
> if (hh) {
> int hh_alen;
>
>
next prev parent reply other threads:[~2005-06-28 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 12:17 Linux 2.6.12 REDIRECT bug? Bradley King
2005-06-23 12:29 ` Patrick McHardy
2005-06-28 9:24 ` Bradley King [this message]
2005-06-28 16:02 ` 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=42C1173D.7010802@freesurf.fr \
--to=bking@freesurf.fr \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.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.