From: William Katsak <wkatsak@gmail.com>
To: dpreed@reed.com
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Anyone using PPPoE with Sugarland?
Date: Sun, 6 Jan 2013 10:31:44 -0500 [thread overview]
Message-ID: <E20CC0E4-744E-4DCC-92FC-B24E7E9308D4@gmail.com> (raw)
In-Reply-To: <1357424714.707316439@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
I don't think that the QDISC variable was used in the Sugarland version of the script.
What do you have for IFACE?
Thanks,
-Bill
On Jan 5, 2013, at 5:25 PM, dpreed@reed.com wrote:
> I am using 3.7.1-1, and comparing my simple_qos.sh config with yours, I don't see any QDISC=... line in yours.
> So is it possible you need that? The egress() interface setup in simple_qos.sh uses that to set the queue discipline.
>
> -----Original Message-----
> From: "William Katsak" <wkatsak@gmail.com>
> Sent: Saturday, January 5, 2013 4:37pm
> To: "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>
> Subject: [Cerowrt-devel] Anyone using PPPoE with Sugarland?
>
> 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
[-- Attachment #2: Type: text/html, Size: 3170 bytes --]
next prev parent reply other threads:[~2013-01-06 15: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 [this message]
2013-01-06 5:31 ` Dave Taht
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=E20CC0E4-744E-4DCC-92FC-B24E7E9308D4@gmail.com \
--to=wkatsak@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.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