From: Ian Pilcher <arequipeno@gmail.com>
To: netfilter@vger.kernel.org
Subject: ebtables rules for specific bridge
Date: Mon, 12 Apr 2021 16:29:51 -0500 [thread overview]
Message-ID: <s52e4f$nr6$1@ciao.gmane.io> (raw)
I need to create the equivalent of a PVLAN for a few VMs on an older
(EL7) hypervisor. This hypervisor has multiple Linux bridges, so I
need to create ebtables rules that affect the "PVLAN" bridge, but not
the other bridges on the box.
My searches haven't come up with any examples for this particular
scenario. Looking at ebtables(8), I have a suspicion that --logical-in
and/or --logical-out may have a role to play, but I'm not sure that's
true or when to use which.
Any hints would be appreciated.
Also, -Ln and -Lc don't seem to have any effect (beyond that of -L). Is
there some trick to actually showing line numbers and/or counters in the
ebtables output? (This is ebtables 2.0.10 on kernel 3.10.0.)
Thanks!
--
========================================================================
In Soviet Russia, Google searches you!
========================================================================
reply other threads:[~2021-04-12 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='s52e4f$nr6$1@ciao.gmane.io' \
--to=arequipeno@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox