From: "Igor 'Lo' (И.L.)" <bombsiteunrested@gmail.com>
To: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: recommendations on implementing a custom Netfilter hook to QUEUE packets before their SEQ/ACK and size before fragmentation are known?
Date: Wed, 2 Mar 2011 05:22:39 +0200 [thread overview]
Message-ID: <AANLkTi=x_khzkObaG4F7PrVzbStd5c1OZMCE_oKHa35b@mail.gmail.com> (raw)
Hi all.
What I look for is reimplementing a part of NFQUEUE functionality at
the stage where TCP packet is formed before sending to network.
It seems that NFQUEUE can't just handle expanded (> MTU) packet, and
also want to have control over SEQ/ACK numbers assigned to
both packets and connection structures.
But errr.. where to look for? The sources are too complex and there's
not enough guides.
Actually I have this doc only:
http://www.nsnam.org/wiki/index.php/GSOC2009Netfilter#Callback_Priority
Can anyone point me to correct place in kernel sources to see/attach
with SystemTap and track how SEQs are generated and how outgoing
packets are planned to be fragmented or even dropped? Deliberately
want a good tour.
P.S. There's at least 2 projects that can benefit from such
transparent packet size growing, one is mine and second is StegBox
(steganography based covert channels in traffic)
--
cheers,
Igor
next reply other threads:[~2011-03-02 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 3:22 Igor 'Lo' (И.L.) [this message]
2011-03-07 23:52 ` recommendations on implementing a custom Netfilter hook to QUEUE packets before their SEQ/ACK and size before fragmentation are known? Frank Ch. Eigler
2011-03-08 3:18 ` Igor 'Lo' (И.L.)
2012-09-11 12:31 ` Hassan
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='AANLkTi=x_khzkObaG4F7PrVzbStd5c1OZMCE_oKHa35b@mail.gmail.com' \
--to=bombsiteunrested@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).