From: Michael Kearey <mutk@iprimus.com.au>
To: netfilter@lists.netfilter.org
Subject: Re: iptc_* implementation queries
Date: Tue, 03 Feb 2004 14:54:12 +1000 [thread overview]
Message-ID: <401F2974.1040902@iprimus.com.au> (raw)
In-Reply-To: <s01e5eb1.078@prv-mail25.provo.novell.com>
Jambunathan Jambunathan wrote:
> I am interested in knowing the netfilter infrastructure and I would
> like to know how iptables communicates with netfilter ( user to
> kernel space communication ) I understand that it happens through
> raw sockets through setsockot and getsockopt. Also there are a
> good number of iptc_* calls that are declared in libiptc.h which
> are used by the iptables user space tool. I would like to know
> where I can see the implementations for these iptc_* calls.
> I am unable to see this either in the kernel code nor in the
> iptables bz2 package. I am looking at 2.4.18 code of linux
> kernel fyi.
>
> I will appreciate a mini code walk through or example.
>
(Jambunathan sorry about replying directly to you..here is message to
list)
Here is a reasonably good 'walk through'. It's ever so slightly
inaccurate in some of the example code with redundant #includes, but
is pretty good as a starting point. It really should 'This is how *I*
did it', as there are several ways to acheive same thing...
http://www.tldp.org/HOWTO/Querying-libiptc-HOWTO/index.html
BTW, the libiptc isn't meant to be used as an 'API' to manipulate
tables etc. Several reasons are given see
http://netfilter.org/documentation/FAQ/netfilter-faq-4.html#ss4.5
Cheers,
Michael
next prev parent reply other threads:[~2004-02-03 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 21:28 iptc_* implementation queries Jambunathan Jambunathan
2004-02-03 3:57 ` Kiran Kumar
2004-02-03 4:54 ` Michael Kearey [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 4:39 Jambunathan Jambunathan
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=401F2974.1040902@iprimus.com.au \
--to=mutk@iprimus.com.au \
--cc=netfilter@lists.netfilter.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