[B.A.T.M.A.N.] Issue with mesh network on different RTL chipsets
Francesco Salvatore [fabbricadigitale]
f.salvatore at fabbricadigitale.it
Thu Jul 19 11:53:26 CEST 2018
we are trying to build a mesh network on Raspberry Pi boards with some USB
Wi-Fi adapters that have different Realtek chipsets and, consequently,
different drivers. Specifically we have:
Gateway => driver rtl8812au (probably the chipset is rtl8811a)
Client => driver rtl8821cu (probably the chipset is rtl8811u)
We are using Raspbian with kernel 4.14.34-v7+ and we tried using built-in
kernel version of batman-adv (2017.3) and then with latest stable (2018.2),
built with all compile flags active, less than network coding option.
The problem is (seems to be) related to client > gateway communication,
specifically in receive capability of the gateway if we use the scenario
The client is able to join the network because gateway recognises it as an
originator and the client correctly recognises the gateway, but even so no
client network traffic is visible on the gateway.
For example, the client is unable to obtain an IP address from DHCP server;
we can see DHCPOFFER packet on the client (dumping with tcpdump) but we
cannot see the same packet transit through the gateway.
The client is also unable to ping or traceroute other neighbours or even the
We also tried to disable, one by one, multicast optimization, bridge loop
avoidance, fragmentation and so forth, but unfortunately without success.
All test were made using batctl tools (ping, traceroute, tcpdump etc.).
In other cases, i.e. if we swap the roles (using rtl8812au as client and
rtl8821cu as gateway) or if we use same chipset both for client and gateway,
we have no issue at all.
Do you know if there's any issue related to listed hardware chipsets? If
yes, you know of some action I can take to fix that problem?
Thank you, have a nice day!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5344 bytes
Desc: not available
More information about the B.A.T.M.A.N