From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] bql-37 is out
Date: Thu, 9 Feb 2012 00:38:31 +0000 [thread overview]
Message-ID: <CAA93jw5LWettLEAxFbOA5Bpd5zNTetkz-rEuRZdAnddoyq9oeg@mail.gmail.com> (raw)
Kernel 3.2.5 + BQL
Updates
http://huchra.bufferbloat.net/~cero1/bql-smoketests/bql-37/
The only tremendously user visible change is that
multicast dns worked out so well that it's enabled
by default on all interfaces except the default gw.
This means that the routed secure networks should
'see' resources on each other.
It also means that the routed guest networks can do the
same, but not necessarily access those resources.
since I felt 'gw.local' might collide with other machines
the router defaults to cerowrt.local at the moment.
While there has a been a lot else changed 'under the hood', most
of the new-est pieces are still flying in loose formation.
That said, this seems stable enough for day to day use
as a secondary router. I need to write up a bit more
doc on how to do that well.
As for being your 'main' router, that's still a ways away.
(for example the new shaper stuff is still command line only,
and not quite done yet. It CAN be fiddled with at the
command line...)
I'm not planning any more kernel level changes for a while
it's all scripts and gui and aqm, aqm, aqm, with maybe
a little ipv6 dhcp-pd thrown in.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
reply other threads:[~2012-02-09 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw5LWettLEAxFbOA5Bpd5zNTetkz-rEuRZdAnddoyq9oeg@mail.gmail.com \
--to=dave.taht@gmail.com \
--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