Linux Netfilter discussions
 help / color / mirror / Atom feed
From: alexb@atix.com.br
To: raymondl@knowledgefactory.co.za
Cc: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: QoS on dynamic port allocation protocols
Date: Thu, 13 Mar 2003 10:40:53 -0300 (BRT)	[thread overview]
Message-ID: <1047562853.3e708a65c21a5@www.spsul.com.br> (raw)
In-Reply-To: <1047533324.11445.64.camel@raylinux.internal>

But how do I distinguish RELATED connection from ftp and H323 ?
If I only whant to limit bandwidht for ftp and not for H323, how could I tell
iptable to mark only the RELATED packets from ftp connections ?

Thanks,

Alex

Cópia Raymond Leach <raymondl@knowledgefactory.co.za>:

> On Thu, 2003-03-13 at 03:09, Antonio Paulo Salgado Forster wrote:
> > 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
> 
> Depending on your QoS setup, you could use the -m state --state
> RELATED
> and the fwmark patch to mark the packets. Then your QoS filters could
> be
> triggered by the fwmark values.
> 
> 


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13  1:09 QoS on dynamic port allocation protocols Antonio Paulo Salgado Forster
2003-03-13  5:28 ` Raymond Leach
2003-03-13 13:40   ` alexb [this message]
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=1047562853.3e708a65c21a5@www.spsul.com.br \
    --to=alexb@atix.com.br \
    --cc=netfilter@lists.netfilter.org \
    --cc=raymondl@knowledgefactory.co.za \
    /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