Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "techicist@gmail.com" <techicist@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Configuring cake for VDSL2 bridged connection
Date: Tue, 23 Aug 2016 16:13:19 +0100	[thread overview]
Message-ID: <CANiaOCnzMOh486gzv=hu7A7zwpA1s52EV1KR+DXBqrowOU2qRg@mail.gmail.com> (raw)
In-Reply-To: <C03A147E-9785-4E27-85C0-E52E18868791@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

Hello,

Thank you for your quick reply.

I take it that one of the DHCPs should read PPPoE?


Yes, you are quite correct. It should read: "TalkTalk uses DHCP to obtain
an IP address and not PPPoE as most other ISPs do." But I think you
understood that :)

My sync speeds on VDSL2 have been very stable for the last 84+ days so my
calculated figures will stay the same for some time, I would like to think.
My DS sync speed is 58976Kbps and thus I have calculated a reference value
of 58068Kbps based on your formula. The US sync speed is 10422Kbps and the
reference value for this is 10261Kbps.

Setting the reference values to 50%, I have: 29034Kbps for the DS; and
5130Kbps for the US. I will test with these numbers shortly. Am I right to
assume I can just paste these into the SQM interface on LuCI? I will set
the "Queuing discipline" to *cake* and the "Queue setup script" to
*piece_of_cake.qos*.

I assume also at this stage, to set "Which link layer to account for" as *none
(default)*?

I will then increment the values I have pasted into LuCI (assuming that is
correct) as you have said. At this point, with an assumed overhead of 8, do
I just choose *Ethernet with overhead...* and then set the "Per Packet
Overhead (byte)" to *8*?

Is there any benefit of going through UCI?

[-- Attachment #2: Type: text/html, Size: 1780 bytes --]

  reply	other threads:[~2016-08-23 15:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 13:44 techicist
2016-08-23 14:27 ` moeller0
2016-08-23 15:13   ` techicist [this message]
2016-08-23 20:09     ` Sebastian Moeller
2016-08-24 17:01       ` techicist
2016-08-24 17:03         ` techicist
2016-08-24 17:03           ` techicist
2016-08-24 17:16             ` Alan Jenkins
2016-08-24 19:33               ` techicist
2016-08-24 19:47                 ` Alan Jenkins
2016-08-24 19:49                   ` Alan Jenkins
2016-08-25 14:53                     ` techicist
2016-08-26  8:14                       ` Alan Jenkins
2016-08-26 11:15                         ` techicist
2016-08-26 11:29                           ` moeller0
2016-08-26 11:32                             ` techicist
2016-08-27  7:43                               ` Alan Jenkins
2016-08-27 16:17                                 ` techicist
2016-08-27 17:48                                   ` Alan Jenkins
2016-09-14 20:06                                     ` techicist
2016-09-14 20:41                                       ` Kevin Darbyshire-Bryant
2016-09-14 20:48                                         ` Sebastian Moeller
2016-09-15  9:24                                           ` Kevin Darbyshire-Bryant
2016-09-15  9:43                                       ` techicist
2016-08-26 11:52                             ` Alan Jenkins
2016-08-26 12:04                               ` techicist
2016-08-27  7:31                                 ` Alan Jenkins
2016-08-24  8:52     ` Kevin Darbyshire-Bryant

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='CANiaOCnzMOh486gzv=hu7A7zwpA1s52EV1KR+DXBqrowOU2qRg@mail.gmail.com' \
    --to=techicist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /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