From: Yacin Nadji <ynadji@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: Add Rules from Within the Kernel -- Where to Start?
Date: Thu, 18 Feb 2010 21:14:44 -0500 [thread overview]
Message-ID: <f503ee681002181814y11321d3cqb9e0b42c314e64d5@mail.gmail.com> (raw)
Howdy list!
I'm working on a research project where I'd like to be able to
create/update iptables entries from within kernel-space instead of the
usual route through user-space (with the client iptables). The idea is
to have a separate rule set that can only be altered by the kernel,
and not by the normal iptables client in user-space. I've looked
around the documentation, but the majority of it seems focused on
adding extensions that would operate in userland.
My question is, where should I look for this functionality in
netfilter/the kernel? I was originally planning on tracing the calls
up into the kernel through the client iptables to see what kernel
functions end up being called, but things got pretty muddy for me as
it passed through libiptc/tipc. Any suggestions on where to look to
achieve iptables-like functionality entirely within the kernel would
be much appreciated.
Thanks!
Yacin
reply other threads:[~2010-02-19 2:15 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=f503ee681002181814y11321d3cqb9e0b42c314e64d5@mail.gmail.com \
--to=ynadji@gmail.com \
--cc=netfilter-devel@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 NNTP newsgroup(s).