[Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Kelvin Edmison]

[-- 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 --]

Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Dave Taht]

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.

> 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

Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Juergen Botz]

On 11/15/2013 02:10 AM, Dave Taht wrote:
> Well, an alternative is to bridge or use WDS.

I tried WDS at one point about a year ago but never was able
to get it to work on cerowrt.  Anybody out there using WDS
with recent cerowrt?

WDS is kind of kludgey, but it is a fairly simple "just works"
approach for small multi-AP networks.

:j

Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Dave Taht]

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

Re: [Cerowrt-devel] Recommendations for cerowrt multi-ap at home?

[Kelvin Edmison]

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

On Sat, Nov 16, 2013 at 11:55 AM, Dave Taht <dave.taht@gmail.com> wrote:

> 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.
>

Ok, I'll do that.  I appreciate the logic behind keeping 2.4 and 5 separate
from each other, so I'm considering vlan-based back-haul from the APs to
the  main router rather than reverting to a completely flat address
scheme.

> 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!
>
> Awesome!  I would be happy to try to contribute.  The build instructions
I've found on bufferbloat.net seem to be out of date; is there a more
recent description of how to get started?

Kelvin

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