public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Rob Cowart <rob.cowart@xecoenergy.com>
Subject: Re: batadv gw_mode client 0?
Date: Wed, 24 Jun 2020 21:54:53 +0200	[thread overview]
Message-ID: <8393812.UZvHzlbVaM@sven-edge> (raw)
In-Reply-To: <9543BE37-DB78-4DC6-A674-F6460D5665BF@xecoenergy.com>

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

On Wednesday, 24 June 2020 21:43:18 CEST Rob Cowart wrote:
> >    ssh fe80::6c39:baff:fe1c:6d11%wlan0
> Yes we knew this, this is Standard Operating Procedure, but atm nothing responds on ping.

When nothing reacts to pings on wlan0 then your lower link is most likely 
broken. batman-adv can also not help here when the link on which it operates 
is "dead".

> > Not sure what the ELP interval is here but the last seen is extremely high. I 
> > would guess that the lower link actually broke down and the neighbor entries
> > just  didn't time out yet.
> How do I tell you what the ELP is?

Echo Location Protocol [1]. It is similar to the OGM messages in 
B.A.T.M.A.N. IV - but only used between single hop neighbors (and sometimes 
also as unicast instead of broadcast)

> we (my boss who tries to be a software engineer) have definitely messed a lot with the batctl settings.

The elp interval can be checked on recent batctl versions using:

    batctl hardif wlan0 elp_interval

Or on systems which are using sysfs for configuration:

    cat /sys/class/net/wlan/batman_adv/elp_interval


The OGM(2) interval can be checked using

    batctl meshif bat0 orig_interval

Or on systems which are using sysfs for configuration:


    cat /sys/class/net/bat0/mesh/orig_interval


Both values are in milliseconds


> pi@raspberrypi:~/xeco-master/enola-daemon $ sudo batctl s 

The ELP packets (and much more) are part of mgmt_tx/mgmt_tx_bytes/mgmt_rx/
mgmt_rx_bytes.


> pi@raspberrypi:~/xeco-master/enola-daemon $ sudo batctl td bat0
> 14:42:51.260179 IP6 fe80::4829:b9ff:fea5:8a76.16962 > fe80::d486:8dff:fe7d:394d.16962: UDP, length 218

ELP messages are not sent on top of bat0 but on the lower interface (wlan0 in 
your case). So you have would have to run "batctl td wlan0". Or create a pcap 
on wlan with tcpdump and open it in a recent version of wireshark.

Kind regards,
	Sven

[1] https://www.open-mesh.org/projects/batman-adv/wiki/ELP

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

  parent reply	other threads:[~2020-06-24 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:45 batadv gw_mode client 0? Rob Cowart
2020-06-16  7:01 ` Sven Eckelmann
     [not found]   ` <3DDDEFCA-57DC-43E1-8534-F816F872CD2B@xecoenergy.com>
2020-06-24 19:36     ` Sven Eckelmann
     [not found]       ` <9543BE37-DB78-4DC6-A674-F6460D5665BF@xecoenergy.com>
2020-06-24 19:54         ` Sven Eckelmann [this message]
     [not found]           ` <E3FD8A72-966A-4CBB-A036-8C0A4152983D@xecoenergy.com>
2020-06-24 20:13             ` Sven Eckelmann
2020-06-24 20:37               ` Rob Cowart
2020-06-24 21:01                 ` Mark Birss
2020-06-24 21:07                   ` Sven Eckelmann
2020-06-24 21:12                 ` Sven Eckelmann
     [not found]                   ` <1C0C87FF-C97B-4118-BCC6-DF1163BAB05F@xecoenergy.com>
2020-07-28  5:06                     ` Sven Eckelmann

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=8393812.UZvHzlbVaM@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=rob.cowart@xecoenergy.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