From: Jonas Berlin <xkr47@outerspace.dyndns.org>
To: Quinton Hoole <quinton@hoole.biz>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Mangling IP Options fields
Date: Mon, 16 May 2005 18:43:35 +0000 [thread overview]
Message-ID: <4288E9D7.10306@outerspace.dyndns.org> (raw)
In-Reply-To: <42889454.6040300@hoole.biz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoting Quinton Hoole on 2005-05-16 12:38 UTC:
> Is mangling of IP options fields supported by netfilter/iptables?
>
> I've seen Fabrice's reply to a simimlar question some 3 years back:
>
> https://lists.netfilter.org/pipermail/netfilter-devel/2002-March/006957.html
I think nothing has changed. The IPV4OPTSSTRIP mentioned in the mail
(which removes all options) is still available.
You can download the latest pom-ng (through www.netfilter.org), which
includes IPV4OPTSSTRIP. If you need more help regarding how to do stuff
in the net/ipv4/netfilter/ipt_IPV4OPTSSTRIP.c file (which is the one you
should modify), just ask :)
Good luck!
- --
- - xkr47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCiOnVxyF48ZTvn+4RAj5zAJwKMG2mfElgS26RV2PRwwcIGuYBPwCfdJnv
RtaGxlBLe/NpODfN5b7zob4=
=9Bp4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-05-16 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 12:38 Mangling IP Options fields Quinton Hoole
2005-05-16 18:43 ` Jonas Berlin [this message]
2005-05-19 12:58 ` Quinton Hoole
2005-05-20 11:17 ` Amin Azez
2005-05-20 13:47 ` Quinton Hoole
2005-06-04 9:23 ` Jonas Berlin
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 12:22 Quinton Hoole
2005-05-16 12:38 ` Tobias DiPasquale
2005-05-16 12:58 ` Quinton Hoole
2005-05-16 15:58 ` Frank Abel
2005-05-16 13:18 ` Quinton Hoole
2005-05-16 13:35 ` Tobias DiPasquale
2005-05-16 14:38 ` Quinton Hoole
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=4288E9D7.10306@outerspace.dyndns.org \
--to=xkr47@outerspace.dyndns.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=quinton@hoole.biz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.