lime-report from LibreMesh on OpenWrt 24.10

[ilario]

I got some lime-reports to compare between LibreMesh on OpenWrt 24.10 and on OpenWrt 23.05. In the first case, I used the latest LibreMesh code (and including also the code from #1139 and #1164)
While for the second I still have to manage to compile the images, will add the reports soonish.

The employed routers are the same employed in #1192: YouHua WR1200JS (DSA), TP-Link WDR3600 (swconfig), TP-Link WR841N v13 (single band, swconfig), PlasmaCloud PA1200 (DSA, without changing the default ath10k driver selection which is ath10k-ct).

Overall, the issues I observed are:

• Default anygw route working intermittently via cable #1192 so that the gateway via cable works intermittently.
• TP-Link WR841N v13 (64 MB RAM) has a high load average and does some boot looping. But I understand this is normal as 64 MB is too much for the default packages set and OpenWrt 24.10. Deselecting lime-app and pirania and avoiding wpad-mesh-* should help.
• libstdcpp dependency of shared-state-async takes 2 MB #1191 shared-state-async dependency libstdcpp is too large to be installed on TP-Link WDR3600
• Observations when testing on PlasmaCloud PA1200 #1151 but I did not check again everything

The cabled network topology is the following:

                      TP-Link WR841N v13
                                  |
laptop--YouHua WR1200JS--TP-Link WDR3600--PlasmaCloud PA1200--internet

As the routing protocols on the cable are active by default only on swconfig routers, via cable I would expect only the two TP-Link routers to see each other.

Here goes the output of lime-report on each router when using a firmware compiled on OpenWrt 24.10:

• TP-Link WR841N v13 TP-Link_WR841N_v13-LibreMesh_master-OpenWrt_24.10-report.txt
• YouHua WR1200JS YouHua_WR1200JS-LibreMesh_master-OpenWrt_24.10-report.txt
• TP-Link WDR3600 TP-Link_WDR3600-LibreMesh_master-OpenWrt_24.10-report.txt
• PlasmaCloud PA1200 PlasmaCloud_PA1200-LibreMesh_master-OpenWrt_24.10-report.txt

I tried to compile the same on OpenWrt 23.05 but got a ERROR: tools/squashfs3-lzma failed to build., so I will post here those lime-reports as soon as I manage to compile it on another laptop.

[ilario]

I forgot to specify: all the routers are in the same cardboard box, so that the wifi connection should be as good as it can be.

Still on OpenWrt 24.10:

• Default anygw route working intermittently via cable #1192 so that the gateway via cable works intermittently.

In this setup, the result of the ping to the gateway via cable is:

--- 10.13.0.1 ping statistics ---
2857 packets transmitted, 2036 received, +6 duplicates, 28.7364% packet loss, time 2924195ms
rtt min/avg/max/mdev = 0.363/0.616/1.840/0.122 ms

---

Pinging 10.13.0.1 when associated to the ap_named interface of each router gave less-than-perfect results, here you can see them.

Associated to the PlasmaCloud PA1200 named AP: close to no packet loss, average one hundred ms.

--- 10.13.0.1 ping statistics ---
341 packets transmitted, 340 received, 0.293255% packet loss, time 340710ms
rtt min/avg/max/mdev = 2.556/101.466/2186.274/269.527 ms, pipe 3
--- 4.2.2.2 ping statistics ---
344 packets transmitted, 341 received, 0.872093% packet loss, time 343917ms
rtt min/avg/max/mdev = 29.845/140.103/2263.815/278.503 ms, pipe 3

Associated to the TP-Link WDR3600 named AP: low packet loss, average 0.7-1 s.

--- 10.13.0.1 ping statistics ---
473 packets transmitted, 473 received, 0% packet loss, time 475456ms
rtt min/avg/max/mdev = 1.245/668.858/7608.648/1092.744 ms, pipe 8
--- 4.2.2.2 ping statistics ---
448 packets transmitted, 434 received, 3.125% packet loss, time 450836ms
rtt min/avg/max/mdev = 29.823/1169.695/11086.026/1838.395 ms, pipe 11

Associated to the TP-Link WR841N v13 named AP: I got disassociated, likely due to the low RAM of this device. Sometimes the AP was not even visible. High packet loss, high average ping time.

--- 10.13.0.1 ping statistics ---
335 packets transmitted, 181 received, +51 errors, 45.9701% packet loss, time 340685ms
rtt min/avg/max/mdev = 125.274/9409.036/32968.540/9788.108 ms, pipe 33
--- 4.2.2.2 ping statistics ---
338 packets transmitted, 169 received, +48 errors, 50% packet loss, time 343902ms
rtt min/avg/max/mdev = 348.591/9709.688/33857.928/9701.469 ms, pipe 34

Associated to the YouHua WR1200JS named AP: high packet loss, high ping time. At some point I had to reboot it in order to see its named AP...

--- 10.13.0.1 ping statistics ---
447 packets transmitted, 218 received, +29 errors, 51.2304% packet loss, time 454768ms
rtt min/avg/max/mdev = 91.357/4320.037/26839.877/5950.690 ms, pipe 27
--- 4.2.2.2 ping statistics ---
443 packets transmitted, 208 received, +27 errors, 53.0474% packet loss, time 451134ms
rtt min/avg/max/mdev = 225.719/4334.390/24983.997/5538.212 ms, pipe 25

[a-gave]

A quick report:
I'm testing the solution proposed by pony in #1121 (comment)
And it seems to work pretty well

create a new device bridge br0 with all dsa user ports
add the bridge br0 as member of br-lan and remove all dsa user ports from being direct members of br-lan
configure the 8021ad vlans for babel and batman on top of br0 (br0_17 and br0_29)

I'm continuing these tests while preparing a pull request modifying /usr/lib/lua/lime/network.lua with these changes

[ilario]

Here goes the output of lime-report on each router when using a firmware compiled on OpenWrt 23.05. The LibreMesh code is the same used for the reports from the first comment.

• TP-Link WR841N v13 TP-Link_WR841N_v13-LibreMesh_master-OpenWrt_23.05-report.txt
• YouHua WR1200JS YouHua_WR1200JS-LibreMesh_master-OpenWrt_23.05-report.txt
• TP-Link WDR3600 TP-Link_WDR3600-LibreMesh_master-OpenWrt_23.05-report.txt
• PlasmaCloud PA1200 PlasmaCloud_PA1200-LibreMesh_master-OpenWrt_23.05-report.txt

---

With the aforementioned setup, when connected via cable, these are the ping results:

--- 10.13.0.1 ping statistics ---
1506 packets transmitted, 871 received, +3 duplicates, 42.1647% packet loss, time 1540639ms
rtt min/avg/max/mdev = 0.361/0.557/4.326/0.175 ms
--- 4.2.2.2 ping statistics ---
1519 packets transmitted, 818 received, +3 duplicates, +82 errors, 46.1488% packet loss, time 1538979ms
rtt min/avg/max/mdev = 29.233/984.279/25267.050/1885.482 ms, pipe 25

So some of the issues reported above with OpenWrt 24.10, including #1192, maybe are not because of the new OpenWrt version, rather it seems to be a problem of my set of routers and cabled connections, or because of some code introduced after LibreMesh 2024.1 release (to be checked).

---

When connected to the named AP, here are the ping results.

PlasmaCloud PA1200 named AP:

--- 10.13.0.1 ping statistics ---
668 packets transmitted, 662 received, 0.898204% packet loss, time 668042ms
rtt min/avg/max/mdev = 2.968/29.097/760.171/53.421 ms
--- 4.2.2.2 ping statistics ---
667 packets transmitted, 661 received, 0.89955% packet loss, time 667036ms
rtt min/avg/max/mdev = 31.287/60.707/1006.807/61.928 ms

TP-Link WDR3600 named AP:

--- 10.13.0.1 ping statistics ---
958 packets transmitted, 946 received, 1.25261% packet loss, time 969574ms
rtt min/avg/max/mdev = 19.480/1812.889/9809.077/1358.636 ms, pipe 10
--- 4.2.2.2 ping statistics ---
955 packets transmitted, 820 received, +88 errors, 14.1361% packet loss, time 969648ms
rtt min/avg/max/mdev = 177.573/3866.448/28220.981/2944.959 ms, pipe 28

TP-Link WR841N v13 named AP. I had to reboot the router in order to see the AP... Clearly 64 MB of RAM are not enough neither with OpenWrt 23.05 :(

--- 10.13.0.1 ping statistics ---
770 packets transmitted, 362 received, +1 duplicates, 52.987% packet loss, time 787307ms
rtt min/avg/max/mdev = 0.358/0.636/28.374/1.466 ms
--- 4.2.2.2 ping statistics ---
782 packets transmitted, 344 received, +357 errors, 56.0102% packet loss, time 793888ms
rtt min/avg/max/mdev = 456.272/1774.110/7234.141/996.027 ms, pipe 8

YouHua WR1200JS named AP:

--- 10.13.0.1 ping statistics ---
2542 packets transmitted, 625 received, +173 errors, 75.4131% packet loss, time 2600059ms
rtt min/avg/max/mdev = 251.825/3996.870/32684.383/4795.232 ms, pipe 32
--- 4.2.2.2 ping statistics ---
2545 packets transmitted, 614 received, +257 errors, 75.8743% packet loss, time 2602981ms
rtt min/avg/max/mdev = 545.967/5386.336/40888.736/7081.234 ms, pipe 40

---

I'm testing the solution proposed by pony in #1121 (comment)
And it seems to work pretty well

Wow @a-gave and @pony1k, this sounds amazing, I love you both!
Looking forward to testing it!

So, if it is a DSA thing, it makes sense that it happens regardless of OpenWrt 23 or 24, right?
And we should expect it affects also LibreMesh 2024.1, right?
Do you think that this can originate also the issues with the WiFi I reported in this issue?