All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott MacKay <scottmackay@yahoo.com>
To: netfilter-devel@lists.netfilter.org
Subject: Kernel 2.6 conntrack defragment of IP packets
Date: Fri, 25 Jun 2004 04:16:41 -0700 (PDT)	[thread overview]
Message-ID: <20040625111641.42357.qmail@web13908.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0406251305390.11001-100000@blackhole.kfki.hu>

Hiyas,
   I was wondering, for the 2.6 kernel is there any
different in how conntrack defragments non TCP/non UDP
IP packets?
    I have a userspace QUEUE app which works fine
using 2.4.18 but has some issues with the 2.6.5 and
2.6.7 kernels.  When the packet goes above ~2360
bytes, the end of the packet is bad.  It is weird
because the data (as seen from a hexdump in the
userspace app) is fine, right up to that mark and
works ok under 2.4.x.  The only other change I made
was capturing the packet in PREROUTING mangle instead
of INPUT, but that looks to be after conntrack is done
with the data.  If the traffic is UDP, it seems to
work fine...

-Scott


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

  reply	other threads:[~2004-06-25 11:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 10:27 pom-ng include question Eicke Friedrich
2004-06-25 11:07 ` Jozsef Kadlecsik
2004-06-25 11:16   ` Scott MacKay [this message]
2004-06-25 13:01     ` Altering destination ethernet device Scott MacKay
2004-06-25 14:03       ` John A. Sullivan III
2004-06-25 14:16         ` Scott MacKay
2004-06-25 14:39           ` Henrik Nordstrom

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=20040625111641.42357.qmail@web13908.mail.yahoo.com \
    --to=scottmackay@yahoo.com \
    --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.