All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Mark Birss <markbirss@gmail.com>
Subject: Re: BATMAN-adv Debug options
Date: Wed, 24 Jun 2020 23:32:16 +0200	[thread overview]
Message-ID: <1986026.lAXmxmQttu@sven-edge> (raw)
In-Reply-To: <CADg1mwL07UQqmUctQexAFCgFMrXBiF=rB1EdRqb3agveSEkckQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]

On Wednesday, 24 June 2020 23:13:50 CEST Mark Birss wrote:
> What other debug  information are available to troubleshoot connection issues?

The first question you have to answer: Is the lower layer working or did the 
lower layer break? Can be tested easily with multicast/broadcast and unicast 
pings on the lower device. Don't assume that the driver/firmware didn't break 
the connection because you see entries in the originator table. And also don't 
assume that the link is working just because you've only tested unicast 
packets on the lower device. WiFi drivers/firmware started to only partially 
(and "accidentally") kill links for only unicast OR for broadcast.

> I have enabled for OpenWRT
> echo "CONFIG_BATMAN_ADV_DEBUG=y" >> .config
> echo "CONFIG_BATMAN_ADV_DEBUGFS=y" >> .config
> echo "CONFIG_BATMAN_ADV_BLA=y" >> .config
> echo "CONFIG_BATMAN_ADV_DAT=y" >> .config
> echo "CONFIG_BATMAN_ADV_MCAST=y" >> .config
> echo "CONFIG_BATMAN_ADV_NC=n" >> .config
> echo "CONFIG_BATMAN_ADV_BATMAN_V=y" >> .config
> echo "CONFIG_BATMAN_ADV_SYSFS=y" >> .config
> echo "CONFIG_BATMAN_ADV_TRACING=y" >> .config
> 
> 
> echo 255 > /sys/class/net/bat0/mesh/log_level
> cat /sys/kernel/debug/batman_adv/bat0/log

Seems about right from the batman-adv perspective. Of course, also check the 
originator/neighbor and local/global translation tables. Use this information 
to check whether the packets are routed correctly through the lower 
interfaces. Just use tools like (batctl) tcpdump to capture this traffic. You 
can also use a recent wireshark to dissect pcaps from the lower interfaces.

You could also start to trace packets using trace-cmd and similar tools to 
figure out where your packets end up inside the kernel.

> since i want to understand also why on wifi mesh seems to crash for me ath10k

I've heard multiple persons complain in recent months about stability problems
of ath10k. So maybe it is the same problem here. But unfortunately, I don't 
have more information than various threads [1] on this mailing list.

Kind regards,
	Sven

[1] https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open-mesh.org/thread/PZK7RS5CACYDJIW4SH7R6UF7BIQI5OYR/#LZX2PNOX3FLG6L4D3WLRZYEULKD5IEF5

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-24 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 21:13 BATMAN-adv Debug options Mark Birss
2020-06-24 21:32 ` Sven Eckelmann [this message]
     [not found]   ` <CADg1mwLTTq-wjxvPvkTBb2J9qtSs_+BxhNsSW0DGTeo6QiWXbA@mail.gmail.com>
2020-06-25 11:44     ` Sven Eckelmann
2020-06-25 11:56       ` Mark Birss

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=1986026.lAXmxmQttu@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=markbirss@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.