On Tuesday, 19 November 2024 15:59:58 CET Mu De wrote:
"batctl o" shows empty table
Which means that the underlying link is not working. Either because the interface is down, not connected or is manipulating the transmitted OGMs (broadcast) in some form. The latter can for example happen if the underlying link is converting broadcasts to unicast - some accesspoints are doing that. I just mention this because you seem to use station interfaces as underlying interface for bat0.
You can use tcpdump on the underlying interface to see whether the submitted packets (OGMs) on one side are received exactly the same on the other side. Wireshark has support for batman-adv. So, you could easily check the recorded PCAPs with it.
You can also check "batctl n" to see on which side you can correctly "hear" OGM packets. If you can not hear it only on one side then you should check this one initially (but continue with the rest).
Kind regards, Sven
ok, thanks for the hint. mystery resolved: my AP and STA were both on WDS mode, looks like batman is having issues with 4-address mac frame format. Taking them to standard mode resolved the issue.
But then Im having many tcp out-of-order, dup-ack issues, making streaming almost impossible. Not sure if these are related to MTU stuff. Will need to spend time on this. If any threads regarding this may help a lot.
Best regards
On Tuesday, 19 November 2024 22:58:23 CET soanican@gmail.com wrote:
my AP and STA were both on WDS mode, looks like batman is having issues with 4-address mac frame format. Taking them to standard mode resolved the issue.
batman-adv doesn't even see these headers. It only gets to see the normal 2-address 802.3 header. This is why I said that you should have used tcpdump to capture on top of the underlying interfaces.
And to be honest, I don't get why you are using standard accesspoint interfaces below batman-adv anyway.
Kind regards, Sven
You are right about frame format. Most probably, while converting from 802.11 to 802.3, source MAC address differs so batman is not working with WDS. (can not recognize advertised interface MAC address??)
Now, packet performance issues arise. I suspect on MTU, fragmentation related issues through cascaded/nested structure of bridge/bat0/link system. Will need to dive into monitoring/capturing (as you also mentioned) this system. For example, streaming continues for a while and then stops. Simple restart of networking system solves the issue. If you have have a clue, it can help a lot. I will consider opening a thread for this.
Best regards,
b.a.t.m.a.n@lists.open-mesh.org
-
soanican＠gmail.com -
Sven Eckelmann