From: Abraham vd Merwe <abraham@2d3d.co.za>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: questions about netfilter/iptables api
Date: Tue, 9 Jul 2002 13:35:37 +0200 [thread overview]
Message-ID: <20020709133537.A1834@crystal.2d3d.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
Hi!
I'm trying to figure out how to prepend rules into the INPUT/OUTPUT chains.
The way I see it, you do
1. getsockopt IPT_SO_GET_INFO and IPT_SO_GET_ENTRIES to get current entries
in chain.
2. construct a ``struct ipt_entry'' with the new rule.
3. construct a ``struct ipt_replace'' entry with new entry + old entries.
4. do setsockopt IPT_SO_SET_REPLACE to insert new entry in the chain.
Now, what I can't figure out is what those hook_entry and underflow arrays
in ``struct ipt_replace'' are used for and what offsets I need to put in them.
Also, I see that iptables goes and appends elems entries for some of the
struct ipt_entry entries. When do I need to do that and is it necessary for
simple rules like these:
-I INPUT -d net/mask -i eth0
-I OUTPUT -s net/mask -o eth1
-I INPUT -d net/mask -p tcp --source-port 23 -i eth0
etc.
I don't see why any additional info would be necessary since you can fit all
that info in the the ``struct ipt_ip'' field.
--
Regards
Abraham
Well, O.K. I'll compromise with my principles because of EXISTENTIAL DESPAIR!
__________________________________________________________
Abraham vd Merwe - 2d3D, Inc.
Device Driver Development, Outsourcing, Embedded Systems
Cell: +27 82 565 4451 Snailmail:
Tel: +27 21 761 7549 Block C, Aintree Park
Fax: +27 21 761 7648 Doncaster Road
Email: abraham@2d3d.co.za Kenilworth, 7700
Http: http://www.2d3d.com South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-07-09 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 11:35 Abraham vd Merwe [this message]
2002-07-09 14:04 ` Harald Welte
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=20020709133537.A1834@crystal.2d3d.co.za \
--to=abraham@2d3d.co.za \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®