Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trivial 6in4 fix(?)
Date: Mon, 17 Jun 2013 11:44:42 +0200	[thread overview]
Message-ID: <87hagxnkad.fsf@toke.dk> (raw)
In-Reply-To: <00B68282-44B0-4392-8AEF-68144A50D94E@gmx.de> (Sebastian Moeller's message of "Mon, 17 Jun 2013 09:30:18 +0200")

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

Sebastian Moeller <moeller0@gmx.de> writes:

> Honestly, I think the best thing to do is not so much assume ATM or
> lack of ATM, but simply measure it :)

Right, doing the ping test with payload sizes from 16 to 113 packets
gives me an almost completely flat ping time distribution ranging from
20.3 to 21.3 ms (see attached graphic). So probably I'm on PTM...

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

$ ping -c 1 -s $((1500-28)) -M do www.debian.org
PING www.debian.org (128.31.0.51) 1472(1500) bytes of data.
1480 bytes from senfl.debian.org (128.31.0.51): icmp_seq=1 ttl=45 time=114 ms

--- www.debian.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 114.522/114.522/114.522/0.000 ms

$ ping -c 1 -s $((1500-27)) -M do www.debian.org
PING www.debian.org (128.31.0.51) 1473(1501) bytes of data.
From 10.42.3.5 icmp_seq=1 Frag needed and DF set (mtu = 1500)

--- www.debian.org ping statistics ---
0 packets transmitted, 0 received, +1 errors

So the MTU seems to be 1500 bytes.

Now, how do I figure out what the PTM overhead is and feed it to HTB? :)

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-06-17  9:44 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
2013-06-17  7:30               ` Sebastian Moeller
2013-06-17  9:44                 ` Toke Høiland-Jørgensen [this message]
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=87hagxnkad.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@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