From: Maxim Kharlamov <mcs@podsolnuh.biz>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] nov 3 cerowrt status
Date: Sun, 4 Nov 2012 13:24:35 +1300 [thread overview]
Message-ID: <CADq85jbR8fzoJ7aqzSRSdxki49BOeGCzigGdTFhNg3=PXVNYhg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7Rq2N7Je8+rHwdKp4-zsEPNe=KYZja_72j9rASgK5rtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4587 bytes --]
Hi Dave,
Sugarland works great indeed. I've been using it on my main router since
the time it was released.
I don't experiment with *_codel though.
My ISP advertises /48 IPv6 network prefix over DHCPv6-PD - not sure what
I'm doing wrong, but I've never hit bug 413, even though I've been running
IPv6 network for almost a year now.
There were some minor glitches with previous versions of cerowrt, but
generally it just works.
Thanks,
Max
On 4 November 2012 12:18, Dave Taht <dave.taht@gmail.com> wrote:
> I'm kind of assuming that with the list as quiet as it is, that
> sugarland is working well for everyone, with the exception of the
> reported bugs? You've got it deployed as your main router, life is
> good, things like simple_qos.sh are working....? Is anyone mucking
> with efq_codel, nfq_codel?
>
> I've been sitting on the cerowrt-3.3 tree, waiting to rebase on the
> openwrt AA final. Don't know when that will happen.
>
> While doing some testing of dhcpv6 on a real cable network with ipv6,
> I hit bug 413. There are a few other bugs in there, and all the same
> bugs we had last month.
> http://www.bufferbloat.net/projects/cerowrt/issues/413
>
> While we wait for openwrt AA to stablize, I have been tracking openwrt
> head. Linux 3.6 support for the ar71xx architecture has arrived!
>
> Rather than muck with cero, it has been simpler to just do builds of
> the ubnt code (picostation 2HP) as it evolves towards being
> functional. There has been a lot of movement and re-organization of
> the next-gen openwrt trees going on, upgrades to fundamental things
> like toolchains, etc. Lot of breakage.
>
> I have HIGH hopes that with the Linux 3.6 TCP small queues I can
> finally get router based measurements to where I trust them, and also
> be able to run heavier workloads (as TSQ uses less memory)
>
> Moving forward:
>
> I've been working on a specification for some very difficult string of
> network tests, that no router (including cerowrt) can pass today. If
> you are interested in commenting on a draft, please email me
> privately.
>
> I'm giving a talk at ELC this week in barcelona, about what the heck
> we can do to fix wifi. I'll be all through europe from now til
> December 15th, expecting to make stops in london, berlin, and paris. I
> enjoyed meeting up with jesper and toke from the main bloat list,
> accidentally, last week,in copenhagen, as well as running into
> old^H^H^H aging gracefully embedded linux revolutionaries like matt
> locke and mark ovek, now of Linaro at the same conference.
>
> There are some interesting homenet related meetings at ietf in Atlanta
> this coming week, they are broadcast live and available via jabber.
>
> Mark Townsley of homenet intends to demo 8 boxes running some ospf
> based prefix distribution code, I'm hoping a few cerowrt based routers
> get plugged into the testbed too. Jim gettys is at ietf as well of
> simon kelly of dnsmasq fame, as well as the minstrel andrew mcgregor -
> good gang of debloaters there - go! go drinking! The mdnsext working
> group is looking promising, too.
>
> Cerowrt donations continue to pour in, and I'm about 2 weeks behind on
> updating the credits page. Apologies. I have a plan for the donations
> - second up is a second SSD for snapon! first up was obtaining a new
> server at linode to host some new stuff, which I based in london, and
> have now forgotten how to access.
>
> I would like to get a release of cerowrt out on the 20th, with a
> gui-enabled simple_qos script (needs a better name - Ceroshaper?
> suggestions?), fixes for the ipv6 problem and closing the dnsmasq port
> hole (bug 411)
>
> would love a refresh of quagga-re, ccn, and other tools, too, and to
> get mdlna fixed, but the above - notably the gui to simple_qos - is
> going to take all my available braincells.
>
> I would like to find a way, going forward, to spread around more of
> the work and find more ways to speed the processes, particularly that
> of CI and getting regular builds done. I've had a couple people
> volunteer stuff privately, but not a lot of time to think about it. I
> don't want to be the bottleneck... and I really want to get started on
> 3.6 as soon as possible.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 5535 bytes --]
prev parent reply other threads:[~2012-11-04 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 23:18 Dave Taht
2012-11-04 0:24 ` Maxim Kharlamov [this message]
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='CADq85jbR8fzoJ7aqzSRSdxki49BOeGCzigGdTFhNg3=PXVNYhg@mail.gmail.com' \
--to=mcs@podsolnuh.biz \
--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