From: Quinton Hoole <quinton@hoole.biz>
To: Tobias DiPasquale <codeslinger@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Mangling IP Options fields
Date: Mon, 16 May 2005 14:58:03 +0200 [thread overview]
Message-ID: <428898DB.5010005@hoole.biz> (raw)
In-Reply-To: <876ef97a05051605385987cc50@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
Tobias DiPasquale wrote:
>On 5/16/05, Quinton Hoole <quinton@hoole.biz> wrote:
>
>
>>This newbie needs to add and/or rewrite data in the IP Options fields.
>>The MANGLE chain looks like the place to do this, but I don't see the
>>appropriate target extensions to achieve it. It seems easy to mangle
>>most other fields (DSCP, ECN, TOS, TTL etc) but no mention of the
>>OPTIONS fields.
>>
>>Is mangling of IP options fields supported by netfilter/iptables?
>>
>>
>
>Which IP options are you looking to be able to mangle? If you just
>need to be able to mangle the MSS, then check out the TCPMSS target
>included in the vanilla Linux kernel.
>
I'll be needing to mangle other fields. My ultimate goal is to "stamp"
a 32 or 64 bit value into each packet for security reasons.
>This would also be a good place
>to start if you need to create an iptables target that mangles an IP
>option of another type.
>
Great, thanks.
Q
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3244 bytes --]
next prev parent reply other threads:[~2005-05-16 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 12:22 Mangling IP Options fields Quinton Hoole
2005-05-16 12:38 ` Tobias DiPasquale
2005-05-16 12:58 ` Quinton Hoole [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 12:38 Quinton Hoole
2005-05-16 18:43 ` Jonas Berlin
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
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=428898DB.5010005@hoole.biz \
--to=quinton@hoole.biz \
--cc=codeslinger@gmail.com \
--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 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.