Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: William Katsak <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Anyone using PPPoE with Sugarland?
Date: Sat, 5 Jan 2013 21:31:31 -0800	[thread overview]
Message-ID: <CAA93jw5rZTy7uLHFBNSfS7YJ3gMUbt=tfwEJ+ruvLW7p=zCtBw@mail.gmail.com> (raw)
In-Reply-To: <F3C8CE17-E50D-4B6D-9CB6-4F1C1D9CF0DE@gmail.com>

Netanalyzer's metrics are wrong when used with a fair queuing or codel
based system. They use a single udp flood to measure the "queue" when
in the "fq" portion of fq_codel there are 1024 by default, and when
codel kicks in, queue depth is reduced eventually to a level that tcp
would expect, but has no effect on a single udp flood.

Use a ping vs a big upload as your test, or the rrul test, after
setting your up/download appropriately.



On Sat, Jan 5, 2013 at 1:37 PM, William Katsak <wkatsak@gmail.com> wrote:
> Hello,
>
> I am experimenting with using Cero/Sugarland on a PPPoE connection, and can't seem to find a config of simple_qos that works well.
>
> The service is DSL, PPPoE, 3M/768K. Without any qos, the router works well, as expected. When I try to use simple_qos, the clients have trouble loading websites (hangs while loading, etc).
>
> Netlyzer shows upstream buffering of about 650ms, consistently. I have tried various higher and lower values for UPLINK and DOWNLINK, but nothing seems to help. Anyway, I think 15-20% below link should be fine.
>
> Here is my config:
> UPLINK=550
> DOWNLINK=1900
> DEV=ifb0
> IFACE=ge00
> DEPTH=42
> TC=/usr/sbin/tc
> FLOWS=8000
> PERTURB="perturb 0" # Permutation is costly, disable
> FLOWS=16000 #
> BQL_MAX=3000 # it is important to factor this into the RED calc
>
> CEIL=$UPLINK
> MTU=1492
> ADSLL=""
> PPOE=yes
>
> Couple of things I am unsure about:
> 1) Should the IFACE be ge00 or pppoe-ge00?
> 2) Should the MTU be the pppoe mtu (1492) or the ethernet (1500)
>
> One last thing: I have the lan split up into VLAN interfaces se00.1, se00.100, and se00.200. Everything otherwise works as expected with these, but could the naming be breaking something?
>
> If anyone is willing to share a working configuration it would be much appreciated.
>
> Thanks,
> Bill Katsak
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  parent reply	other threads:[~2013-01-06  5:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 21:37 William Katsak
2013-01-05 22:25 ` dpreed
2013-01-06 15:31   ` William Katsak
2013-01-06  5:31 ` Dave Taht [this message]
2013-01-06 15:31   ` William Katsak
2013-01-06 21:47   ` Sebastian Moeller

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='CAA93jw5rZTy7uLHFBNSfS7YJ3gMUbt=tfwEJ+ruvLW7p=zCtBw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=wkatsak@gmail.com \
    /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