Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Thibaut" <hacks@slashdirt.org>
To: "Sebastian Moeller" <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Trouble with CAKE
Date: Fri, 13 Dec 2019 14:21:58 +0000	[thread overview]
Message-ID: <68b10e0a9ee0fd087dfc4f15e2c66328@slashdirt.org> (raw)
In-Reply-To: <623C176A-C78F-4FFA-905D-C59F0131804F@gmx.de>

Hi Sebastian,

December 13, 2019 3:15 PM, "Sebastian Moeller" <moeller0@gmx.de> wrote:

> Hi Thibaut,
> 
> so ADSL is both special and precious, may I recommend to follow the instructions on
> https://github.com/moeller0/ATM_overhead_detector? 

I will give it a try.

> This will either confirm the overhead settings,
> or more likely "explode" if the freeebox truely tunnels all IPv4 data through IPv6.

It does, this is a confirmed fact (and in fact trying to connect with my VDSL modem the DSLAM only speaks IPv6: I could tcpdump encapsulated frames from the BR containing IPv4 data that were destined to other subscribers - an unpleasant side effect of map-t "shared IPv4": by default free splits every IPv4 between 4 subscriber (by splitting the port range). You have to actively ask for a "full stack IP" to turn that off).

> 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'll report when the buildslave is done uploading :)

> 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.

*nod*

Thanks,
Thibaut

  parent reply	other threads:[~2019-12-13 14:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 13:43 Thibaut
2019-12-13 14:02 ` Jonathan Morton
2019-12-13 22:39   ` Thibaut
2019-12-13 22:40     ` Thibaut
2019-12-13 23:52       ` Thibaut
2019-12-14  9:50         ` Jonathan Morton
2019-12-14 10:01           ` Thibaut
2019-12-14 10:35             ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 10:56               ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 11:59                 ` Thibaut
2019-12-14 12:07                   ` Thibaut
2019-12-14 12:09                   ` Jonathan Morton
2019-12-14 12:11                     ` Thibaut
2019-12-14 12:59                       ` Toke Høiland-Jørgensen
2019-12-14 14:04                         ` Thibaut
2019-12-14 21:35                           ` Toke Høiland-Jørgensen
2019-12-13 14:13 ` Thibaut
2019-12-13 14:15 ` Sebastian Moeller
2019-12-13 14:21 ` Thibaut [this message]
2019-12-13 18:44   ` Thibaut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68b10e0a9ee0fd087dfc4f15e2c66328@slashdirt.org \
    --to=hacks@slashdirt.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox