Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trivial 6in4 fix(?)
Date: Mon, 17 Jun 2013 09:35:23 +0200	[thread overview]
Message-ID: <5A07FB3F-F967-4EC2-9578-2DC82B4498F6@gmx.de> (raw)
In-Reply-To: <CAA93jw5kB4c6mAywx-1s8huwtb=40t4NRTvLEyRtqfvZLUBJ8Q@mail.gmail.com>

Hi Dave, hi Toke,


On Jun 16, 2013, at 22:57 , Dave Taht <dave.taht@gmail.com> wrote:

> On Sun, Jun 16, 2013 at 1:55 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Sebastian Moeller <moeller0@gmx.de> writes:
>> 
>>> As far as I can tell at least VDSL typically means VDSL2 and that
>>> probably means PTM instead of ATM. In essence this means you do not
>>> have to deal with ATMs 48 payload bytes per 53 byte cell transport
>>> inefficiencies. So all you need to deal with is per packet overhead.
>>> Then again I am sure you probably know that already. (Sidenote, as far
>>> as I understand (so not very far) using ATM for DSL connections with
>>> POTS service in the lower frequency range never made much sense at
>>> all, the 5 byte ATM header typically was constant and by that just
>>> ballast and the 48 byte quantization on the last mile never came with
>>> any benefits, but I digress)
>> 
>> Right, thanks. So that means the overhead is constant per (ethernet)
>> package?
> 
> So what's the MTU on VSDL2? Is PPPOE used?

	Easy to figure out empirically by hand, by finding the largest ping packet size that still passes without fragmentation (see http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_finding_optimal_mtu)

Best
	Sebastian

> 
>> -Toke
> 
> 
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html


  parent reply	other threads:[~2013-06-17  7:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 17:13 Dave Taht
2013-06-16 18:56 ` Toke Høiland-Jørgensen
2013-06-16 19:13   ` Dave Taht
2013-06-16 19:19     ` Dave Taht
2013-06-16 19:21     ` Toke Høiland-Jørgensen
2013-06-16 19:27       ` Dave Taht
2013-06-16 19:36         ` Toke Høiland-Jørgensen
2013-06-16 19:38           ` Toke Høiland-Jørgensen
2013-06-16 20:32           ` Sebastian Moeller
2013-06-16 20:55             ` Toke Høiland-Jørgensen
2013-06-16 20:57               ` Dave Taht
2013-06-16 20:58                 ` Toke Høiland-Jørgensen
2013-06-17  7:35                 ` Sebastian Moeller [this message]
2013-06-17  7:30               ` Sebastian Moeller
2013-06-17  9:44                 ` Toke Høiland-Jørgensen
2013-06-17 10:40                   ` Sebastian Moeller
2013-06-17 10:50                     ` Toke Høiland-Jørgensen
2013-06-17 12:27                       ` Sebastian Moeller
2013-07-09 15:06                       ` Sebastian Moeller
2013-06-16 19:21   ` Dave Taht
2013-06-16 19:30     ` Toke Høiland-Jørgensen

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=5A07FB3F-F967-4EC2-9578-2DC82B4498F6@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=toke@toke.dk \
    /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