From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-22-ewr.dyndns.com (mxout-063-ewr.mailhop.org [216.146.33.63]) by lists.bufferbloat.net (Postfix) with ESMTP id 71F532E00FC for ; Mon, 31 Jan 2011 01:52:19 -0800 (PST) Received: from scan-21-ewr.mailhop.org (scan-21-ewr.local [10.0.141.243]) by mail-22-ewr.dyndns.com (Postfix) with ESMTP id A81892E6DC for ; Mon, 31 Jan 2011 09:52:17 +0000 (UTC) X-Spam-Score: -1.0 (-) X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 209.85.216.43 Received: from mail-qw0-f43.google.com (mail-qw0-f43.google.com [209.85.216.43]) by mail-22-ewr.dyndns.com (Postfix) with ESMTP id 53AAE2EBC0 for ; Mon, 31 Jan 2011 09:52:13 +0000 (UTC) Received: by qwk3 with SMTP id 3so5182091qwk.16 for ; Mon, 31 Jan 2011 01:52:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=RzX38sSgG0lps0da1T24Zrha+0bZV0peOxo2lx6+XLg=; b=VrXMExofoXxLkefLjD56pCxExFXk9t9dDPeeFwzQDWM8WWMEfTMw940RGTnAA0u3fT Oqud7LKAY18DU9fCC57uZXBk4lIFg+tds7wnkfoMHkTjnlwsNCSOfskxEU7HCNjCvSBQ uUFbAgY6QJ0bhBtQUP1o8OzJK1B9nH/d328Gc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hICpR2nwD1245by8UjrLPYhwvHmmjt5b35m6bYAPGDKM/O0DVjNmfkYHLvWsTp2B6i wkxpUHsTOyEaVX2B4wPrQ96wbhap+3hMrD2tYfO7xSMtsB3mGl9c/OLyNcF7e90esEQR QQ3afSvEc+TAyR5L5EfoIzgHyGe6zjOUH+8hs= MIME-Version: 1.0 Received: by 10.229.246.145 with SMTP id ly17mr3917693qcb.67.1296467532835; Mon, 31 Jan 2011 01:52:12 -0800 (PST) Received: by 10.229.25.7 with HTTP; Mon, 31 Jan 2011 01:52:12 -0800 (PST) Date: Mon, 31 Jan 2011 10:52:12 +0100 Message-ID: From: Luca Dionisi To: bufferbloat list Content-Type: text/plain; charset=ISO-8859-1 Subject: [Bloat] new network deploy X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 09:52:19 -0000 Hi all I am starting to deploy a local TCP/IP network in order to test a new routing protocol. Info on the routing protocol: www.netsukuku.org Info on the network being deployed: pyntk.blogspot.com It is separated from the Internet at the moment. I ask for advices on how to make it as free as possible from the bufferbloat problem. I would also make some tests on this network and report here what I find out about bufferbloat. Further information: * every node active on the network will be a modern linux host. * all of the links between nodes will be on wifi or on cables owned by the users. That is, no VPN links over the Internet. * if it is needed I can list the actual chipset of ethernet cards and radio devices. * most of the wifi links will be managed by radio chipset installed in linux hosts (mostly ad-hoc, no strange do-it-all out-of-control embedded-router-bridge-repeater devices) There is also a particular case. Two linux nodes are connected via a VPN at layer 2 (I use tinc) over another network with static addresses and routing. This network is formed by the 2 linux hosts and 2 embedded radio devices, from Ubiquity, which run AirOS, a derived of OpenWRT. In this particular case, where do I have to look for possible buffers? Is it enough to look the tx-queue of the virtual nic or do I have to check also the settings of the Ubiquity devices? --Luca