From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (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 3CE1E21F1BC for ; Sat, 16 Nov 2013 08:56:01 -0800 (PST) Received: by mail-wi0-f178.google.com with SMTP id hn6so2236251wib.11 for ; Sat, 16 Nov 2013 08:55:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2QmbaB0XJAyCp+QAunIiXX5zr7BA7U67w24GLBQTGUQ=; b=0Q1aOCsryo10B8E1qt3EF2cJv5unVYBkdbKFiw9bKUI1VGklUvXkTdMBo+MG40FV83 UoWBPGHEtVEOd9tLdeuT4KnkoR1uqEi29/hhq0OLdPwh4V8PqibkdsNz6qy/KJgwsGl8 diM6qtSb6w2RgqljLTWFADHwAgoE8j0iysFfjwJy/+vEgSatKNdjzNeLa7UB8vmlse9K 8cqniypzc+kmixh/pHgjCAmoqSchzqbfsWf/xd3C2/pyBY1stu037kL4pPprcA9G56UI 8Is+uQ1f+iQew6cRKn/iE/C5aWgU0XwmkqBtXBzEHAhV5CWqK6ohIZU9CmpP4+4FGLg4 XYLA== MIME-Version: 1.0 X-Received: by 10.180.184.14 with SMTP id eq14mr11201689wic.56.1384620959093; Sat, 16 Nov 2013 08:55:59 -0800 (PST) Received: by 10.217.51.5 with HTTP; Sat, 16 Nov 2013 08:55:59 -0800 (PST) In-Reply-To: References: Date: Sat, 16 Nov 2013 08:55:59 -0800 Message-ID: From: Dave Taht To: Kelvin Edmison Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Stuart Cheshire , cerowrt-devel Subject: Re: [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: Sat, 16 Nov 2013 16:56:01 -0000 On Thu, Nov 14, 2013 at 9:10 PM, Dave Taht wrote: > On Thu, Nov 14, 2013 at 9:03 PM, Kelvin Edmison wrot= e: >> 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 li= ke >> to provide guest and internal WiFi networks at both APs, so that both wi= ll >> 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 secon= d >> 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 subn= ets > > 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/dhc= p 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 assum= e >> ownership of the hostname on the new network. My Mac's hostname has cha= nged >> 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=E4ht > > Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html