From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Advice for dual wifi home network
Date: Thu, 7 Mar 2013 19:24:43 -0500 [thread overview]
Message-ID: <CAA93jw7MWz4GOjGtQVg0LN_axDBf2ed-v307j-X+yrw0GPt=7w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1303071608320.30313@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 3068 bytes --]
On Thu, Mar 7, 2013 at 7:09 PM, David Lang <david@lang.hm> wrote:
> On Thu, 7 Mar 2013, Dave Taht wrote:
>
> On Thu, Mar 7, 2013 at 6:36 PM, Jonathan Morton <chromatix99@gmail.com
>> >wrote:
>>
>>
>>> On 8 Mar, 2013, at 1:22 am, Sandy McArthur wrote:
>>>
>>> I'm looking to setup a home network with two APs connected by ethernet.
>>>>
>>> I think I understand the default network settings for use as a single
>>> cerowrt network but I'm struggling how to wrap my brain around how a
>>> second
>>> router should be configured so that the second access point isn't just
>>> another level of NAT deeper inside the first router.
>>>
>>>>
>>>> Internet ---- cerowrt A ---- cerowrt B
>>>>
>>>> Configuring the B router is what is confusing me.
>>>>
>>>
>>> You will need four devices, if your modem is not itself a router:
>>>
>>> Modem ----- Router (does NAT)
>>> | |
>>> AP AP (both in bridge mode)
>>>
>>> - Jonathan Morton
>>>
>>>
>> Bridging bad idea in modern age. Routing good. Just the two cero devices
>> he
>> has is fine.,
>>
>
> Bridging is bad, but bridging with the ability to move from AP to AP can
> be far better than two routers and the user has to manually disconnect from
> one (breaking all existing connections) and attach to the other.
>
Depends on signal strength. I'd rather reconnect to wifi box "upstairs",
clearly marked as such, when upstairs. I'd rather my wifi boxes live on
different channels, so devices in each part of the house get more
bandwidth, less errors/retries and lower latency.
In the case of persistent connections these days I mostly use
mosh.mit.eduinstead of ssh, and mosh survives moving from any network
to any network
and even suspend/resume. That was my main use of persistent connections,
admittedly.
That's me.
Now, cero's preference for routing over bridging comes from the science
part, in that it was impossible to analyze the behavior of bridged
wifi/wired networks when we started, so we broke apart the 2.4 ghz, 5.xghz
and ethernet networks started exploring what it would take to make routing
easier and better.
Along the way, for example, babel gained authentication.
It certainly is possible to bridge or only partially bridge cero, it's just
more complex than routing it, presently.
Secondly, and I know I'm weird, I still generally use ahcp and babel on my
laptops and thus regain the ability to move from AP to AP, as well as act
as a mesh node for such, as well as move from ethernet to wireless and
back, transparently, without dropping connections.
That's a bit of bleeding edge technology that few have tried... and has
become harder and harder to use on unhackable android devices, in
particular.
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 4434 bytes --]
next prev parent reply other threads:[~2013-03-08 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 23:22 Sandy McArthur
2013-03-07 23:36 ` Jonathan Morton
2013-03-07 23:48 ` Dave Taht
2013-03-08 0:09 ` David Lang
2013-03-08 0:24 ` Dave Taht [this message]
2013-03-08 0:51 ` David Lang
2013-03-08 15:12 ` Sandy McArthur
2013-03-07 23:47 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7MWz4GOjGtQVg0LN_axDBf2ed-v307j-X+yrw0GPt=7w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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