From: Sam Roberts <vieuxtech@gmail.com>
To: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: can expectations be marked persistent, so they can match repeatedly until they timeout?
Date: Thu, 24 Mar 2011 10:43:31 -0700 [thread overview]
Message-ID: <AANLkTi=dEfb8f1moPE5Mp2yS5DqiB=abuJcFP99opXy9@mail.gmail.com> (raw)
I'm writing a userspace conntrack, using nfqueue and conntrack.
Creating expectations works fine, metfilter matches and allows the
expected connection.
However, unlike ftp, the negotiated ephemeral port is used by multiple
simultaneous tcp connections for some period. I'd like the expectation
to be kept in place until it times out, even when its matched.
I can create this effect by watching for the conntrack event
indicating the expectation was destroyed, and recreating it, but I'd
like to know if there is a better way.
Cheers,
Sam
next reply other threads:[~2011-03-24 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 17:43 Sam Roberts [this message]
2011-03-28 11:27 ` can expectations be marked persistent, so they can match repeatedly until they timeout? Patrick McHardy
2011-03-29 18:54 ` Sam Roberts
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='AANLkTi=dEfb8f1moPE5Mp2yS5DqiB=abuJcFP99opXy9@mail.gmail.com' \
--to=vieuxtech@gmail.com \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).