From: Roger Sala <rsala@ssci.com>
To: netfilter@vger.kernel.org
Subject: Packets occasionally not queued
Date: Tue, 14 Sep 2010 12:53:31 -0400 [thread overview]
Message-ID: <4C8FA88B.5090405@ssci.com> (raw)
I have some basic netfilter queue code that diverts packets with the
following two rules:
iptables -A OUTPUT -m tos --tos 0xe0/0xe0 -j QUEUE
iptables -A FORWARD -m tos --tos 0xe0/0xe0 -j QUEUE
It works as expected almost all the time, but occasionally I see cases
where Wireshark indicates that the packet was received at the nic, but
my code doesn't log the recv() of it.
I had assumed that my receive buffer was sometimes being overrun, but
now that I'm throttling back the traffic, I see cases where isolated
packets just don't get queued, so I assume its a case off competing for
resources with other processes on the machine.
Is there anything I can do, such as increasing the priority of my
program, to enhance the likelyhood of receiving all the packets I am
filtering on?
Thanks
reply other threads:[~2010-09-14 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C8FA88B.5090405@ssci.com \
--to=rsala@ssci.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