All of lore.kernel.org
 help / color / mirror / Atom feed
From: nix4me <nix4me@cfl.rr.com>
To: lartc@vger.kernel.org
Subject: [LARTC] shaping passive ftp traffic
Date: Wed, 21 Jul 2004 00:42:45 +0000	[thread overview]
Message-ID: <40FDBC05.4010903@cfl.rr.com> (raw)

Hi,

I have tried unsuccesfully to limit my ftp server send speed in linux.  
I have an ipcop linux firewall/router with 2 nics.  1 nic (eth1) is 
connected to a 3mbit/384Kbit cable connection and the other (eth0) a 
switch.  Behind it i have a suse linux box and a windows box.

On the suse box i run proftpd.  I need to shape my passive ftp send 
speed to 34KBytes because if it is maxed out at 45K it slows down all 
surfing on the entire network.

I have tried running wondershaper-htb on the ipcop firewall and it 
limits my upload speed, but it still seems to slow down everything else 
a little bit.   I notice a slow www experience however my ping times are 
good. 

Is there a simple way to just put a limit on the traffic coming from the 
passive ports (50000-51000) from my proftpd computer?  I just want to 
set a limit on ftp and not affect anything else.

I have looked at all the documentation and I must admit that I dont 
understand any of it.  It all seems to be too complicated for my needs.

I hope someone out there is doing what I am trying to do.

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

             reply	other threads:[~2004-07-21  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  0:42 nix4me [this message]
2004-07-21 14:25 ` [LARTC] shaping passive ftp traffic mjoachimiak
2004-07-21 15:22 ` Piszcz, Justin Michael
2004-07-21 15:35 ` Horst Graffy
2004-07-21 16:30 ` mjoachimiak

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=40FDBC05.4010903@cfl.rr.com \
    --to=nix4me@cfl.rr.com \
    --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.