Cannot connect to Batman Mesh

mcarni · October 26, 2019, 6:15pm

i did some more testing and now i am more confused..

removed the CT drivers and replaced with the non-ct on both routers

archer c7:

kmod-ath10k - 4.19.79+5.4-rc2-1-1
ath10k-firmware-qca988x - 20190815-1

1043:

kmod-ath10k - 4.19.79+5.4-rc2-1-1

with no encryption all works fine:

1043 gets connected to the mesh and to the internet:

root@OpenWrt2:~# logread | fgrep mesh
Fri Oct 25 10:05:25 2019 user.notice mac80211: Failed command: iw dev mesh0 set channel 6 HT40
Fri Oct 25 10:05:29 2019 kern.info kernel: [   34.850851] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Fri Oct 25 10:05:29 2019 kern.info kernel: [   35.090092] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Fri Oct 25 10:05:29 2019 daemon.notice netifd: Network device 'mesh0' link is up
Fri Oct 25 10:05:29 2019 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Fri Oct 25 10:05:29 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Fri Oct 25 10:05:29 2019 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Fri Oct 25 10:05:30 2019 kern.info kernel: [   35.359038] batman_adv: bat0: Adding interface: mesh0
Fri Oct 25 10:05:30 2019 kern.info kernel: [   35.364154] batman_adv: bat0: Interface activated: mesh0
Fri Oct 25 10:05:30 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now up

root@OpenWrt2:~# batctl o
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/54:e6:fc:9a:36:8e (bat0/d2:11:b8:85:f4:3c BATMAN_IV)]
   Originator        last-seen (#/255) Nexthop           [outgoingIF]
 * 60:e3:27:78:85:37    0.460s   (241) 60:e3:27:78:85:37 [     mesh0]

root@OpenWrt2:~# batctl n
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/54:e6:fc:9a:36:8e (bat0/d2:11:b8:85:f4:3c BATMAN_IV)]
IF             Neighbor              last-seen
        mesh0	  60:e3:27:78:85:37    0.240s

root@OpenWrt2:~# ping -c 3 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: seq=0 ttl=64 time=4.016 ms
64 bytes from 192.168.2.1: seq=1 ttl=64 time=2.295 ms
64 bytes from 192.168.2.1: seq=2 ttl=64 time=3.537 ms

--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.295/3.282/4.016 ms

root@OpenWrt2:~# batctl ping -c 3 192.168.2.1
PING 192.168.2.1 (60:e3:27:78:85:37) 20(48) bytes of data
20 bytes from 192.168.2.1 icmp_seq=1 ttl=50 time=1.22 ms
20 bytes from 192.168.2.1 icmp_seq=2 ttl=50 time=0.84 ms
20 bytes from 192.168.2.1 icmp_seq=3 ttl=50 time=1.23 ms
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss
rtt min/avg/max/mdev = 0.842/1.097/1.231/0.181 ms

192.168.2.177 is a computer which is off the mesh...

root@OpenWrt2:~# ping -c 3 192.168.2.177
PING 192.168.2.177 (192.168.2.177): 56 data bytes
64 bytes from 192.168.2.177: seq=0 ttl=64 time=187.019 ms
64 bytes from 192.168.2.177: seq=1 ttl=64 time=202.615 ms
64 bytes from 192.168.2.177: seq=2 ttl=64 time=29.680 ms

--- 192.168.2.177 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 29.680/139.771/202.615 ms

root@OpenWrt2:~# batctl ping -c 3 192.168.2.177
PING 192.168.2.177 (60:e3:27:78:85:37) 20(48) bytes of data
20 bytes from 192.168.2.177 icmp_seq=1 ttl=50 time=105.71 ms
20 bytes from 192.168.2.177 icmp_seq=2 ttl=50 time=1.13 ms
20 bytes from 192.168.2.177 icmp_seq=3 ttl=50 time=0.85 ms
--- 192.168.2.177 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss
rtt min/avg/max/mdev = 0.853/35.898/105.706/49.362 ms

