From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C062F3CB47 for ; Fri, 13 Dec 2019 09:15:11 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1576246510; bh=I6cqrbOjJJQ+JdoNh/aLQcvhKRA+ko7/xk60rrSxdKU=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=DnlBEXxm5QYWAc0fpTLP4DTfF4iZMIrImMt3W5wqKPifWpfzXDuctDIRpbWTtR6hc YddzNkz9D8NGhOTuB8jkuWp0JNQqnNI/V0J1dHezVGodvnRgzCUIhjTPXCDlRC+hB+ MZHK34X6P9I4gT3qJCGOopABLOJWBrOH2XliJi+I= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.11.12.33] ([134.76.241.253]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N7zFj-1hatmn2bUh-01546e; Fri, 13 Dec 2019 15:15:10 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Sebastian Moeller In-Reply-To: <1d359153abfc413b4f61c647437427d6@slashdirt.org> Date: Fri, 13 Dec 2019 15:15:09 +0100 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <623C176A-C78F-4FFA-905D-C59F0131804F@gmx.de> References: <1d359153abfc413b4f61c647437427d6@slashdirt.org> To: Thibaut X-Mailer: Apple Mail (2.3445.104.11) X-Provags-ID: V03:K1:BW0/4rGpZaDF7zSHPNqd1pyqupLR3XT8Zd5kfqMYKNmdduf6AR6 cRJi7XtT8OO0HXBwKo6Tf81ZeiAIbzMsqQkMbMvJl4AeFsDxKqmMnv7GKAIMMBB8j483zXY XUJTMZvcdVzcYX5plEMJguhiajAXTWMgrk5zGT1TmvuufmeOl0SFMMkDnL+WO++yICl2ElB lB+VLZfOZmdADgcj009BA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:0CfE7qpnUbc=:63FIbAEQjwSis1y7BW2Jrm NmMo16FrlPMorN3zsg4xtZuDT7B13Vo59WyrLXqXQuAybqHfN/YE4KKzSJ5k78z+b37QYl1uT TC2HHnneAbGhhf/SpYniJrsZ8OF52699EPn/LdanQt+K88D6PG/7mwMj1gcTbrGe/n2qTeSic YseVARLDeEhx7jdpP9kPVmpOtlttucoJSMzn76QcpHySMVBpo7M+W0Xlw/It8WlsFSDEPBlhW VHBsns2BzHOKZ5dNPpVdAdJTextbAaJl68su1Yx7A5MVHARahl4bQMjLVDdNWJbuMdKK9TqqS xOp/7yYOCsswl4hIXKp4bs97n8yvAAMMLevzOaQSnVvjLs+eAkrnr9PHkim9Bbfzn/NjiLWhu thpKBXt3wxKYs88axQ+/Q2eioMAEY6vrocCI497++WbqETJ9afQBvsYeM4mlzfOzdgYfuzeqw Nf6l2nAuZ5iWnc5doAmKR0Oc6+jW/6AITFks+y4MagThf9pPfj/a9rlq5rPdqyiXs2xeHjX1+ 6H9elGpGMj+INWEdN1GIaT26fAObuKjRoEtLc7CYMqMq/Zkpgp284lY/x+O/9qOm0sQkHPSoe IdKKF8bdKPv/in3BpfkaPOWYJhkheQuYyOFdoAOj/LPYbf00ZvtJQhyRXcWb6UFB1vBu3fZRQ 8rZu+pm2JODt/W/zo56MehpZKlXEqLmkR9vMuqJVs7PRwQo7SoDVaJhvdf/gEVGXkY6zYggFK 4gWiAqhq1o89m2Tizq/KXolWb7Rk4HW7tbFic2xMQj0qj+CwSWEb1Dah2qeb+RJn8IM9KKzoy ch64NoiV9znD3LSZn5oZRyXRN3xVoBGdMwEMptsWvV9NLjWQOdC4Kv8gm6MBIx3Mo9f+VfX6H /CgyOuRluslS3sGkkwj6/UKsaTvDO9IT0jm2JgYtc14pQa4OCbBfDtqtDgjSyRRe9hPzVvf8r p+268a8Af+vGqnaOdJ8LsENcMLlWXcZ0i7RfNK7tS+pDjpp5fth508eDuJ5EYAQVNH9BfLR2o gd5SJhnsKCzXsGlHJHN4JGe9OswgIGx2bIxKf79eR0tasMMmxYz+mIVJgE6pjK8ajLaUulAas 3LYjDTbGDyejWjphGn+2NVGtIAOR3oLSNlZ+dSLwWMvq7IjfTBbdROoFt+vamucQXYqQj339N kQbW+DYxI22SYhkj86vbdj9EFklJSIbzcmFXCKwc9Gh5YIo5E5JvxMFZPIgc4z0Y7xFqvME5I V04lGtN27/+4qY0IwCqFA7w4TzhyhRNhyVjVOJGEJNH3UT1Dze2gdgGXXM5c= Subject: Re: [Cake] Trouble with CAKE X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2019 14:15:12 -0000 Hi Thibaut, so ADSL is both special and precious, may I recommend to follow the = instructions on https://github.com/moeller0/ATM_overhead_detector? This = will either confirm the overhead settings, or more likely "explode" if = the freeebox truely tunnels all IPv4 data through IPv6. In both cases = the results should be interesting. As a quick test, what is the textual = output from the "Share Your Results" box on = https://www.speedguide.net/analyzer.php? I would not be amazed if the issue might be related to having a whoping = 40 bytes more of unaccounted for per-packet-overhead (in combination = with ATM/AAL5's lovely per packet padding). But that might all be moot = if it is/was caused by a kernel issue. Best Regards Sebastian > On Dec 13, 2019, at 14:43, Thibaut wrote: >=20 > Hi list, >=20 > I've been using CAKE on my DSL-connected Linux router for the last few = years, and it worked well until very recently. Two things happened: >=20 > 1) My ISP (French "Free") switched my DSLAM to native IPv6, which for = the time being means that I had to revert to using their set-top-box = (Freebox) instead of the VDSL2 model I was using in bridge mode until = then (CAKE in "bridged-ptm ether-vlan" mode) > 2) I upgraded my router from 3.16 (Devuan Jessie) to 4.9 (Devuan = ASCII) >=20 > Since then, no matter which setup I use, I cannot get CAKE to work as = intended. Specifically, any long-standing best effort stream (such as a = remote rsync) will be throttled to a near grinding halt even though = there is no other significant traffic going on. Some random bursts can = be seen (with iftop) but nothing ever gets close to half the maximum = bandwidth. This is notably affecting the OpenWRT buildbots I'm hosting = on this link. >=20 > In details: >=20 > $ uname -a > Linux rapid-ts1 4.9.0-11-686 #1 SMP Debian 4.9.189-3+deb9u2 = (2019-11-11) i686 GNU/Linux >=20 > Cake commit: 183b320 RFC 8622 diffserv3, 4 & 8 LE PHB support >=20 > cake setup on the wan iface: bandwidth 1Mbit diffserv3 dual-srchost = nat nowash ack-filter split-gso bridged-vcmux no-sce > the available ATM uplink bandwith is 1.2Mbps, I tried going as low as = 700kbps, disabling ack-filter and setting "conservative" to see if it = would make a difference, it wouldn't in any significant way: the upload = would still be severely throttled. I also tried disabling the ingress = leg to get that out of the equation: also no difference. >=20 > As I broke rule #1 of any setup upgrade (by changing both the link - = VDSL to ADSL - and the running kernel), I can't tell for sure where the = fault lies; however I must add something about the "native IPv6 DSLAM" = bit: >=20 > Free uses map-e/map-t, i.e. ipip6 tunnels on its native v6 DSLAMs. The = Freebox still offers a public IPv4 to the connected router, but inside = the Freebox there is an ipip6 tunnel setup to encapsulate the IPv4 = traffic into IPv6, a tunnel over which I have no control. I wonder if = this encapsulation and its associated overhead could be throwing CAKE = computations off? FWIW, my router now operates in dual-stack mode, with = both a public IPv4 and a public IPv6 (although for the time being my LAN = remains IPv4 only). >=20 > I haven't (yet) found a way to connect directly to the DSLAM without = the Freebox (using my VDSL modem as I did before), so I can't get around = this particular blackbox. >=20 > I hope this provides enough detail, I'm happy to expand as needed: I = would really want my CAKE back :) >=20 > Cheers, > Thibaut > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake