From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] allocating b/w
Date: Wed, 22 Dec 2004 10:36:31 +0000 [thread overview]
Message-ID: <200412221136.31095.stef.coene@docum.org> (raw)
In-Reply-To: <20041222071416.GA25105@tranquility.scriptkitchen.com>
On Wednesday 22 December 2004 08:14, Payal Rathod wrote:
> Hi,
> A majority of our work inolves ftp to my clients' side over our
> slow connection. Now we need to allocate a greater b/w for this
> protocol. Is there anyway I can do it using lartc easily?
It can be done, but not so easy. Ftp traffic uses some random ports. But you
can filter ftp traffic if you use iptables to mark all ftp traffic (make sure
you match them all and not only the command traffic). That mark can be used
with the fw filter to put the traffic in a separate htb/cbq class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-12-22 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
2004-12-22 10:36 ` Stef Coene [this message]
2004-12-22 15:50 ` Antonios Chalkiopoulos
2004-12-23 0:13 ` nix4me
2004-12-23 0:58 ` Peter Surda
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=200412221136.31095.stef.coene@docum.org \
--to=stef.coene@docum.org \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.