From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: joe@careyhome.org
Subject: Re: Problems with Multiple Interfaces
Date: Tue, 13 Apr 2021 13:53:16 +0200 [thread overview]
Message-ID: <6830943.IaFvOplyQc@prime> (raw)
In-Reply-To: <20210410003953.1234.9147@diktynna.open-mesh.org>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Saturday, April 10, 2021 2:39:53 AM CEST joe@careyhome.org wrote:
> Linus and Simon,
>
> Thank you for your responses.
>
> I did try "batctl ping" and the adjacent device was unreachable. I could
> see it with "batctl n". I did not try a simple IPv6 link local ping.
> However, I could see it using "iw dev mesh_5g station dump"
>
> I agree that it feels like a problem with ath10k reporting the data rate
> incorrectly (or not at all).
>
> I am going to try upgrading to the latest release, but it will be a few
> days. I'll let you know how it goes.
>
> Thanks again,
>
> --Joe
Sounds great! You may want to take some more measures to find out if the
packets are actually getting transferred, e.g. doing tcpdump on both the
sending and receiving side. If you see packets sent but not received on the
other side, you know that it's a driver issue. Also "tcpdump" helps. For
ath10k, you may want to try 11s/mesh mode with TTL=1, while with ath10k-ct you
may prefer IBSS mode (I think that wasn't mentioned in your first mail).
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-13 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 5:56 Problems with Multiple Interfaces joe
2021-04-09 10:17 ` Simon Wunderlich
2021-04-09 11:16 ` Linus Lüssing
2021-04-10 0:39 ` joe
2021-04-13 11:53 ` Simon Wunderlich [this message]
2021-04-13 12:02 ` Sven Eckelmann
2021-04-13 14:37 ` Andi Depressivum
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=6830943.IaFvOplyQc@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=joe@careyhome.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