From: Sven Eckelmann <sven@narfation.org>
To: Rob Cowart <rob.cowart@xecoenergy.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: batadv gw_mode client 0?
Date: Wed, 24 Jun 2020 22:13:47 +0200 [thread overview]
Message-ID: <2094569.NUmnuQNPM9@sven-edge> (raw)
In-Reply-To: <E3FD8A72-966A-4CBB-A036-8C0A4152983D@xecoenergy.com>
[-- Attachment #1: Type: text/plain, Size: 5795 bytes --]
On Wednesday, 24 June 2020 22:02:38 CEST Rob Cowart wrote:
[....]
> Is anything wrong with these?
Most likely not, but someone on the mailing list with deeper knowledge on
B.A.T.M.A.N. V's echo location protocol could actually check whether non-
symmetric settings on different nodes could create problems or not. Or if
having both ELP and OGM2 interval set to the same value could have negative
side effects.
> Our gateway:
>
> pi@raspberrypi:~/xeco-master/enola-daemon $ cat /sys/class/net/wlan0/batman_adv/elp_interval
> 500
> pi@raspberrypi:~/xeco-master/enola-daemon $ cat /sys/class/net/bat0/mesh/orig_interval
> 1000
>
> nodes:
> pi@raspberrypi:~ $ cat /sys/class/net/wlan0/batman_adv/elp_interval
> 30000
> pi@raspberrypi:~ $ cat /sys/class/net/bat0/mesh/orig_interval
> 30000
[...]
On Wednesday, 24 June 2020 21:23:09 CEST Rob Cowart wrote:
> IF Neighbor last-seen
> b8:27:eb:4e:73:6d 25.330s ( 1.0) [ wlan0]
> b8:27:eb:ff:0e:b6 23.320s ( 1.0) [ wlan0]
> b8:27:eb:08:13:37 18.850s ( 1.0) [ wlan0]
> b8:27:eb:aa:1e:6d 37.010s ( 1.0) [ wlan0]
> b8:27:eb:35:c6:77 63.590s ( 1.0) [ wlan0]
> b8:27:eb:e9:34:41 18.280s ( 1.0) [ wlan0]
> b8:27:eb:84:ca:90 30.560s ( 1.0) [ wlan0]
> b8:27:eb:1e:eb:cd 27.410s ( 1.0) [ wlan0]
> b8:27:eb:cb:80:34 23.100s ( 1.0) [ wlan0]
Btw. it looks to me like B.A.T.M.A.N. V is a really bad choice for your setup.
All links have the throughput value 1.0 Mbit/s. This sounds to me like the
wifi driver doesn't provide the required expected_throughput. And so you have
a REALLY, REALLY, REALLY bad metric when you are using 1.0 everywhere. So if
you want to continue experimenting with B.A.T.M.A.N. V then you should try to
get this fixed in your wifi driver or just switch to B.A.T.M.A.N. IV with
increased multicast rate.
> Lots of stuff I don't understand here, looks like loopback is very busy?
Not sure what you mean here with loopback. I will just leave the whole output
here in case somebody else on the mailing list wants to figure it out.
> pi@raspberrypi:~/xeco-master/enola-daemon $ sudo batctl td wlan0
> 15:01:52.075412 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 704843962, v 15, interval 500ms, length 20
> 15:01:52.076036 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.076507 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.076854 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.077456 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.077937 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.078028 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.078657 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.079155 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.079246 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.079894 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.080480 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.080965 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.081435 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.081904 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.081995 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.082435 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.082539 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.082957 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
> 15:01:52.415359 BAT b8:27:eb:fb:4e:58: OGM2 via neigh b8:27:eb:fb:4e:58, seq 500807384, throughput MAX, ttl 50, v 15, length 60, tvlv_len 40
> TVLV TTv1: OGM DIFF [.] ttvn=1 vlan_num=1 entry_num=0
> VLAN ID -1, crc 0xf0cfd284
> TVLV GWv1: down 10.0Mbps, up 2.0Mbps
> TVLV DATv1: enabled
> 15:01:52.423153 BAT b8:27:eb:fb:4e:58: OGM2 via neigh b8:27:eb:aa:1e:6d, seq 500807384, throughput 15.0Mbps, ttl 49, v 15, length 60, tvlv_len 40
> TVLV TTv1: OGM DIFF [.] ttvn=1 vlan_num=1 entry_num=0
> VLAN ID -1, crc 0xf0cfd284
> TVLV GWv1: down 10.0Mbps, up 2.0Mbps
> TVLV DATv1: enabled
> 15:01:52.424280 BAT b8:27:eb:fb:4e:58: OGM2 via neigh b8:27:eb:cb:80:34, seq 500807384, throughput 14.9Mbps, ttl 49, v 15, length 60, tvlv_len 40
> TVLV TTv1: OGM DIFF [.] ttvn=1 vlan_num=1 entry_num=0
> VLAN ID -1, crc 0xf0cfd284
> TVLV GWv1: down 10.0Mbps, up 2.0Mbps
> TVLV DATv1: enabled
> 15:01:52.428556 BAT b8:27:eb:fb:4e:58: OGM2 via neigh b8:27:eb:84:ca:90, seq 500807384, throughput 15.0Mbps, ttl 49, v 15, length 60, tvlv_len 40
> TVLV TTv1: OGM DIFF [.] ttvn=1 vlan_num=1 entry_num=0
> VLAN ID -1, crc 0xf0cfd284
> TVLV GWv1: down 10.0Mbps, up 2.0Mbps
> TVLV DATv1: enabled
> 15:01:52.575301 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 704843963, v 15, interval 500ms, length 20
> 15:01:52.575486 BAT b8:27:eb:fb:4e:58: ELP via iface b8:27:eb:fb:4e:58, seq 0, v 15, interval 0ms, length 200
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-24 20:13 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
[not found] ` <E3FD8A72-966A-4CBB-A036-8C0A4152983D@xecoenergy.com>
2020-06-24 20:13 ` Sven Eckelmann [this message]
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=2094569.NUmnuQNPM9@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 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.