root@OpenWrt2:~# ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=52 time=14.725 ms
64 bytes from 8.8.8.8: seq=1 ttl=52 time=9.042 ms
64 bytes from 8.8.8.8: seq=2 ttl=52 time=9.909 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 9.042/11.225/14.725 ms

as soon as i switch to psk encryptio the connection between the two nodes fails

config wifi-iface 'mesh0'
        option device 'radio0'
        option ifname 'mesh0'
        option network 'nwi_mesh0'
        option mode 'mesh'
        option mesh_fwding '0'
        option mesh_id 'XXX'
        option encryption 'none'
#        option encryption 'psk2+ccmp'
#       option key 'XXX'

on the 1043

root@OpenWrt2:~# logread | fgrep mesh
Sat Oct 26 17:46:48 2019 user.notice mac80211: Failed command: iw dev mesh0 set channel 6 HT40
Sat Oct 26 17:46:52 2019 kern.info kernel: [   35.636596] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Sat Oct 26 17:46:53 2019 user.notice mac80211: Failed command: iw dev mesh0 set mesh_param mesh_fwding 0
Sat Oct 26 17:46:53 2019 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Sat Oct 26 17:46:54 2019 daemon.err wpa_supplicant[1411]: Using interface mesh0 with hwaddr 54:e6:fc:9a:36:8e and ssid ""
Sat Oct 26 17:46:54 2019 daemon.notice wpa_supplicant[1411]: mesh0: interface state UNINITIALIZED->ENABLED
Sat Oct 26 17:46:54 2019 daemon.notice wpa_supplicant[1411]: mesh0: AP-ENABLED
Sat Oct 26 17:46:54 2019 daemon.notice wpa_supplicant[1411]: mesh0: joining mesh XXX
Sat Oct 26 17:46:54 2019 daemon.notice netifd: Network device 'mesh0' link is up
Sat Oct 26 17:46:54 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Sat Oct 26 17:46:54 2019 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Sat Oct 26 17:46:54 2019 kern.info kernel: [   38.304827] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Sat Oct 26 17:46:54 2019 daemon.notice wpa_supplicant[1411]: mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sat Oct 26 17:46:54 2019 daemon.notice wpa_supplicant[1411]: mesh0: MESH-GROUP-STARTED ssid="XXX" id=0
Sat Oct 26 17:46:55 2019 kern.info kernel: [   38.396218] batman_adv: bat0: Adding interface: mesh0
Sat Oct 26 17:46:55 2019 kern.info kernel: [   38.401469] batman_adv: bat0: Interface activated: mesh0
Sat Oct 26 17:46:55 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now up
Sat Oct 26 17:51:03 2019 daemon.notice wpa_supplicant[1411]: mesh0: new peer notification for 60:e3:27:78:85:37
Sat Oct 26 17:51:04 2019 daemon.notice wpa_supplicant[1411]: mesh0: mesh plink with 60:e3:27:78:85:37 established
Sat Oct 26 17:51:04 2019 daemon.notice wpa_supplicant[1411]: mesh0: MESH-PEER-CONNECTED 60:e3:27:78:85:37

root@OpenWrt2:~# batctl o
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/54:e6:fc:9a:36:8e (bat0/6e:fd:4d:ee:e9:b1 BATMAN_IV)]
   Originator        last-seen (#/255) Nexthop           [outgoingIF]
 * 60:e3:27:78:85:37    1.020s   (242) 60:e3:27:78:85:37 [     mesh0]

root@OpenWrt2:~# batctl n
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/54:e6:fc:9a:36:8e (bat0/6e:fd:4d:ee:e9:b1 BATMAN_IV)]
IF             Neighbor              last-seen
        mesh0	  60:e3:27:78:85:37    0.940s

root@OpenWrt2:~# ping -c 3 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes

--- 192.168.2.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

root@OpenWrt2:~# batctl ping -c 3 192.168.2.1
PING 192.168.2.1 (60:e3:27:78:85:37) 20(48) bytes of data
Reply from host 192.168.2.1 timed out
Reply from host 192.168.2.1 timed out
Reply from host 192.168.2.1 timed out
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss
rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms

and now the archer c7

