From: Fred Stratton <fredstratton@imap.cc>
To: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd: Re: CeroWrt 3.10.24-8 badly bloated?
Date: Fri, 27 Dec 2013 19:10:07 +0000 [thread overview]
Message-ID: <52BDD08F.2000904@imap.cc> (raw)
In-Reply-To: <CAA93jw4+FJXpOxA2KLYrqM22Y92BYrhdftOUyWnnz-74BLF4KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
I upgraded to 3.10.24-8 on 2013-12-23.
I modified /etc/fixdaemons, adding
/etc/init.d/sqm restart
input the appropriate sqm settings, transcribed from aqm
rebooted
and the build works very well. For ADSL2+ here, it is the best so far.
On 27/12/13 18:55, Dave Taht wrote:
>
> A race condition appears to have crept in...
>
> ---------- Forwarded message ----------
> From: "Dave Taht" <dave.taht@gmail.com <mailto:dave.taht@gmail.com>>
> Date: Dec 27, 2013 10:47 AM
> Subject: Re: [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated?
> To: "Richard E. Brown" <richb.hanover@gmail.com
> <mailto:richb.hanover@gmail.com>>
> Cc:
>
> Probably didn't start sqm properly
>
> Restart it by hand via /etc/init.d/sqm restart
>
> tc -s qdisc show dev ge00
>
> Should show htb and fq codel.
>
> On Dec 27, 2013 10:36 AM, "Rich Brown" <richb.hanover@gmail.com
> <mailto:richb.hanover@gmail.com>> wrote:
>
> So I screwed up my courage and replaced my 3.10.18-? firmware in
> my primary router with 3.10.24-8. That version had worked well as
> a secondary, so I figured, What the heck... Let's give it try.
>
> The result was not pretty. I set my link speeds in the SQM page,
> chose the defaults for the Queue Discipline tab, and link layer to
> ATM with no additional overhead for my DSL link.
>
> Ping times to google are normally ~51-54 msec. But when I fired up
> speedtest.net <http://speedtest.net>, they jumped to 1500-2500
> msec. Is there something I should look at before reverting? Thanks.
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> <mailto:Cerowrt-devel@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 3801 bytes --]
next prev parent reply other threads:[~2013-12-27 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 18:36 [Cerowrt-devel] " Rich Brown
[not found] ` <CAA93jw7oS-NsBVbzHHUyVKb=0yo-yX9h-j-okafvM2c=DBJwDA@mail.gmail.com>
2013-12-27 18:55 ` [Cerowrt-devel] Fwd: " Dave Taht
2013-12-27 19:10 ` Fred Stratton [this message]
2013-12-27 19:15 ` Dave Taht
2013-12-27 19:20 ` Fred Stratton
2013-12-27 19:25 ` Sebastian Moeller
2013-12-27 19:49 ` Dave Taht
2013-12-27 20:20 ` Fred Stratton
2013-12-28 0:07 ` Sebastian Moeller
2013-12-28 1:14 ` Dave Taht
[not found] ` <52BE494E.7010904@imap.cc>
2013-12-28 3:46 ` Fred Stratton
2013-12-28 10:33 ` Fred Stratton
2013-12-27 20:41 ` Fred Stratton
2013-12-27 20:59 ` [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated?/Not anymore Rich Brown
2013-12-27 21:13 ` Fred Stratton
2013-12-27 21:14 ` Fred Stratton
2013-12-28 0:10 ` 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=52BDD08F.2000904@imap.cc \
--to=fredstratton@imap.cc \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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