All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Vogt <beunlovable@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: libipq does not shorten package
Date: Thu, 09 Mar 2006 16:55:35 +0100	[thread overview]
Message-ID: <44104FF7.1030104@trash.net> (raw)
In-Reply-To: <859616420603090530p24d0cb9cg@mail.gmail.com>

David Vogt wrote:
> Dear all,
> 
> I already posted this question on netfilter mailing list, however, I
> got no response, so maybe someone around here can help me.
> 
> I am using iptables and queue packets to user space. Packets are
> either augmented (with a signature) or shortened (removal of
> signature). The augmentation works.
>  However, when removing the signature, the resulting packet contains
> the correct data, but its overall size is equal to the original
> (signed) packet. (i.e. original packet size: 83, signed packet size:
> 163)

Thomas Graf posted a patch that should fix this a couple of days
ago, check the list archives.

  reply	other threads:[~2006-03-09 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 13:30 libipq does not shorten package David Vogt
2006-03-09 15:55 ` Patrick McHardy [this message]
2006-03-10  6:28   ` David Vogt

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=44104FF7.1030104@trash.net \
    --to=kaber@trash.net \
    --cc=beunlovable@gmail.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.