netdev - Re: Bypass flow control problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101229084909.GS2754@reaktio.net>
Date:	Wed, 29 Dec 2010 10:49:09 +0200
From:	Pasi Kärkkäinen <pasik@....fi>
To:	Alkis Georgopoulos <alkisg@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Bypass flow control problems

On Wed, Dec 29, 2010 at 10:47:15AM +0200, Alkis Georgopoulos wrote:
> ???????? 27-12-2010, ?????????? ??????, ?????? ?????? 15:43 +0200, ??/?? Pasi Kärkkäinen
> ????????????:
> > You could set up QoS rules on the server to limit the network speed per client..
> 
> That sounds promising. I'll try to limit the rate of packages that the
> server sends to each client to 90 Mbps and see if that works around the
> flow control problem. Any tips for a good method to do that?
> 

I guess you need to read the Linux Advanced Routing and Traffic Control howto..
it has examples how to use the Linux QoS stuff.

There are also some scripts out there that make it easier to set it up.

-- Pasi

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html