From: "Miguel Alejandro González" <maggonzz@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: about ip header options
Date: Wed, 7 Nov 2012 16:38:54 -0600 [thread overview]
Message-ID: <CAOSBYzf3VCAeKybJee6CFrB+PjQWesOHjxsJ6a7dpoC_CSxxVQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
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
Do I have to process the packet's options in my module or what?
Please, help
Regards
[-- Attachment #2: Screenshot from 2012-11-07 15_50_47.png --]
[-- Type: image/png, Size: 51730 bytes --]
next reply other threads:[~2012-11-07 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 22:38 Miguel Alejandro González [this message]
2012-11-08 12:42 ` about ip header options Pablo Neira Ayuso
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=CAOSBYzf3VCAeKybJee6CFrB+PjQWesOHjxsJ6a7dpoC_CSxxVQ@mail.gmail.com \
--to=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).