From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 91EE121F1EF for ; Thu, 14 Nov 2013 21:03:41 -0800 (PST) Received: by mail-vb0-f52.google.com with SMTP id f12so2392444vbg.25 for ; Thu, 14 Nov 2013 21:03:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=vTilvxJOkobi7LRYEcVcv00MVsi5/kh6DeOx0kVInrQ=; b=f7b8S2wW3UjtCNwQUCQEBHQU1OkdE5r9ehANC6aJ4OMNDSeGrXaew6INR1uJ/op4jX MAlHEwCWvR+2a1vp9VUSBEB6kQpouBsqTGuUX1O0FqUUUgNE7qkIDdDzsHi4SFQtk6po rn3TbtroTpgdDjC14hiTbwZ+sn1qqg1jUHXTcYmbEdUr8OznMW8g+pf+yxutO7Sb2Ye5 lPhOzedhzyPwranIWODss4FE4VKti1Gd68wqy/lRW6y9x8CQ1kNbpQlrNTNUmy/pWUF4 p1niVWvpHDI5Rth8ddZe22Awb697g+66L26G4bxZ2t6S16h77llfwWMUTDd/tjCkyYxE Z+9Q== X-Gm-Message-State: ALoCoQn8pUJKqcqA1hDB72lQOHX7Q1QJpADajAKB9kLUgWcJHs4dv3+pMCKPwS+uWMIUf5+f0e7f MIME-Version: 1.0 X-Received: by 10.220.244.132 with SMTP id lq4mr74451vcb.31.1384491820043; Thu, 14 Nov 2013 21:03:40 -0800 (PST) Received: by 10.58.109.134 with HTTP; Thu, 14 Nov 2013 21:03:39 -0800 (PST) Date: Fri, 15 Nov 2013 00:03:39 -0500 Message-ID: From: Kelvin Edmison To: cerowrt-devel Content-Type: multipart/alternative; boundary=089e0115f68220eb3904eb301fc6 Subject: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 05:03:42 -0000 --089e0115f68220eb3904eb301fc6 Content-Type: text/plain; charset=ISO-8859-1 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 --089e0115f68220eb3904eb301fc6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I've been experimenting with two WNDR3800s a= nd meshing, and I'm starting to wonder if meshing is the right answer f= or a typical residential user who needs multiple APs.

My use c= ase is a single cable internet connection, and a footprint that needs 2 APs= to provide sufficient high-performance coverage.=A0 I would like to provid= e guest and internal WiFi networks at both APs, so that both will be reason= ably fast.

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

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

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

Thanks,
=A0 Kel= vin
--089e0115f68220eb3904eb301fc6--