Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.2-1 dev release + owamp
Date: Wed, 31 Jul 2013 22:37:07 +0100	[thread overview]
Message-ID: <F7B0C688-A28F-4DCB-9318-B74C706A6470@imap.cc> (raw)
In-Reply-To: <BC8259B7-8E9C-4758-9A30-162C7C8ECE17@gmx.de>

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

tc -s -d class show dev ge00

class htb 1:10 parent 1:1 leaf 110: prio 0 quantum 1500 rate 700000bit ceil 700000bit burst 1599b/1 mpu 0b overhead 0b cburst 1599b/1 mpu 0b overhead 0b level 0 
 Sent 15809014 bytes 115190 pkt (dropped 4733, overlimits 0 requeues 0) 
 rate 3616bit 3pps backlog 0b 0p requeues 0 
 lended: 115190 borrowed: 0 giants: 0
 tokens: 263560 ctokens: 263560

class htb 1:1 root rate 700000bit ceil 700000bit burst 1599b/1 mpu 0b overhead 0b cburst 1599b/1 mpu 0b overhead 0b level 7 
 Sent 15809014 bytes 115190 pkt (dropped 0, overlimits 0 requeues 0) 
 rate 3616bit 3pps backlog 0b 0p requeues 0 
 lended: 0 borrowed: 0 giants: 0
 tokens: 263560 ctokens: 263560

class fq_codel 110:1b8 parent 110: 
 (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  deficit 84 count 0 lastcount 0 delay 10us



tc -s -d class show dev ifb0
class htb 1:10 parent 1:1 leaf 110: prio 0 quantum 1500 rate 7000Kbit ceil 7000Kbit burst 1598b/1 mpu 0b overhead 0b cburst 1598b/1 mpu 0b overhead 0b level 0 
 Sent 192992612 bytes 168503 pkt (dropped 0, overlimits 0 requeues 0) 
 rate 17096bit 4pps backlog 0b 0p requeues 0 
 lended: 168503 borrowed: 0 giants: 0
 tokens: 27454 ctokens: 27454

class htb 1:1 root rate 7000Kbit ceil 7000Kbit burst 1598b/1 mpu 0b overhead 0b cburst 1598b/1 mpu 0b overhead 0b level 7 
 Sent 192992612 bytes 168503 pkt (dropped 0, overlimits 0 requeues 0) 
 rate 17096bit 4pps backlog 0b 0p requeues 0 
 lended: 0 borrowed: 0 giants: 0
 tokens: 27454 ctokens: 27454

class fq_codel 110:cc parent 110: 
 (dropped 10, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  deficit -198 count 1 lastcount 1 ldelay 2.3ms
class fq_codel 110:1d9 parent 110: 
 (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  deficit 226 count 0 lastcount 0 ldelay 2us
class fq_codel 110:1de parent 110: 
 (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  deficit 238 count 0 lastcount 0 ldelay 10us
class fq_codel 110:345 parent 110: 
 (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  deficit 226 count 0 lastcount 0 delay 9us

I changed the hard coded values in /usr/lib/aqm/functions.sh to arbitrary values, rebooted and obtained the same results. Both reflect the 7000kbit/s down and 700kbit/s up I entered in the window. I ticked the adsl box. Altering the value in functions.sh and unticking the box, with reboot, produced the same outcome.



traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 173.194.41.128
traceroute to google.com (173.194.41.128), 64 hops max, 52 byte packets
 1  172.30.42.1 (172.30.42.1)  0.631 ms  0.323 ms  0.249 ms
 2  * * *
 3  10.1.3.234 (10.1.3.234)  22.596 ms  21.241 ms  22.392 ms
 4  * 10.1.3.214 (10.1.3.214)  27.018 ms  26.703 ms
 5  10.1.4.249 (10.1.4.249)  29.682 ms  28.923 ms  27.479 ms
 6  * * *
 7  * 209.85.252.186 (209.85.252.186)  30.379 ms *
 8  72.14.238.55 (72.14.238.55)  25.745 ms  25.345 ms  25.594 ms
 9  lhr08s03-in-f0.1e100.net (173.194.41.128)  27.566 ms  27.390 ms  27.663 ms

mtr shows packet losses at hops 2-5 
10.1.3.* are Internet Watch Foundation.

Netalyzr was used. I appreciate it is an imperfect metric.






On 31 Jul 2013, at 21:38, Sebastian Moeller <moeller0@gmx.de> wrote:

> tc -s -d class show dev ge00


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

  reply	other threads:[~2013-07-31 21:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 18:45 Dave Taht
2013-07-26  5:20 ` Dave Taht
2013-07-26  6:21   ` Fred Stratton
2013-07-26  9:54     ` Sebastian Moeller
2013-07-26 10:51     ` David Personette
2013-07-26 14:31       ` Fred Stratton
2013-07-26 15:51         ` Sebastian Moeller
2013-07-31 19:50           ` Fred Stratton
2013-07-31 20:38             ` Sebastian Moeller
2013-07-31 21:37               ` Fred Stratton [this message]
     [not found]                 ` <7AA8F2EC-633F-4DF6-86D1-73B7BAB6DDB7@gmx.de>
2013-07-31 22:35                   ` Fred Stratton
     [not found]                     ` <94CA76B3-44B9-41E8-9893-864BBEEFB70D@gmx.de>
2013-08-03 10:36                       ` Fred Stratton
2013-08-03 18:56                         ` Fred Stratton
     [not found]                         ` <AE353C99-CFF9-49F7-B3CB-912DD2078E2F@gmx.de>
2013-08-03 21:28                           ` Fred Stratton
2013-08-04 13:03                           ` Fred Stratton
2013-08-11 20:25   ` Sebastian Moeller
2013-08-11 21:52     ` Dave Taht
2013-08-12  8:55       ` Sebastian Moeller
     [not found] <46820144-E1DD-4858-A2B6-38F95D2894DB@imap.cc>
2013-08-05 10:47 ` Fred Stratton
2013-08-07 13:38   ` Sebastian Moeller
2013-08-07 23:21     ` Fred Stratton
2013-08-08  9:41       ` Sebastian Moeller
2013-08-08 10:26         ` Fred Stratton

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=F7B0C688-A28F-4DCB-9318-B74C706A6470@imap.cc \
    --to=fredstratton@imap.cc \
    --cc=cerowrt-devel@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