root@OpenWrt:~# logread | fgrep mesh
Sat Oct 26 17:34:43 2019 user.notice mac80211: Failed command: iw dev mesh0 set channel 6 HT40
Sat Oct 26 17:39:04 2019 kern.info kernel: [   50.066844] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Sat Oct 26 17:39:04 2019 kern.info kernel: [   50.378949] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Sat Oct 26 17:39:04 2019 daemon.notice netifd: Network device 'mesh0' link is up
Sat Oct 26 17:39:04 2019 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Sat Oct 26 17:39:04 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Sat Oct 26 17:39:04 2019 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Sat Oct 26 17:39:05 2019 kern.info kernel: [   50.743871] batman_adv: bat0: Adding interface: mesh0
Sat Oct 26 17:39:05 2019 kern.info kernel: [   50.749015] batman_adv: bat0: Interface activated: mesh0
Sat Oct 26 17:39:05 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now up
Sat Oct 26 17:51:42 2019 daemon.notice netifd: Interface 'nwi_mesh0' is disabled
Sat Oct 26 17:51:42 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity loss
Sat Oct 26 17:51:42 2019 kern.info kernel: [  808.190814] batman_adv: bat0: Interface deactivated: mesh0
Sat Oct 26 17:51:42 2019 kern.info kernel: [  808.196504] batman_adv: bat0: Removing interface: mesh0
Sat Oct 26 17:51:42 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now down
Sat Oct 26 17:51:43 2019 user.notice mac80211: Failed command: iw dev mesh0 set channel 6 HT40
Sat Oct 26 17:51:45 2019 kern.info kernel: [  810.971082] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Sat Oct 26 17:51:46 2019 user.notice mac80211: Failed command: iw dev mesh0 set mesh_param mesh_fwding 0
Sat Oct 26 17:51:47 2019 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Sat Oct 26 17:51:47 2019 daemon.err wpa_supplicant[2982]: Using interface mesh0 with hwaddr 60:e3:27:78:85:37 and ssid ""
Sat Oct 26 17:51:47 2019 daemon.notice wpa_supplicant[2982]: mesh0: interface state UNINITIALIZED->ENABLED
Sat Oct 26 17:51:47 2019 daemon.notice wpa_supplicant[2982]: mesh0: AP-ENABLED
Sat Oct 26 17:51:47 2019 daemon.notice wpa_supplicant[2982]: mesh0: joining mesh XXX
Sat Oct 26 17:51:47 2019 daemon.notice netifd: Network device 'mesh0' link is up
Sat Oct 26 17:51:47 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Sat Oct 26 17:51:47 2019 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Sat Oct 26 17:51:48 2019 kern.info kernel: [  813.754229] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Sat Oct 26 17:51:48 2019 daemon.notice wpa_supplicant[2982]: mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sat Oct 26 17:51:48 2019 daemon.notice wpa_supplicant[2982]: mesh0: MESH-GROUP-STARTED ssid="XXX" id=0
Sat Oct 26 17:51:48 2019 kern.info kernel: [  813.959072] batman_adv: bat0: Adding interface: mesh0
Sat Oct 26 17:51:48 2019 kern.info kernel: [  813.964317] batman_adv: bat0: Interface activated: mesh0
Sat Oct 26 17:51:48 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now up
Sat Oct 26 17:51:48 2019 daemon.notice wpa_supplicant[2982]: mesh0: new peer notification for 54:e6:fc:9a:36:8e
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: new peer notification for 54:e6:fc:9a:36:8e
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: new peer notification for 54:e6:fc:9a:36:8e
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: new peer notification for 54:e6:fc:9a:36:8e
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: new peer notification for 54:e6:fc:9a:36:8e
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: mesh plink with 54:e6:fc:9a:36:8e established
Sat Oct 26 17:51:49 2019 daemon.notice wpa_supplicant[2982]: mesh0: MESH-PEER-CONNECTED 54:e6:fc:9a:36:8e

