Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Kelvin Edmison <kelvin@edmison.net>
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 08:55:59 -0800	[thread overview]
Message-ID: <CAA93jw63LktP+PmPxCX5_yn_rwj-T5QdWtU1EJFB2w3rQ7mzag@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6srNA+JhwuxyyjVcvZNDniuQu_eXi4BBjXu70d3Fb49w@mail.gmail.com>

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.
>
>
>>
>> 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
>
> ? that's one line
>
>> 2) both routers try to maintain DNS for home.lan and do not exchange
>> information.
>
> That is something of a problem. The right thing here would be to use subnets
>
> downstairs.home.lan
>
> upstairs.home.lan
>
> so you can have the databases be correctly separated.

I am incidentally allergic to guis. You can change all references to
home.lan to upstairs.home.lan (or whatever you choose) with:

sed -i s/home.lan/upstairs.home.lan/g /etc/config/*

you can then point your other dns properly with one line in /etc/config/dhcp

        list server '/downstairs.home.lan/172.30.43.1' # well,
whatever name and ip you used


>
>> 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.
>
> 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!
>
>>
>> Is mesh the right way to go here?  What are best practices for tackling
>> these issues?
>>
>> Thanks,
>>   Kelvin
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  parent reply	other threads:[~2013-11-16 16: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 [this message]
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=CAA93jw63LktP+PmPxCX5_yn_rwj-T5QdWtU1EJFB2w3rQ7mzag@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cheshire@apple.com \
    --cc=kelvin@edmison.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