Am Dienstag, 11. Mdrz 2008 21:05:31 schrieben Sie: > On 2008-03-10, Marc Rene Arns <[EMAIL PROTECTED]> wrote: > > For several reasons it would be better, if I could limit the traffic on > > the webserver side. I thought, I would configure pf with altq to limit > > the bandwidth of the ssh-client. > > Is this any good? > > $ cat /usr/ports/net/trickle/pkg/DESCR > trickle is a portable lightweight userspace bandwidth shaper. It can > run in collaborative mode (together with trickled) or in stand alone > mode. trickle works by taking advantage of the unix loader preloading. > Essentially it provides, to the application, a new version of the > functionality that is required to send and receive data through sockets. > It then limits traffic based on delaying the sending and receiving of > data over a socket. trickle runs entirely in userspace and does not > require root privileges. Whow! That was really helpful. I used trickle with the sftp client and expect.pm to trottle my large downloads and it seems to work, at least on the server-side.
The ruby sftp library I previously used segfaulted with large files (200MB). What I like about trickle is that you can use it now and then (for scripts) and could have your general limits handled by pf. > > > Or is it part of the ssh protocol to agree on a lower bandwidth based on > > the > > > number of lost packets? > > TCP backs off when it detects packet loss. I thought so, but wasn't sure if one can rely upon it. (Cause the customers internet connection is the needle in this scenario). Thank you very much! Best Regards, Benny
