From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Miguel Alejandro González" <maggonzz@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: about ip header options
Date: Thu, 8 Nov 2012 13:42:38 +0100 [thread overview]
Message-ID: <20121108124238.GA3741@1984> (raw)
In-Reply-To: <CAOSBYzf3VCAeKybJee6CFrB+PjQWesOHjxsJ6a7dpoC_CSxxVQ@mail.gmail.com>
Hi Miguel,
On Wed, Nov 07, 2012 at 04:38:54PM -0600, Miguel Alejandro González wrote:
> Hello
>
> I have a netfilter module on the mangle table PREROUTING... I want to
> validate unexpired routes in ipv4 headers, but I think the TCP/IP
> stack already does this... because it is mentioned on the rfc 1812 so
> I'm guessing it is already implemented by the kernel
>
> but somehow my module catches the packet first before the kernel does
> its magic...
>
> As I understand the picture I'm attaching represents the whole process
> the TCP/IP stack performs to handle the options in a IPv4 packet, but
> I still don't understand how netfilter works with the stack
This is rather old, but it helps to provide the big picture:
http://open-source.arkoon.net/kernel/kernel_net.png
> Do I have to process the packet's options in my module or what?
I think it's better if you try to explain what you're trying to do
with your new extension. That may help to attract people to help you.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-11-08 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 22:38 about ip header options Miguel Alejandro González
2012-11-08 12:42 ` Pablo Neira Ayuso [this message]
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=20121108124238.GA3741@1984 \
--to=pablo@netfilter.org \
--cc=maggonzz@gmail.com \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).