From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: How to have a dynamic ingress device(s) list?
Date: Wed, 24 Apr 2024 18:03:31 -0000 [thread overview]
Message-ID: <20240424180331.3dfb6fc4@localhost> (raw)
Hi,
I am trying to do this:
# dynamic list, updated through a bash script:
define $nics = { "nic1", "nic5", ... }
# ...
chain foo {
type filter hook ingress devices = $nics priority -500
# ...
}
The problems I am facing:
1. It seems the perfect solution I was hoping for is not possible:
devices = "nic*"
2. If there is only one device (e.g. "nic7"), the syntax requires:
device "nic7" # not 'devices' and no '='
Trying something like devices = "nic7" results in a segmentation fault.
3. Adding/removing a separate chain for each nic dynamically seems to
me less efficient, i.e. I am trying to avoid it if possible.
What is the right way to do this?
next reply other threads:[~2024-04-24 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 18:03 William N. [this message]
2024-04-24 18:49 ` How to have a dynamic ingress device(s) list? Kerin Millar
2024-04-24 19:20 ` William N.
2024-04-24 23:25 ` Kerin Millar
2024-04-25 14:12 ` William N.
2024-04-25 14:22 ` Kerin Millar
2024-04-25 15:30 ` William N.
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=20240424180331.3dfb6fc4@localhost \
--to=netfilter@riseup.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).