From: Todd Underwood <todd@docforge.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: changing packet length?
Date: Thu, 12 May 2005 09:25:33 -0600 [thread overview]
Message-ID: <20050512152533.GE22646@docforge.org> (raw)
In-Reply-To: <20050506111410.GG30482@sunbeam.de.gnumonks.org>
Harald, all,
On Fri, May 06, 2005 at 01:14:10PM +0200, Harald Welte wrote:
> On Tue, May 03, 2005 at 05:34:06PM -0400, BJ Premore wrote:
> > So my hopefully simple question is, can packet sizes be
> > changed and then reinjected using ipq_set_verdict?
>
> Of course. you just reinject the packet with a different data_len.
>
this seems not to work. given the code that was posted, the trivial
case of this fails: adding 4 bytes of option-1 to the tcp header,
changing the checksum and changing the size.
the data gets corrupted.
is there some simple bug that i'm not seeing the in the header/data
handling code that was posted. running tcpdump, i see the same errors
that bj was reporting.
scouring the web i can find *no* examples of anyone changing the size
of the header or the data in ipq userspace processes. without being
able to do that, interesting things (like a userspace md5 signing
implementation) are obviously not possible.
harald: did you mean something by 'reinject' other than
ipq_set_verdict, with new data?
todd
next prev parent reply other threads:[~2005-05-12 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:34 changing packet length? BJ Premore
2005-05-06 11:14 ` Harald Welte
2005-05-06 14:11 ` BJ Premore
2005-05-29 19:00 ` Harald Welte
2005-05-29 19:01 ` Harald Welte
2005-06-07 7:21 ` Quinton Hoole
2005-05-12 15:25 ` Todd Underwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 13:34 BJ Premore
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=20050512152533.GE22646@docforge.org \
--to=todd@docforge.org \
--cc=netfilter-devel@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.