All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roy" <roy@xxx.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: wondershaper + htb limiting ftp sends
Date: Mon, 09 Feb 2004 03:33:02 +0000	[thread overview]
Message-ID: <004e01c3eebd$6cee92f0$030aa8c0@t> (raw)
In-Reply-To: <87n07tcaxf.fsf@iki.fi>

if you need only hardlimit ftp trafic then better find something about this
in proftp manual

But if you want it to depend on other trafic(if you have other servers) then
you will need to use htb anyway,
tc filters are very primitive and cant match port range well, but you can
adjust ftp port ranges in such way that you can use binary masks to match
them.



----- Original Message ----- 
From: "Nuutti Kotivuori" <naked@iki.fi>
To: <lartc@mailman.ds9a.nl>
Sent: Monday, February 09, 2004 3:13 AM
Subject: [LARTC] Re: wondershaper + htb limiting ftp sends


> mark ryan wrote:
> > Or, ideally, I would like to limit proftpd itself...howeve
> there
> > doesn't seem to be a way to do that with linux.  Windows can
> but I
> > guess Linux cant.
>
> Proftpd does have plenty of ways to limit the bandwidth specifically
> for certain commands only and directions wished and all that.
>
> Just peruse the documentation. Operating system has nothing to do with
> it.
>
> -- Naked
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-02-09  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-09  1:13 [LARTC] Re: wondershaper + htb limiting ftp sends Nuutti Kotivuori
2004-02-09  3:33 ` Roy [this message]

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='004e01c3eebd$6cee92f0$030aa8c0@t' \
    --to=roy@xxx.lt \
    --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.