From: Kelvin Edmison <kelvin@edmison.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Stuart Cheshire <cheshire@apple.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?
Date: Sat, 16 Nov 2013 20:56:19 -0500 [thread overview]
Message-ID: <CALErE73udK281-z-zVjMJTmzxW_v-=f2kgHh+8KtPhBaERT==g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw63LktP+PmPxCX5_yn_rwj-T5QdWtU1EJFB2w3rQ7mzag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
On Sat, Nov 16, 2013 at 11:55 AM, Dave Taht <dave.taht@gmail.com> wrote:
> On Thu, Nov 14, 2013 at 9:10 PM, Dave Taht <dave.taht@gmail.com> wrote:
> > On Thu, Nov 14, 2013 at 9:03 PM, Kelvin Edmison <kelvin@edmison.net>
> wrote:
> >> I've been experimenting with two WNDR3800s and meshing, and I'm
> starting to
> >> wonder if meshing is the right answer for a typical residential user who
> >> needs multiple APs.
> >
> > Well, an alternative is to bridge or use WDS.
>
Ok, I'll do that. I appreciate the logic behind keeping 2.4 and 5 separate
from each other, so I'm considering vlan-based back-haul from the APs to
the main router rather than reverting to a completely flat address
scheme.
> stuart cheshire is starting up a project to make dns-sd with a hybrid
> > proxy work right, so we can git rid of the klugey multicast forwarding
> > causing this problem (on WAY more networks than just ceros, this is a
> > problem on many campus's worldwide) and actually use the defined
> > standard for dealing with multiple mdns subnets.
> >
> > http://tools.ietf.org/html/draft-cheshire-mdnsext-hybrid-02
> >
> > some code already exists as fallout of the homenet wg and was
> > demonstrated at ietf. It works...
> >
> > It will be a huge relief to have this problem resolved sometime in the
> > near future. developers wanted!
>
> Awesome! I would be happy to try to contribute. The build instructions
I've found on bufferbloat.net seem to be out of date; is there a more
recent description of how to get started?
Kelvin
[-- Attachment #2: Type: text/html, Size: 2455 bytes --]
prev parent reply other threads:[~2013-11-17 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 5:03 Kelvin Edmison
2013-11-15 5:10 ` Dave Taht
2013-11-16 11:42 ` Juergen Botz
2013-11-16 16:55 ` Dave Taht
2013-11-17 1:56 ` Kelvin Edmison [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='CALErE73udK281-z-zVjMJTmzxW_v-=f2kgHh+8KtPhBaERT==g@mail.gmail.com' \
--to=kelvin@edmison.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cheshire@apple.com \
--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