From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 8.mo64.mail-out.ovh.net (8.mo64.mail-out.ovh.net [46.105.72.247]) (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 134213CB35 for ; Fri, 11 Oct 2019 10:56:58 -0400 (EDT) Received: from ex3.mail.ovh.net (unknown [10.109.143.66]) by mo64.mail-out.ovh.net (Postfix) with ESMTPS id EB91A1C3A88 for ; Fri, 11 Oct 2019 16:56:56 +0200 (CEST) Received: from DAG6EX2.indiv3.local (172.16.2.12) by DAG3EX3.indiv3.local (172.16.2.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 11 Oct 2019 16:56:56 +0200 Received: from DAG6EX1.indiv3.local (172.16.2.11) by DAG6EX2.indiv3.local (172.16.2.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1779.2; Fri, 11 Oct 2019 16:56:55 +0200 Received: from DAG6EX1.indiv3.local ([fe80::5d21:496b:431d:8acc]) by DAG6EX1.indiv3.local ([fe80::5d21:496b:431d:8acc%5]) with mapi id 15.01.1779.004; Fri, 11 Oct 2019 16:56:55 +0200 From: Guillaume ROBIER To: "bloat@lists.bufferbloat.net" Thread-Topic: Bufferbloat on 4G Connexion Thread-Index: AdWARBAOeFGGgCG8TKe8oActC1aSOQ== Date: Fri, 11 Oct 2019 14:56:55 +0000 Message-ID: <775be8cd393d47aabdac5097e9ae054c@icow-systems.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [80.215.212.173] Content-Type: multipart/alternative; boundary="_000_775be8cd393d47aabdac5097e9ae054cicowsystemscom_" MIME-Version: 1.0 X-Ovh-Tracer-Id: 10968798369820503696 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrieehgdekgecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecu X-Mailman-Approved-At: Tue, 22 Oct 2019 15:31:33 -0400 Subject: [Bloat] Bufferbloat on 4G Connexion X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2019 14:56:58 -0000 --_000_775be8cd393d47aabdac5097e9ae054cicowsystemscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am new to this mailing list and I discovered the bufferbloat in December = 2018. I work on 4G routers and the bufferbloat is very present on this type= of link (4G). I contact you today to find out if people have experimented = with solutions on this type of link or have configuration suggestions, beca= use the classic fq_codel or piece_of_cake and pie do not allow to fix the b= ufferbloat. My architecture: ARM/MIPS with dd-wrt and OpenWRT kernel 3.10.14+ Thank you in advance. Sincerely, Guillaume --_000_775be8cd393d47aabdac5097e9ae054cicowsystemscom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

I am new to this mailing list and I discovered the b= ufferbloat in December 2018. I work on 4G routers and the bufferbloat is ve= ry present on this type of link (4G). I contact you today to find out if pe= ople have experimented with solutions on this type of link or have configuration suggestions, because the classi= c fq_codel or piece_of_cake and pie do not allow to fix the bufferbloat.

 

My architecture: ARM/MIPS with dd-wrt and OpenWRT &n= bsp;kernel  3.10.14+

 

Thank you in advance.

 

Sincerely,

Guillaume

--_000_775be8cd393d47aabdac5097e9ae054cicowsystemscom_--