From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org, srn@coolheads.com
Cc: smartwires@gmail.com, greearb@candelatech.com
Subject: Re: Network stops passing traffic randomly
Date: Thu, 28 May 2020 21:19:39 +0200 [thread overview]
Message-ID: <1970963.L7oaDoOIKM@sven-edge> (raw)
In-Reply-To: <c022e032-f283-8432-2d3e-3013cf91773b@coolheads.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Thursday, 28 May 2020 21:03:20 CEST Steve Newcomb wrote:
> I have seen Sven's remark about unicast packets. I'm not sanguine about
> getting Qualcomm to fix a driver for an older product.
I am slightly confused now about the mentioning of the candelatech driver.
Just to sync both of you up:
* Are you using ath10k-ct with the ath10k-firmware*-ct or are you using ath10k
with the ath10k-firmware*?
* And are you using IBSS or 802.11s (meshpoint with mesh_fwding=0)? Is this
encrypted or not encrypted?
> The Candela
> Technologies driver refuses to function on the DFS channels (100, 116,
> 132), which in my large, populous US residential environment work far,
> far better than channels 36 or 149.
Was this reported to Ben Greear?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-28 19:19 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 [this message]
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
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=1970963.L7oaDoOIKM@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=greearb@candelatech.com \
--cc=smartwires@gmail.com \
--cc=srn@coolheads.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