From: Philip Craig <philipc@snapgear.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Volker Sauer <volker@volker-sauer.de>,
netfilter@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: Problem with new --physdev-out style
Date: Wed, 24 Oct 2007 18:22:52 +1000 [thread overview]
Message-ID: <471F00DC.9070001@snapgear.com> (raw)
In-Reply-To: <471EF68A.702@trash.net>
Patrick McHardy wrote:
>> $IPTABLES -A FORWARD -i $BR_GUEST -o $BR_INT -m physdev --physdev-out $IF_DMZ -p tcp --dport 3389 -j ACCEPT
>
> Try adding "--physdev-is-bridged" to your rules. Without that the kernel
> is not able to tell whether they apply only to bridged packets or also
> to forwarded or locally generated ones.
That won't work for the above rule, for example, since the packet is
being forwarded between two different bridges, so it is not bridged.
The only solution I am aware of is to stop bridging and use routing
and arp proxy.
next prev parent reply other threads:[~2007-10-24 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071024071854.GA18581@volker-sauer.de>
2007-10-24 7:38 ` Problem with new --physdev-out style Patrick McHardy
2007-10-24 8:22 ` Philip Craig [this message]
2007-10-24 8:34 ` Patrick McHardy
2007-10-24 8:43 ` Pascal Hambourg
2007-10-24 9:15 ` Philip Craig
2007-10-24 9:22 ` Pascal Hambourg
2007-10-24 9:39 ` Philip Craig
2007-10-24 9:46 ` Pascal Hambourg
2007-10-24 9:05 ` Philip Craig
2007-10-24 9:42 ` Patrick McHardy
2007-10-24 12:06 ` Volker Sauer
2007-10-24 12:49 ` Patrick McHardy
2007-10-24 12:57 ` Volker Sauer
2007-10-24 14:11 ` Pascal Hambourg
2007-10-24 15:18 ` Volker Sauer
2007-10-24 9:28 ` Philip Craig
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=471F00DC.9070001@snapgear.com \
--to=philipc@snapgear.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=volker@volker-sauer.de \
/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;
as well as URLs for NNTP newsgroup(s).