From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.44-3 released
Date: Wed, 18 Jun 2014 16:41:17 -0400 [thread overview]
Message-ID: <21916.1403124077@sandelman.ca> (raw)
In-Reply-To: <CAA93jw7JxTupbPywRtK9N2H2hw0e5vdpbDXEDP0JcYO47jkfOw@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> wrote:
> + huge resync with openwrt head
Good... how can I tell which version of which in?
Did you happen to see any netifd changes that might fix a problem I had on
the weekend with 10.36, whereby netifd basically would not setup bridges.
On a reboot, it might set up 1 bridge, but never two, and never would set
them up incrementally.
(I just want my a,b,g,n wifi bridged on the same subnet, but routed to the
rest of the world. I want a saparate bridge for for guest and secure.)
> - the hnetd, mdns, and mdnsproxy work is still in progress, and these
> daemons are built but not installed by default. And installing them
> leads to major system instability, so don't do that unless you are
> prepared to debug over a serial port and factory reflash.
I bought 10x of the TTL/USB frobs from aliexpress, I hope to solder things
up, and find a pretty way to be able to close the case.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2014-06-18 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 1:44 Dave Taht
2014-06-18 20:41 ` Michael Richardson [this message]
2014-06-18 11:49 Steven Barth
2014-06-18 17:37 ` Dave Taht
2014-06-18 17:54 ` Steven Barth
2014-06-18 20:42 ` Michael Richardson
2014-06-18 20:43 ` Dave Taht
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=21916.1403124077@sandelman.ca \
--to=mcr@sandelman.ca \
--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