From: Florian Westphal <fw@strlen.de>
To: "Yigal Reiss (yreiss)" <yreiss@cisco.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] brouted packet identified as PACKET_OTHERHOST blocked by higher protocol
Date: Tue, 14 Jul 2015 13:35:31 +0200 [thread overview]
Message-ID: <20150714113531.GD25674@breakpoint.cc> (raw)
In-Reply-To: <3167EFAB95044A4EB6B134B9A39AA98A055B5E50@xmb-rcd-x05.cisco.com>
Yigal Reiss (yreiss) <yreiss@cisco.com> wrote:
> > No, thats not the problem you're trying to solve.
> >
> > If you want to move OTHERHOST skbs, don't (b)route them?
> >
> > Whats the real issue that you're trying to solve?
>
> I want to (b)route them because I want to be able to inspect the packets in higher levels
> (through iptables or user space IPS).
For nfqueue via iptables, use call-iptables sysctl?
Alternatively, implement NFQUEUE support for NF_BRIDGE family,
we'll need this eventually for nftables bridge family anyway.
AF_PACKET should just 'work' without brouting.
> Once I do that (i.e. (b)route by applying an appropriate ebtables rule), the corresponding
> packets get dropped unless I apply the patch.
Maybe, but if you broute everything you might as well just remove the
bridge...
You can use -j redirect in ebtables broute table to force local MAC dnat (this also
'fixes' the pkttype to _HOST) if you really want to broute.
next prev parent reply other threads:[~2015-07-14 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 10:37 [PATCH] brouted packet identified as PACKET_OTHERHOST blocked by higher protocol Yigal Reiss (yreiss)
2015-07-14 11:05 ` Florian Westphal
2015-07-14 11:18 ` Yigal Reiss (yreiss)
2015-07-14 11:35 ` Florian Westphal [this message]
2015-07-14 11:52 ` Yigal Reiss (yreiss)
2015-07-14 11:59 ` Florian Westphal
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=20150714113531.GD25674@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=yreiss@cisco.com \
/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).