From: Simon Wunderlich <sw@simonwunderlich.de>
To: "mareklindner@neomailbox.ch" <mareklindner@neomailbox.ch>,
XU Yang <young.xu@connect.ust.hk>
Cc: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: Inquiry about Communication Issue between Nodes in "ONLY two nodes mesh network" with batman-adv
Date: Mon, 16 Oct 2023 16:24:38 +0200 [thread overview]
Message-ID: <2197854.1BCLMh4Saa@prime> (raw)
In-Reply-To: <OS0P286MB0116B77E8A851D552949A43CBCD7A@OS0P286MB0116.JPNP286.PROD.OUTLOOK.COM>
On Monday, October 16, 2023 4:12:41 PM CEST XU Yang wrote:
> Dear maintainer,
>
> I am a developer currently using the batman-adv library in research and have
> encountered some issues that I hope you might be able to assist with.
> In setting up a mesh network using batman-adv, I've noticed that when only
> two nodes are present in the network, they are unable to communicate with
> each other. However, once a third node is introduced, all nodes can
> communicate normally. Further testing has revealed that even with two
> nodes, despite good ad-hoc wifi connection quality, the nodes remain
> invisible to each other.
> Here are the system and configuration details:
>
> Hardware: Jetson Orin NX with rtl8822ce
> Operating System: L4T r35.3.1 Ubuntu20.04
> batman-adv version: 2023.2-9-g5fecd4a3
>
> The configuration code we use is in the attachment.
>
>
> I appreciate your time in reading this email and look forward to your
> response. I hope you might be able to help me understand the cause of this
> issue and suggest possible methods to resolve it.
Hi Young Xu,
this sounds like a underlying Wi-Fi driver issue. You may want to set up IP
addresses on the base Wi-Fi interfaces (e.g. wlan0) and try to ping between
the nodes directly, without batman-adv. You may also check further with "iw
wlan0 station dump" (or similar) who receives packets by whom, or check with
tcpdump if you see the OGM broadcasts.
I haven't seen many Realtek Wi-Fi devices to use batman-adv, and at least in
the past my experience with those devices not very positive, so also for that
reason I'd look into driver related issues first.
Cheers,
Simon
parent reply other threads:[~2023-10-16 14:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OS0P286MB0116B77E8A851D552949A43CBCD7A@OS0P286MB0116.JPNP286.PROD.OUTLOOK.COM>]
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=2197854.1BCLMh4Saa@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
--cc=young.xu@connect.ust.hk \
/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