From: Tore Anderson <tore@linpro.no>
To: netfilter@lists.netfilter.org
Subject: Distinguishing between individual tracked connections
Date: 24 Nov 2002 02:46:17 +0100 [thread overview]
Message-ID: <uiuhee7spsm.fsf@nfsd.linpro.no> (raw)
I've been trying for the last few weeks to find a way to distinguish
between individual connections, but to no avail.
What I want to accomplish is to `mark' outgoing connections as I please,
and be able to detect these marked connections in the INPUT chain. In
other words, a match+target couple similar to the MARK-stuff already
included, only that it should work for tracked connections instead of
individual packets.
More specifically, I want to send all outgoing packets generated by the
`squid' user trough my QoS setup (easy, thanks to -m owner and -j MARK),
and to send incoming packages destined for the squid process through the
intermediate queuing device instead of simply accepting them.
Is there some way of accomplishing this?
Please send me carbon copies of eventual answers, I don't subscribe.
Kind regards,
--
Tore Anderson
reply other threads:[~2002-11-24 1:46 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=uiuhee7spsm.fsf@nfsd.linpro.no \
--to=tore@linpro.no \
--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