public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Steve Newcomb <srn@coolheads.com>
To: Ben Greear <greearb@candelatech.com>,
	b.a.t.m.a.n@lists.open-mesh.org, smartwires@gmail.com
Subject: Re: Network stops passing traffic randomly
Date: Tue, 2 Jun 2020 22:06:40 -0400	[thread overview]
Message-ID: <f99daabf-2081-c6af-779d-580f8d352b59@coolheads.com> (raw)
In-Reply-To: <8cb674e5-26b2-e992-61e6-5969cc50358f@candelatech.com>



On 6/2/20 4:02 PM, Ben Greear wrote:
> Have you tried using IPQ4019 based systems?  They seem pretty 
> affordable, and the 3-radio Linksys MR8300 & EA8300 seem pretty stable
> in my testing recently (in AP mode, not tested mesh).
No.  Used, on E-bay, the cheaper of the two, the EA8300  is at least 
twice as expensive as what we're using now.  To buy a dozen or so in 
hope of getting them to work with Batman is out of the question, alas.

Ben, I fully understand your lack of incentive to spend your time on 
drivers for older hardware.  This is not your problem, really. (Unless, 
like me, you are seeking ways to address the digital divide, where low 
entry cost is the key consideration.  Every dollar cheaper means more 
people can connect, which was important even before the pandemic began.  
I selected these Archer [AC]7 v[245] units because there are so many of 
them for sale that they are kind of hard to sell.  True, I didn't know 
the QCA driver would limit me to 3 nodes per mesh, nor did I know your 
driver couldn't support encryption nor DFS, at least not out of the 
box.  It looked like a reasonable bet at the time; with 2 drivers to 
choose from, what could go wrong?  Oh, well, nothing worthwhile was ever 
easy.)

Steve

  reply	other threads:[~2020-06-03  2:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  8:35 Network stops passing traffic randomly smartwires
2020-05-25  8:43 ` Sven Eckelmann
     [not found]   ` <CAL3ir7+RWLrYOzjNQh1VwiKg1sxSgHZMwwqx=9xSfXFnFjE_KQ@mail.gmail.com>
2020-05-25 13:22     ` Sven Eckelmann
2020-05-25 13:45     ` Sven Eckelmann
2020-05-28  1:05   ` smartwires
2020-05-28  8:46     ` Sven Eckelmann
     [not found]   ` <cf75d66e-b0ac-632d-34e6-681ed9c6769d@coolheads.com>
2020-05-28 19:31     ` Sven Eckelmann
2020-05-28 21:17       ` Steve Newcomb
2020-05-28 19:03 ` Steve Newcomb
2020-05-28 19:19   ` Sven Eckelmann
2020-05-28 19:22     ` Ben Greear
2020-05-28 20:59     ` Steve Newcomb
2020-05-28 21:28       ` Ben Greear
2020-06-02  1:41         ` Steve Newcomb
2020-06-02 12:40           ` Steve Newcomb
2020-05-29  0:13   ` smartwires
2020-06-02  2:05     ` Steve Newcomb
2020-06-02 20:02       ` Ben Greear
2020-06-03  2:06         ` Steve Newcomb [this message]
2020-06-03 12:48           ` Ben Greear
2020-06-03 15:35             ` Steve Newcomb
2020-06-03 16:42               ` Ben Greear
2020-06-03 17:56                 ` Steve Newcomb

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=f99daabf-2081-c6af-779d-580f8d352b59@coolheads.com \
    --to=srn@coolheads.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=greearb@candelatech.com \
    --cc=smartwires@gmail.com \
    /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