Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Antonio Paulo Salgado Forster" <aforster@br.ibm.com>
To: netfilter@lists.netfilter.org
Subject: QoS on dynamic port allocation protocols
Date: Wed, 12 Mar 2003 22:09:16 -0300	[thread overview]
Message-ID: <OFA83BF598.09B2B5B9-ON83256CE8.000228A8@LocalDomain> (raw)

Hello all,

      I'm trying to apply QoS rules on protocols that use dynamic port
allocation on secondary connections such as ftp or H323 that have a
specific iptables helper to handle them, and the problem begins when the
secondary connections startup.  Would the connmark module mark also the
seconday connections if you tells it to mark the main flow?  Or, is there
any way to to match a packet using, at the same time, the -m state --state
RELATED match and check if the related connection belongs to a ftp session?

Any ideas are appreciated. Thanks in advance.

Forster



             reply	other threads:[~2003-03-13  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  1:09 Antonio Paulo Salgado Forster [this message]
2003-03-13  5:28 ` QoS on dynamic port allocation protocols Raymond Leach
2003-03-13 13:40   ` alexb
2003-03-13 14:07     ` Eric Leblond
2003-03-13 14:54     ` Jozsef Kadlecsik

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=OFA83BF598.09B2B5B9-ON83256CE8.000228A8@LocalDomain \
    --to=aforster@br.ibm.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