root@OpenWrt:~# batctl o
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/60:e3:27:78:85:37 (bat0/e6:41:e8:76:6e:b7 BATMAN_IV)]
   Originator        last-seen (#/255) Nexthop           [outgoingIF]
 * 54:e6:fc:9a:36:8e    0.520s   (255) 54:e6:fc:9a:36:8e [     mesh0]

root@OpenWrt:~# batctl n
[B.A.T.M.A.N. adv openwrt-2019.3-0, MainIF/MAC: mesh0/60:e3:27:78:85:37 (bat0/e6:41:e8:76:6e:b7 BATMAN_IV)]
IF             Neighbor              last-seen
        mesh0	  54:e6:fc:9a:36:8e    0.900s

root@OpenWrt:~# ping -c 3 192.168.2.2
PING 192.168.2.2 (192.168.2.2): 56 data bytes

--- 192.168.2.2 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

root@OpenWrt:~# batctl ping -c 3 192.168.2.2
Error - mac address of the ping destination could not be resolved and is not a bat-host name: 192.168.2.2

root@OpenWrt:~# batctl ping -c 3 54:e6:fc:9a:36:8e
PING 54:e6:fc:9a:36:8e (54:e6:fc:9a:36:8e) 20(48) bytes of data
Reply from host 54:e6:fc:9a:36:8e timed out
Reply from host 54:e6:fc:9a:36:8e timed out
Reply from host 54:e6:fc:9a:36:8e timed out
--- 54:e6:fc:9a:36:8e ping statistics ---
3 packets transmitted, 0 received, 100% packet loss
rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms

in this case it seems to me that the main difference is that the node 1 cannot ping node 1, which is something that strangely it could do before...

if anyone has anything that wants me to test, i would be happy to try..

thanks
M

gallo · October 26, 2019, 6:48pm

It appears your not part of the justice league

jeff · October 26, 2019, 7:44pm

iw dev mesh0 station dump

and examination of the logs on both machines is probably all you need if the problem is at the 802.11s level. Use those as diagnostics for the mesh itself. If the mesh is not connecting (which is my guess), nothing is going to route over it.

See Cannot connect to Batman Mesh - #15 by jeff (post #15 above) for what the station dump looks like for connected peers on my device. Comparing your own unencrypted vs. encrypted logs and station dump should help.

If the mesh is connected, then it is likely one or more of:

Config version and batman version don't match on one or both routers
Config of batman on router A incompatible with router B

You can also add an explicit IP address to the mesh interfaces. the 172.16.X.Y private address space is a convenient one as it "looks different" than the typical 192.168.X.Y or 10.x.y.z addresses.

mcarni · October 26, 2019, 8:33pm

thanks for the feedback

these are the results from "iw dev mesh0 station dump" on the two routers

no encryption - archer c7 router:

Station 54:e6:fc:9a:36:8e (on mesh0)
	inactive time:	140 ms
	rx bytes:	95459
	rx packets:	1292
	tx bytes:	1229
	tx packets:	11
	tx retries:	4
	tx failed:	0
	rx drop misc:	0
	signal:  	-57 [-59, -69, -61] dBm
	signal avg:	-57 [-59, -71, -61] dBm
	Toffset:	18446744068901901026 us
	tx bitrate:	120.0 MBit/s MCS 5 40MHz short GI
	tx duration:	5379 us
	rx bitrate:	81.0 MBit/s MCS 10 40MHz
	rx duration:	144076 us
	airtime weight: 256
	expected throughput:	40.191Mbps
	mesh llid:	25661
	mesh plid:	54578
	mesh plink:	ESTAB
	mesh local PS mode:	ACTIVE
	mesh peer PS mode:	ACTIVE
	mesh non-peer PS mode:	ACTIVE
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	short slot time:yes
	connected time:	84 seconds

no encryption - archer 1043 router:

root@OpenWrt2:~# iw dev mesh0 station dump
Station 60:e3:27:78:85:37 (on mesh0)
	inactive time:	80 ms
	rx bytes:	37018
	rx packets:	501
	tx bytes:	1205
	tx packets:	11
	tx retries:	3
	tx failed:	0
	rx drop misc:	0
	signal:  	-64 [-65, -71, -79] dBm
	signal avg:	-63 [-64, -72, -79] dBm
	Toffset:	4807612191 us
	tx bitrate:	81.0 MBit/s MCS 10 40MHz
	tx duration:	6511 us
	rx bitrate:	120.0 MBit/s MCS 5 40MHz short GI
	rx duration:	52700 us
	airtime weight: 256
	expected throughput:	35.705Mbps
	mesh llid:	54578
	mesh plid:	25661
	mesh plink:	ESTAB
	mesh local PS mode:	ACTIVE
	mesh peer PS mode:	ACTIVE
	mesh non-peer PS mode:	ACTIVE
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	short slot time:yes
	connected time:	22 seconds

now both with encryption
archer c7:

root@OpenWrt:~# iw dev mesh0 station dump
Station 54:e6:fc:9a:36:8e (on mesh0)
	inactive time:	20 ms
	rx bytes:	13226567
	rx packets:	157119
	tx bytes:	136553
	tx packets:	2175
	tx retries:	119
	tx failed:	0
	rx drop misc:	0
	signal:  	-57 [-58, -64, -69] dBm
	signal avg:	-57 [-58, -65, -69] dBm
	Toffset:	18446744073196868478 us
	tx bitrate:	52.0 MBit/s MCS 11
	tx duration:	1751594 us
	rx bitrate:	52.0 MBit/s MCS 11
	rx duration:	18409724 us
	airtime weight: 256
	expected throughput:	26.733Mbps
	mesh llid:	0
	mesh plid:	0
	mesh plink:	ESTAB
	mesh local PS mode:	ACTIVE
	mesh peer PS mode:	ACTIVE
	mesh non-peer PS mode:	ACTIVE
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		yes
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	connected time:	7648 seconds

1043_

root@OpenWrt2:~# iw dev mesh0 station dump
Station 60:e3:27:78:85:37 (on mesh0)
	inactive time:	0 ms
	rx bytes:	14206319
	rx packets:	164645
	tx bytes:	4961
	tx packets:	52
	tx retries:	3
	tx failed:	0
	rx drop misc:	2088
	signal:  	-68 [-69, -78, -78] dBm
	signal avg:	-67 [-68, -76, -78] dBm
	Toffset:	512644732 us
	tx bitrate:	52.0 MBit/s MCS 11
	tx duration:	28622 us
	rx bitrate:	52.0 MBit/s MCS 11
	rx duration:	19352028 us
	airtime weight: 256
	expected throughput:	26.733Mbps
	mesh llid:	0
	mesh plid:	0
	mesh plink:	ESTAB
	mesh local PS mode:	ACTIVE
	mesh peer PS mode:	ACTIVE
	mesh non-peer PS mode:	ACTIVE
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		yes
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	connected time:	7687 seconds

i am not really sure of where to look, so i put all of them on a table and it seems to me:

all of them have ESTAB, active, authorized and associated
the encrypted ones have mesh llid and plid 0 for both routers while the unencrypted have 25661 and 54578 alternatively
MFP is yes for encrypted option and no for unencrypted

hope this helps

both routers have "kmod-batman-adv - 4.19.79+2019.3-0"

config should be pretty identical, but i am quite good at leaving typos here and there, so i will double check

thanks

jeff · October 26, 2019, 9:28pm

Yes, both unencrypted and encrypted look to be communication point-to-point to me as well. I don't know what all the lines mean, but nothing stands out as strange in and of itself.

Curious, though, is that the unencrypted case is showing high-rate, 802.11n modulation, but the encrypted case is showing "52.0 MBit/s MCS 11" -- which is a two-stream, moderate-rate modulation. (See, for example, https://www.wlanpros.com/mcs-index-charts/)

Hmmm...

What happens if you connect the Archer C7 to the 1043 as a "normal" AP/STA link (just to see what rates you get, not to try to get batman to work)??

markbirss · October 26, 2019, 9:53pm

Hi

I notice with my own mix mesh firmware B.A.T.M.A.N. adv openwrt-2019.4-0 not encrypted
the expected throughput values dont actually match the tested mesh performance values

for example

iw dev mesh0 station dump
-> expected throughput: 26.733Mbps

vs

batctl tp aa:0b:86:cf:7f:a9

so i think it better to run "batctl tp mesh-node" a couple of times to check performance numbers

I have also tried mesh bonding but this does not seem to work for me.

jeff · October 26, 2019, 9:54pm

Nothing to do with throughput (other than not having any) at this point. More the “curious” difference in modulation.

markbirss · October 26, 2019, 10:00pm

Ok, well my modulation changes but my tested performance still upto 104Mbps

mcarni · October 26, 2019, 10:07pm

super silly question

you are asking me to connect the router 2 (tp link 1043) to the router 1 (the archer c7), which i guess will need some kind of modification to the /etc/confi/wireless of the router 2

... once i get the two connected, how do i measure the rates?

markbirss · October 26, 2019, 10:08pm

use iperf from client to server

jeff · October 26, 2019, 10:10pm

Don’t need to measure the rates. Just see if the modulation behaves similarly between unencrypted and encrypted

mcarni · October 26, 2019, 10:48pm

sorry, i am struggling to get to connect in AP/STA mode the two routers...
at the moment i created a new interface, called wwan in /etc/config/network and cloned the AP in wireless and replaces lan with wwan and ap with sta
i am trying to follow this
https://openwrt.org/docs/guide-user/network/wifi/ap_sta
but probalby it is too late here for my brain to get this done...router 2 is not connecting to router 1...
is there any chance you could give me some hints on how to do this?

if it can help, while the mesh was still up i got some "batctl tp"

router 1 - unencrypted

root@OpenWrt:~# batctl tp 54:e6:fc:9a:36:8e
Test duration 10430ms.
Sent 50120532 Bytes.
Throughput: 4.58 MB/s (38.44 Mbps)

router 1 - encrypted

root@OpenWrt:~# batctl tp 54:e6:fc:9a:36:8e
Test duration 10240ms.
Sent 141696 Bytes.
Throughput: 13.51 KB/s (110.70 Kbps)

router 2 - unencrypted

root@OpenWrt2:~# batctl tp 60:e3:27:78:85:37
Test duration 10210ms.
Sent 47733840 Bytes.
Throughput: 4.46 MB/s (37.40 Mbps)

router 2 - encrypted

root@OpenWrt2:~# batctl tp 60:e3:27:78:85:37
Test duration 10160ms.
Sent 0 Bytes.
Throughput: 0 Bytes/s (0 Bps)

markbirss · October 27, 2019, 12:48am

It should be clear now, that encrypted throughput is unusable, and it as I pointed out earlier

mcarni · October 29, 2019, 6:08am

sorry guys, i will be away from home for the next three weeks, so i might be not be able to test a lot...
before leaving i updated both routers to the latest snapshot and the situation is still the same
on my return i will be trying to setup the the router in AP/STA mode to see the effects of encryptions

might be completely unrelated, but for the tp link 1043 i went for the ath79 firmware, maybe it would have been a wiser choice if i used the ar71... i will try and let you know

thanks
M

jeff · October 29, 2019, 6:13am

ar71xx is deprecated

mcarni · January 15, 2020, 11:44am

hope it is not too late...my second archer c7 arrived only few days ago...

i just wanted to thank thank you all and confirm that what in the wiki works perfectly and i have an encrypted batman mesh between the two archers
i am guessing the issue was with the old hardware of the 1043nd

only little deviation from the wiki is that i did not have to replace ct firmware with non-ct, everything worked out of the box

thanks
M

dlakelan · January 15, 2020, 1:33pm

thanks for coming back and giving the update. perhaps mark your last post as the solution using the checkbox too. someone trying to set up a mesh will benefit I'm sure

mcarni · January 15, 2020, 1:41pm

thanks to you all,
post marked as solution
i wanted also to mark the thread as [solved] but maybe i am too late...can't find the option to edit the title

M

slh · January 15, 2020, 8:35pm

The draft-n AR9103 wireless chipset inside the tl-wr1043nd v1 is plagued with quite a few silicon bugs and stability issues, it's not surprising that it doesn't behave as it's supposed to - especially in more exotic operation modes.

system · January 25, 2020, 8:35pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.