From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) (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 BC1AD21F23E for ; Sat, 24 Jan 2015 07:30:47 -0800 (PST) Received: by mail-ie0-f174.google.com with SMTP id vy18so2232929iec.5 for ; Sat, 24 Jan 2015 07:30:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=j1niVc/Y3TZSrxSRMX0CT43z3SFrga/u6DEBESwwvJU=; b=I30yCfO+3WmxCzT9cpd0n5J4i73BsnrAg48vDGTljwkl9nnKTBfxpsQc2lHABqP85T 06hRqdITKFmkDc1g5cPhIz2jxMyUJPCGJulhVP0gmwGAyJrs5+Stg3R8aSUgDpij1w8z KnqgLJQq9eDLHcen/JuNmDn/Xiax3y7KnDEvvZBc2A7Jt7BIA5+AY3IYcGGlwT9tH58j lEQM03BKYmv+HV1yMlh1jr1f8C2pXdVVv+UwTbIQp418iGy9XukiHZxLgS8qWbjvx09x 8figk4WFt6klAvMx3ARhpCAEyePyNdBv3bq9Qe0Cd/ZQotzBtjdTbnmvpmzUZrKDq4vH /TIw== X-Gm-Message-State: ALoCoQngkpnqF45AJYsuyy9/G49gLE7rhjj4aTB+6vP3DdFX4d6k5srfp7IPA6UolNQkG4yNQFsj X-Received: by 10.107.34.149 with SMTP id i143mr9697362ioi.1.1422113446103; Sat, 24 Jan 2015 07:30:46 -0800 (PST) Received: from [192.168.1.148] (dhcp-24-53-240-252.cable.user.start.ca. [24.53.240.252]) by mx.google.com with ESMTPSA id l6sm2568231igv.8.2015.01.24.07.30.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 24 Jan 2015 07:30:45 -0800 (PST) References: <54B5D28A.3010906@gmail.com> <7B1EA8F0-FCB6-4A37-950F-2558FC751DE8@gmail.com> <54C038D0.1000305@gmail.com> <54C0BD22.3000608@gmail.com> <54C13F47.1010203@gmail.com> <1422111577.328132080@apps.rackspace.com> Mime-Version: 1.0 (1.0) In-Reply-To: <1422111577.328132080@apps.rackspace.com> Content-Type: multipart/alternative; boundary=Apple-Mail-40910EE7-FDC6-484B-93ED-2B7B65536428 Content-Transfer-Encoding: 7bit Message-Id: <6D05A200-67B2-4B53-959C-C4A9B443D3E9@edmison.net> X-Mailer: iPhone Mail (12B440) From: Kelvin Edmison Date: Sat, 24 Jan 2015 10:30:44 -0500 To: "dpreed@reed.com" Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic? 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, 24 Jan 2015 15:31:17 -0000 --Apple-Mail-40910EE7-FDC6-484B-93ED-2B7B65536428 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable > On Jan 24, 2015, at 9:59 AM, dpreed@reed.com wrote: >=20 > On Thursday, January 22, 2015 1:19pm, "Richard Smith" said: > =20 > > On 01/22/2015 04:18 AM, David Lang wrote: > >=20 > > >> Recently, we picked up the 11th floor as well and moved many people u= p > > >> there. I got a 3rd AP (another TP-Link AC1750) and set that one up on= > > >> a free channel with a different ESSID. > > > > > > I like to put all the APs on the same ESSID so that people can roam > > > between them. This requires that the APs act as bridges to a dedicated= > > > common network, not as routers. > >=20 > > That's the ultimate plan but for convenience of being able to easily > > select what AP I'm talking to or to be able to tell folks to move from > > one to another I've got them on different ESSIDs. It also helps me keep > > track of what RF channel things are on. >=20 > A side comment, meant to discourage continuing to bridge rather than route= . > There's no reason that the AP's cannot have different IP addresses, but a c= ommon ESSID. Roaming between them would be like roaming among mesh subnets.= Assuming you are securing your APs' air interfaces using encryption over th= e air, you are already re-authenticating as you move from AP to AP. So usin= g routing rather than bridging is a good idea for all the reasons that routi= ng rather than bridging is better for mesh. >=20 Have the MDNS problems been addressed? The last time I had a go with CeroWR= T (about 6 months ago) the problems were too severe for me to keep using it.= I had to fall back to a bridged setup for my primarily Mac environment.=20= I'm a long-time Linux user-space developer but am a complete newbie when it c= omes to developing for CeroWRT. If someone can point me at the right spot to= start working on the MDNS issues then I'll see if I can do anything to help= . =20 Regards, Kelvin --Apple-Mail-40910EE7-FDC6-484B-93ED-2B7B65536428 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On Jan 24, 2015, at 9:59 AM, dpreed@reed.com wrote:

On Thursday, January 22, 2015 1:19pm, "Richard Smith" <smithbone@gmail.com> said:

 

> On 01/22/2015 04:18 AM, David Lang wrote:
>
> >> Recently, we picked up the 11th floor as well and moved many people up
> >> there. I got a 3rd AP (another TP-Link AC1750) and set that one up on
> >> a free channel with a different ESSID.
> >
> > I like to put all the APs on the same ESSID so that people can roam
> > between them. This requires that the APs act as bridges to a dedicated
> > common network, not as routers.
>
> That's the ultimate plan but for convenience of being able to easily
> select what AP I'm talking to or to be able to tell folks to move from
> one to another I've got them on different ESSIDs. It also helps me keep
> track of what RF channel things are on.

A side comment, meant to discourage continuing to bridge rather than route.

There's no reason that the AP's cannot have different IP addresses, but a common ESSID.  Roaming between them would be like roaming among mesh subnets. Assuming you are securing your APs' air interfaces using encryption over the air, you are already re-authenticating as you move from AP to AP.  So using routing rather than bridging is a good idea for all the reasons that routing rather than bridging is better for mesh.



Have the MDNS problems been addressed?  The last time I had a go with CeroWRT (about 6 months ago) the problems were too severe for me to keep using it.  I had to fall back to a bridged setup for my primarily Mac environment. 

I'm a long-time Linux user-space developer but am a complete newbie when it comes to developing for CeroWRT. If someone can point me at the right spot to start working on the MDNS issues then I'll see if I can do anything to help.  

Regards,
  Kelvin

--Apple-Mail-40910EE7-FDC6-484B-93ED-2B7B65536428--