Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Rudi Starcevic <tech@wildcash.com>
To: netfilter@lists.netfilter.org
Subject: Re: limit speed of file transfer
Date: Mon, 24 Jan 2005 09:38:07 -0800	[thread overview]
Message-ID: <41F5327F.3070803@wildcash.com> (raw)
In-Reply-To: <001001c5001e$d80df760$0201a8c0@micah>

Hi,

An option may be to use SSH with RSYNC instead of SCP.
The Rsync command has a bandwidth limit option.

I use it like this:

rsync -avz --bwlimit 10 -e ssh remoteuser@remotehost:/remote/dir /this/dir/

Check the 'man' pages for more info on the 'bwlimit' option.

HTH
Regards
Rudi.

Micah Wedemeyer wrote:

>Hi,
>
>My system consistently locks up on file transfers across the LAN.  When
>transferring a file to it using scp, it dies after less than 5 seconds.
>However, if I use it to download a file from the Internet (using wget),
>it does just fine.
>
>I have heard that my motherboard (a Via Epia MII) has DMA problems and
>that high Ethernet traffic is known to lock them up.  My theory is that
>the Internet connection is slow enough to not hit whatever magic
>threshold causes the crash.  So, I was hoping to find a way to limit the
>speed of transfers with scp and ftp so that they also don't lock up the
>machine.
>
>I asked on a few message boards, and they all mentioned iptables.  I've
>never used it before, and am a total noob when it comes to networking
>stuff.  So, I was hoping that the people on this list could point me in
>the right direction of where to start.
>
>To sum up:  I need a way to limit the speed of incoming file transfers
>using ftp or scp.
>
>Any help would be greatly appreciated,
>Micah
>
>
>
>
>  
>



  parent reply	other threads:[~2005-01-24 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22  1:08 limit speed of file transfer Micah Wedemeyer
2005-01-22  1:54 ` Jason Opperisano
2005-01-22  7:28 ` R. DuFresne
2005-01-22 20:22 ` Jose Maria Lopez
2005-01-24 17:38 ` Rudi Starcevic [this message]
2005-01-24  0:05   ` R. DuFresne

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=41F5327F.3070803@wildcash.com \
    --to=tech@wildcash.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