From: "Jay Brussels" <jay@dslx.net>
To: 'The list for a Better Approach To Mobile Ad-hoc Networking'
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] good dual radio node?
Date: Wed, 15 Oct 2014 10:44:19 -0400 [thread overview]
Message-ID: <156a01cfe886$809ba760$81d2f620$@dslx.net> (raw)
In-Reply-To: <744721D9-A7D7-4F59-93E2-ED4DA8939D53@altermundi.net>
Have you deployed 100 radios in a single mesh? We are used to doing frequency allocation/management and with a single radio mesh AP all radios need to be on the same frequency correct? We are planning on using dual-radio nodes but the 2.4G will be for the client access and the 5.8G will be for the mesh.
This is a huge project with 6,000 nodes in a one square mile community.
-----Original Message-----
From: B.A.T.M.A.N [mailto:b.a.t.m.a.n-bounces@lists.open-mesh.org] On Behalf Of Gui Iribarren
Sent: Wednesday, October 15, 2014 3:55 AM
To: The list for a Better Approach To Mobile Ad-hoc Networking; dan
Subject: Re: [B.A.T.M.A.N.] good dual radio node?
Tplink wdr3500, we've deployed more than 100, running nice with barrierbreaker tplink wdr3600 is identical, but with gigabit ethernet in some places, one or the other will be easier to find (availability) and cheaper.
Tplink wdr4300 is like wdr3600 but with 3x3 on one of the bands (5ghz IIRC) so it has an extra, single-band antenna
HTH,
cheers!
On October 14, 2014 7:34:56 PM CDT, dan <dandenson@gmail.com> wrote:
>Anyone have any recommendations for a good dual radio mesh node for
>batman-adv that won't break the bank? I'm looking at having wired
>clients, but two mesh radios to keep throughput high. 802.11n radios
>also required.
>
>Thanks!
prev parent reply other threads:[~2014-10-15 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 0:34 [B.A.T.M.A.N.] good dual radio node? dan
2014-10-15 7:55 ` Gui Iribarren
2014-10-15 12:49 ` dan
2014-10-15 12:51 ` dan
2014-10-15 14:15 ` Gui Iribarren
2014-10-15 14:57 ` dan
2014-10-15 22:50 ` tjhowse
2014-10-15 14:44 ` Jay Brussels [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='156a01cfe886$809ba760$81d2f620$@dslx.net' \
--to=jay@dslx.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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