All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:38:22 +0200	[thread overview]
Message-ID: <4288B05E.4050205@hoole.biz> (raw)
In-Reply-To: <876ef97a050516063532a0f24e@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]


>On 5/16/05, Quinton Hoole <quinton@hoole.biz> wrote:
>  
>
>>big issue).  Some further reading of the netfilter FAQ has revealed that
>>patch-o-matic based extensions seem to be the way that others have
>>achieved things similar to my aims.
>>
>>http://www.netfilter.org/documentation/HOWTO//netfilter-extensions-HOWTO-4.html
>>
>>Can anyone confirm that I'm heading in the right direction?
>>    
>>
>
>  
>
Incidently, I'd ideally like to avoid patching the kernel (for fairly 
obvious reasons).  Is anyone aware of a way to instruct something in 
kernel space (in the standard kernel) to stamp values into the IP 
options fields.  I understand that this does not appear to be possible 
with the standard netfilter implementation, but perhaps there is another 
kernel module which will  do the trick?  Any pointers appreciated.

Quinton


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3244 bytes --]

  reply	other threads:[~2005-05-16 14:38 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
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 [this message]
  -- 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=4288B05E.4050205@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.