From: Patrick McHardy <kaber@trash.net>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org,
Harald Welte <laforge@netfilter.org>,
James Morris <jmorris@redhat.com>,
coreteam@netfilter.org, David Miller <davem@davemloft.net>
Subject: Re: [netfilter-core] iptables redirect is broken on bridged setup
Date: Wed, 03 Aug 2005 03:46:40 +0200 [thread overview]
Message-ID: <42F02200.1090802@trash.net> (raw)
In-Reply-To: <200507291209.37247.vda@ilport.com.ua>
Denis Vlasenko wrote:
> Linux 2.6.12
>
> Was running for months with this simple iptables rule:
>
> iptables -t nat -A PREROUTING -s 172.17.6.44 -d 172.16.42.201 -p tcp --dport 9100 -j REDIRECT --to 9123
>
> Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
> 0 0 REDIRECT tcp -- * * 172.17.6.44 172.16.42.201 tcp dpt:9100 redir ports 9123
>
> But now I need to bridge together two eth cards in this machine, and
> suddenly redirect is no longer works.
This doesn't look related to the nf_reset problem since it happens
in PREROUTING and only the output hooks are defered. I suspect a
configuration error, when there is no IP configured on a device
the REDIRECT target can't be used.
prev parent reply other threads:[~2005-08-03 1:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 9:11 iptables redirect is broken on bridged setup Denis Vlasenko
2005-07-29 11:23 ` Jan Engelhardt
2005-07-29 12:11 ` Denis Vlasenko
2005-07-31 10:50 ` Harald Welte
2005-07-29 19:37 ` David S. Miller
2005-07-30 14:40 ` Denis Vlasenko
2005-07-31 10:42 ` Harald Welte
2005-08-03 1:46 ` 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=42F02200.1090802@trash.net \
--to=kaber@trash.net \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=vda@ilport.com.ua \
/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