Linux Netfilter discussions
 help / color / mirror / Atom feed
From: lising <xing.starwill@gmail.com>
To: netfilter@lists.netfilter.org
Subject: [Fwd: Questions about the netfilter_queue]
Date: Thu, 26 Jul 2007 19:10:38 +0800	[thread overview]
Message-ID: <1185448238.4506.11.camel@lising-desktop> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Forwarded message - Questions about the netfilter_queue --]
[-- Type: message/rfc822, Size: 790 bytes --]

From: lising <xing.starwill@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Questions about the netfilter_queue
Date: Thu, 26 Jul 2007 18:25:17 +0800
Message-ID: <1185445508.4506.7.camel@lising-desktop>

hi, 

  I wrote some code to parse the packets captured by the
netfilter_queue. I used the following the iptables rules on my PC:

 iptables -A OUTPUT -p tcp --dport ${PORT} -j NFQUEUE --queue-num 0
 iptables -A INPUT  -p tcp --sport ${PORT} -j NFQUEUE --queue-num 0

When I try to transfer a file about 500M to the server, after several
seconds, the capturing process can't capture any more packets.

Do you all encounter the same problem? Thanks a lot.

Lixing
July.26 2007


                 reply	other threads:[~2007-07-26 11:10 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=1185448238.4506.11.camel@lising-desktop \
    --to=xing.starwill@gmail.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox