Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Kelvin Edmison <kelvin@edmison.net>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?
Date: Fri, 15 Nov 2013 00:03:39 -0500	[thread overview]
Message-ID: <CALErE73u_bEzyyU4z+12q7wHLsROBtd0z5rm=TLBy5R7juOAyQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

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.

My use case is a single cable internet connection, and a footprint that
needs 2 APs to provide sufficient high-performance coverage.  I would like
to provide guest and internal WiFi networks at both APs, so that both will
be reasonably fast.

I initially set up mesh mode according to wiki directions, and have it
mostly up and running.  I can ping from a machine connected to the second
router, across the mesh, to the first router and out to the internet.

The problems I am experiencing are that
1) the second router by default isn't set to forward DNS requests to the
first router, so I have to configure each of the interfaces manually to
supply the IP of the primary router as the DNS server
2) both routers try to maintain DNS for home.lan and do not exchange
information.
3) the Macs in the household go a little nuts when they change networks as
they seem to detect the mdns repeater as a conflict when trying to assume
ownership of the hostname on the new network.  My Mac's hostname has
changed repeatedly to avoid the conflict and is now tesla-71.local.

Is mesh the right way to go here?  What are best practices for tackling
these issues?

Thanks,
  Kelvin

[-- Attachment #2: Type: text/html, Size: 1537 bytes --]

             reply	other threads:[~2013-11-15  5:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15  5:03 Kelvin Edmison [this message]
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

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='CALErE73u_bEzyyU4z+12q7wHLsROBtd0z5rm=TLBy5R7juOAyQ@mail.gmail.com' \
    --to=kelvin@edmison.net \
    --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