From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Link layer adaptation VDSL2 - Basis for 8 byte overhead?
Date: Tue, 28 Apr 2015 17:32:32 +0200 [thread overview]
Message-ID: <0EB27232-6810-4B4F-A9BD-4C9466BF650F@gmx.de> (raw)
In-Reply-To: <553F8932.6050009@darbyshire-bryant.me.uk>
Hi Kevin,
On Apr 28, 2015, at 15:20 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> Hi,
>
> Enquiring mind here :-) Reading http://www.bufferbloat.net/projects/cerowrt/wiki/Everything_you_wanted_to_know_about_Link_Layer_Adaptation and the linked to email discussion, I'm curious as to where the 8 byte overhead recommendation for VDSL2 comes from. Is this assumption that PPPoE is being used?
Not exactly, for all we know using PPPoE and a VLAN on a VDSL2 link results in:
VDSL2 header:
VDSL (IEEE 802.3-2012 61.3 relevant for VDSL2): 2 Byte PPP + 6 Byte PPPoE + 4 Byte VLAN + 1 Byte Start of Frame (S), 1 Byte End of Frame (Ck), 2 Byte TC-CRC (PTM-FCS), = 16 Byte
Or in other words, 8 byte either just reflect PPPoE or the real VDSL2 headers plus a VLAN (I am still unsure what to do with the ethernet FCS).
But I think you are right that initially the 8 byte came as a recommendation jus to handle PPPoE overhead ;)
> Based on that assumption it raises further questions in my mind:
>
> My ISP supplier (Sky in the UK) provide straight ethernet over PTM, with DHCP to obtain a public IP address, so in theory no PPPoE overhead unlike other ISPs offering 'fibre' (ha!) broadband in the UK. There appears to be a tagged VLAN on the WAN port, therefore I think the correct overhead in my case is 4 (VLAN) and for everyone else it should be 12 (VLAN + PPPoE)
See above. BUT this might or might not be relevant; my ISP actually throttles my link to a speed below the VDSL2 link speed and accounts for 16 bytes overhead at the BRAS level, so ymmv… I had a nice way to figure out the per packet overhead on ATM links (actually only ATM links using AAL5, but that should be all of them ;) ), but for PTM I have no real idea...
>
> Please correct my assumptions :-)
The other thing I am uncertain of is the VLAN tag, if your router terminates it will the kernel account for it or not? Not that I can test this currently as my modem terminates the VLAN “silently"
Best Regards & hope that helps
Sebastian
>
> Kevin
>
> --
> Thanks,
>
> Kevin@Darbyshire-Bryant.me.uk
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-04-28 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 13:20 Kevin Darbyshire-Bryant
2015-04-28 15:32 ` Sebastian Moeller [this message]
2015-04-28 16:07 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0EB27232-6810-4B4F-A9BD-4C9466BF650F@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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