From: <abirvalg@lavabit.com>
To: netfilter@vger.kernel.org
Subject: nfqueue stuck on queue length >299
Date: Thu, 13 Oct 2011 13:37:10 +0000 [thread overview]
Message-ID: <20111013133710.6c302eeb@wwwwww-701SD> (raw)
Sorry, I have to retract my previos statement.
The reason why it lifted the bar to 359 is because I changed the amount of data to copy to NFQUEUE to
nfq_set_mode ( globalqh_repeat, NFQNL_COPY_META, 0 )
whereas the 299 was hit when I had
nfq_set_mode ( globalqh_input, NFQNL_COPY_PACKET, 40 )
Of course this shows that some NFQUEUEs buffer get filled.
But my issue is not how to increase the size of this buffer, my question is:
Why after the buffer reaches its limit, it refuses to shrink and get stuck.
Am I overlooking something or is this a bug worth reporting to the developers.
Or could somebody write a simple app and confirm my finding on their machine?
next reply other threads:[~2011-10-13 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:37 abirvalg [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 14:05 nfqueue stuck on queue length >299 aletum
2011-10-13 13:27 abirvalg
2011-10-13 10:50 ` Victor Julien
2011-10-13 12:29 abirvalg
2011-10-13 9:35 ` Victor Julien
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=20111013133710.6c302eeb@wwwwww-701SD \
--to=abirvalg@lavabit.com \
--cc=netfilter@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