From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HdZfG-0005ln-WC for garchives@archives.gentoo.org; Mon, 16 Apr 2007 22:27:15 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l3GMPKJ1022743; Mon, 16 Apr 2007 22:25:20 GMT Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.233]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l3GMJFmJ014016 for ; Mon, 16 Apr 2007 22:19:15 GMT Received: by wr-out-0506.google.com with SMTP id 60so1626655wri for ; Mon, 16 Apr 2007 15:19:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ASZI6/io3udMRtApOkjZIrLA0SLwxn9NXLb60xA5Ds4Rq7430RwiE/ZZ4IqzeJudB+9l7h06bwEFVUo0Cbosvw8ccreVbT/UncfCXnoC+uoRxzFxb6zBCS0x2L3gdFj4PPT9SGiSl7nTY52CikC/KYXZ4A+9LLNbOCx1sfCJhtU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TN2sJbApGNAOU9b6sMcHS6mQxlRWi+aBJJFoUuoBqrwEu89/6DesDLLswAYlURj+rzd3JAyC5JVOE2p23oRq62QUpBaUa3In+2xCkuXjO5d701WYytitfBM7zplYl+P8oKjYL9E83fFwD1w3EQagskp/9eCTB99zMifOXPmkKKw= Received: by 10.114.26.1 with SMTP id 1mr2101947waz.1176761954382; Mon, 16 Apr 2007 15:19:14 -0700 (PDT) Received: by 10.114.174.18 with HTTP; Mon, 16 Apr 2007 15:19:14 -0700 (PDT) Message-ID: <49bf44f10704161519w7e5b9010p9062c74fbeb4dcea@mail.gmail.com> Date: Mon, 16 Apr 2007 15:19:14 -0700 From: Grant To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Packet Shaping In-Reply-To: <20070416223151.70937275.hilse@web.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49bf44f10704131124o33353cc6xa5de097eba5fb052@mail.gmail.com> <20070413210444.acbef9ac.hilse@web.de> <49bf44f10704140837q4cfe2498ie065d7a608023f79@mail.gmail.com> <20070414190735.cd7f1b58.hilse@web.de> <49bf44f10704160900m65f3e8beh5a044d38d8761a1d@mail.gmail.com> <20070416223151.70937275.hilse@web.de> X-Archives-Salt: 468f3628-c219-45d7-a094-909f27c55621 X-Archives-Hash: 3caa5d7f903cb82b0ba4113738cddf2f > Well, the problem is that limiting inbound traffic is absolutely > unreliable. From the numbers given, I guess you're on DSL, right? (Just > like me, BTW.) If you were on cable, well, there's not a lot you can do > since the media is unreliable w/ regard to your share of it. But I > think you're talking about stable bandwith. If you're not lucky, all > those peers out there flood your inbound traffic line. You can't shape > this on your side, it's absolutely an issue to be resolved on the DSLAM > your DSL modem connects to. OTOH, those routers usually don't do very > sophisticated packet inspection... So it's all about cutting expensive > connections down very early. This is the even more true for > applications that are somewhat hasty in changing their requested and > incoming traffic. So first try cutting down the maximum even more. Take > a few measures and see what is actually saturated: upstream or > downstream. If it's in fact neither, it's a configuration issue. It's actually my upload rate that's difficult to limit. That's not inbound traffic right? - Grant -- gentoo-user@gentoo.org mailing list