BATMAN-adv Debug options

BATMAN-adv Debug options

[Mark Birss]

Hi All

I just recently been using BATMAN-adv over ethernet

What other debug  information are available to troubleshoot connection issues?


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


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


Regards

Re: BATMAN-adv Debug options

[Sven Eckelmann]

[-- 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 --]

Re: BATMAN-adv Debug options

[Sven Eckelmann]

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

[please never contact me privately about batman-adv without a really good 
 reason. Cc at least the mailing list]

On Thursday, 25 June 2020 13:12:34 CEST Mark Birss wrote:
> "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."
> 
> How to do this ?

ping/ping6.

* unicast: just ping as normal the lower device (not bat0) IPv4 address or 
  (link local) IPv6 address
* multicast: just send from both sides an multicast ping. For example 
  ff02::1%wlan0 and check if the remote (not your own device) responds with a 
  unicast reply

> As for originator and neighbours this can also be checked by batctl or
> proc file system.

proc? If you have batman-adv entries in proc then you should definitely 
upgrade. This was removed in 2010.

Should this have been a question about where to find the originators and 
neighbors table? And you can see this via "batctl meshif bat0 originators" 
and "batctl meshif bat0 neighbors". The "meshif bat0" has to replaced with 
"-m bat0" on older batctl versions.

> Another question is there a breakdown of the meaning of the messages for
> 
> $ cat /sys/kernel/debug/batman_adv/bat0/log
> 
> The additional debug output is by default disabled. It can be enabled
> during run time. Following log_levels are defined:

No idea what you want here. The help text already says what each message type 
is about. If you don't know what a specific feature is then please check the 
wiki [1].

> and what is the Flags here
> 
> root@LiMe-a376eb:~# batctl tl
> [B.A.T.M.A.N. adv 2020.1-openwrt-2, MainIF/MAC:
> dummy0/aa:84:86:a3:76:eb (bat0/72:8b:cf:a4:00:77 BATMAN_IV), TTVN: 4]
> Client             VID Flags    Last seen (CRC       )
> 72:8b:cf:a4:00:77   -1 [.P....]   0.000   (0x1c349131)
> 50:3e:aa:06:6f:4d   -1 [......]   0.280   (0x1c349131)
> 72:8b:cf:a4:00:77    0 [.P....]   0.000   (0x9243e316)
> cc:2d:e0:47:b3:56   -1 [......]   0.980   (0x1c349131)
> 72:8b:cf:a4:00:77    1 [.P....]   0.000   (0xdb7f9e31)

The flags here are

* 'R' BATADV_TT_CLIENT_ROAM
* 'N' BATADV_TT_CLIENT_NEW
* 'X' BATADV_TT_CLIENT_PENDING
* 'W' BATADV_TT_CLIENT_WIFI
* 'I' BATADV_TT_CLIENT_ISOLA
* 'P' BATADV_TT_CLIENT_NOPURGE

And they are documented in the wiki [2]

Kind regards,
	Sven

[1] https://www.open-mesh.org/projects/batman-adv/wiki/Protocol_information
[2] https://www.open-mesh.org/projects/batman-adv/wiki/TT-Flags

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

Re: BATMAN-adv Debug options

[Mark Birss]

Sorry about the reply not including the mailing address, i  made error
clicking wrong reply icon

> As for originator and neighbours this can also be checked by batctl or1
> proc file system.

No i meant /sys/kernel/debug as I run recent Batman adv 2020-1

Thank you for pointing out the correct wiki links, I could not find them

I will create another topic for some other questions,

Thank you


On Thu, Jun 25, 2020 at 1:44 PM Sven Eckelmann <sven@narfation.org> wrote:
>
> [please never contact me privately about batman-adv without a really good
>  reason. Cc at least the mailing list]
>
> On Thursday, 25 June 2020 13:12:34 CEST Mark Birss wrote:
> > "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."
> >
> > How to do this ?
>
> ping/ping6.
>
> * unicast: just ping as normal the lower device (not bat0) IPv4 address or
>   (link local) IPv6 address
> * multicast: just send from both sides an multicast ping. For example
>   ff02::1%wlan0 and check if the remote (not your own device) responds with a
>   unicast reply
>
> > As for originator and neighbours this can also be checked by batctl or
> > proc file system.
>
> proc? If you have batman-adv entries in proc then you should definitely
> upgrade. This was removed in 2010.
>
> Should this have been a question about where to find the originators and
> neighbors table? And you can see this via "batctl meshif bat0 originators"
> and "batctl meshif bat0 neighbors". The "meshif bat0" has to replaced with
> "-m bat0" on older batctl versions.
>
> > Another question is there a breakdown of the meaning of the messages for
> >
> > $ cat /sys/kernel/debug/batman_adv/bat0/log
> >
> > The additional debug output is by default disabled. It can be enabled
> > during run time. Following log_levels are defined:
>
> No idea what you want here. The help text already says what each message type
> is about. If you don't know what a specific feature is then please check the
> wiki [1].
>
> > and what is the Flags here
> >
> > root@LiMe-a376eb:~# batctl tl
> > [B.A.T.M.A.N. adv 2020.1-openwrt-2, MainIF/MAC:
> > dummy0/aa:84:86:a3:76:eb (bat0/72:8b:cf:a4:00:77 BATMAN_IV), TTVN: 4]
> > Client             VID Flags    Last seen (CRC       )
> > 72:8b:cf:a4:00:77   -1 [.P....]   0.000   (0x1c349131)
> > 50:3e:aa:06:6f:4d   -1 [......]   0.280   (0x1c349131)
> > 72:8b:cf:a4:00:77    0 [.P....]   0.000   (0x9243e316)
> > cc:2d:e0:47:b3:56   -1 [......]   0.980   (0x1c349131)
> > 72:8b:cf:a4:00:77    1 [.P....]   0.000   (0xdb7f9e31)
>
> The flags here are
>
> * 'R' BATADV_TT_CLIENT_ROAM
> * 'N' BATADV_TT_CLIENT_NEW
> * 'X' BATADV_TT_CLIENT_PENDING
> * 'W' BATADV_TT_CLIENT_WIFI
> * 'I' BATADV_TT_CLIENT_ISOLA
> * 'P' BATADV_TT_CLIENT_NOPURGE
>
> And they are documented in the wiki [2]
>
> Kind regards,
>         Sven
>
> [1] https://www.open-mesh.org/projects/batman-adv/wiki/Protocol_information
> [2] https://www.open-mesh.org/projects/batman-adv/wiki/TT-Flags