From: Tobias DiPasquale <codeslinger@gmail.com>
To: Quinton Hoole <quinton@hoole.biz>
Cc: netfilter@lists.netfilter.org
Subject: Re: Mangling IP Options fields
Date: Mon, 16 May 2005 09:35:16 -0400 [thread overview]
Message-ID: <876ef97a050516063532a0f24e@mail.gmail.com> (raw)
In-Reply-To: <42889D97.7000601@hoole.biz>
On 5/16/05, Quinton Hoole <quinton@hoole.biz> wrote:
> I looked into the libipq user space queueing option, but unfortunately
> switching to user space is not feasble in my case (every single packet
> on a GBit ethernet needs to be stamped, and resource utilisation is a
> 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?
You are headed in the right direction. I will say two more things:
1. What you are trying to do is very simple and shouldn't require much
deviation from iptables targets that already exist w/r/t coding
ability. Just make sure you know the pertinent RFCs and have a fast
machine to compile on.
2. You will need 2-3 CPUs (x86) to keep up with GBit forwarding + netfilter.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
next prev parent reply other threads:[~2005-05-16 13:35 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 [this message]
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=876ef97a050516063532a0f24e@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=netfilter@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.