Banana Pi BPI-Wifi6 Mini Router design with Triductor TR6560 + TR5220 wifi SOC, same size as BPI-R3 Mini

sinovoip · December 16, 2023, 3:18am

Banana Pi BPI-Wifi6 Mini Router design with Triductor TR6560 + TR5220 wifi SOC, it is a standard wifi6 router solution,Mini size same as BPI-R3 Mini， Low cost . are you like it ???

same size as Banana Pi BPI-R3 Mini - Banana Pi Wiki and can shared housing

Hardware design same as Banana Pi BPI-Wifi6 Router - Banana Pi Wiki .

sinovoip · December 16, 2023, 4:04am

dangowrt · December 16, 2023, 2:58pm

The hardware looks fine and useful.

Any information regarding the power consumption?

And as there is a connector for a fan I assume it will need it when running in a small case, just like the R3mini, right?

Most important: Will the chip vendor provide support for this SoC and WiFi chip in upstream Linux or at least help others to do so (by making sourcecode, datasheets and firmware publicly available for developers under GPLv2 license)?

I found this Github repo

However, there is only support for old Kernel 5.10 (ie. the level of OpenWrt 21.02) and all drivers are provided as binary blobs only, so we cannot easily port to newer kernel or even just make changes to the kernel without breaking those wifi driver binaries.

A BSP containing binary kernel modules without any sourcecode is only of limited use and impossible to maintain in the long run.

To officially support boards using TR6560 and/or TR52x0 in OpenWrt we would at least need to have all drivers sources released under GPL, and needed firmware blobs published under a license allowing unconditional redistribution and sent to the linux-firmware mailing list as a contribution for inclusion in linux-firmware by the chip vendor owning the IP. Only in this way we can have maintainable open source drivers which qualify for inclusion in OpenWrt without getting anyone in legal trouble or a technical dead-end.

phpaiva · January 28, 2024, 9:28pm

In another post and in OpenWRT forum I have adviced the huge limitations of the WiFi Driver (which is closed source), more details in the issue:

github.com/BPI-SINOVOIP/THG6500-TAX2-OPENWRT-BSP

Multi-AP STA mode and Monitor mode do not work/ are not supported

opened 01:53AM - 27 Jan 24 UTC

phpaiva

I am trying to put to work a radio with a **Multi-AP STA interface** (EasyMesh l…ink), the connectivity at Layer 1/2 seems to work well but at least **IP traffic is not being forwarded to/from the Multi-AP WDS link**. The UCI configuration is: ``` wireless.bh_sta=wifi-iface wireless.bh_sta.device='radio1' wireless.bh_sta.mode='sta' wireless.bh_sta.network='lan' wireless.bh_sta.ssid='SMBackhaulSSID_54:af:97:c5:c0:8d' wireless.bh_sta.key='tFKUEAtQ4zwV3uk6' wireless.bh_sta.macaddr='2c:11:52:4f:41:04' wireless.bh_sta.encryption='psk2+ccmp' wireless.bh_sta.multi_ap='1' wireless.bh_sta.wps_pushbutton='1' wireless.bh_sta.ifname='sta0' ``` The MAC address should be overrided because the default value was "00:00:00:00:00:00" and that leads to a failure. As I said, **with wpa_cli all seems to work well and also the bridge shows the interface**: ``` <3>Trying to associate with 60:a4:b7:7c:6c:8f (SSID='SMBackhaulSSID_54:af:97:c5:c0:8d' freq=5260 MHz) <3>Associated with 60:a4:b7:7c:6c:8f <3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 <3>WPA: Key negotiation completed with 60:a4:b7:7c:6c:8f [PTK=CCMP GTK=CCMP] <3>CTRL-EVENT-CONNECTED - Connection to 60:a4:b7:7c:6c:8f completed [id=0 id_str=] root@OpenWrt:~# brctl show bridge name bridge id STP enabled interfaces br-lan 7fff.d4772b555557 no lan1 lan2 lan3 p-1905 sta0 wan ``` In LUCI: ![image](https://github.com/BPI-SINOVOIP/THG6500-TAX2-OPENWRT-BSP/assets/48815307/fb572830-ed0a-4349-88ed-6525eb8c34a0) But a ping to the IP of the device working as a WDS AP fails (and also, any kind of traffic expected to go through that link): ``` root@OpenWrt:~# ping -I sta0 192.168.0.44 PING 192.168.0.44 (192.168.0.44): 56 data bytes ^C --- 192.168.0.44 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss ``` With a tcpdump in the client interface (sta0) and br-lan, **we can see ARP requests from the device which runs the Multi-AP WDS AP (192.168.0.44), but no response**: ``` root@OpenWrt:~# tcpdump -vvv -i sta0 | grep 192.168.0.44 tcpdump: listening on sta0, link-type EN10MB (Ethernet), capture size 262144 bytes 09:19:36.413026 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:37.452643 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:38.492548 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:39.533129 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:40.573055 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:41.613377 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:42.653261 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:43.692417 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:44.732137 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:47.904990 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:48.972169 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:50.013555 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:51.862394 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:52.892419 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:53.932962 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:19:56.222445 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 ^C264 packets captured 266 packets received by filter 0 packets dropped by kernel ``` ``` root@OpenWrt:~# ^C root@OpenWrt:~# tcpdump -vvv -i br-lan | grep 192.168.0.44 tcpdump: listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes 09:20:02.492561 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:03.532611 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:04.579466 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:05.612608 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:06.651959 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:07.692552 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:08.732910 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:09.773520 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:10.812390 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:11.852520 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:12.892041 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 09:20:13.932065 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.0.1 tell 192.168.0.44, length 28 ^C216 packets captured 229 packets received by filter 0 packets dropped by kernel ``` This shows that t**he inbound traffic is being received but the system is unable to forward it properly**. Also the outbound traffic won't go out for the same reason, the system can't forward properly to the WDS link to send it out. **Regarding the monitor mode,** simply there is no capability using an **iw list** command. **There is only "managed" and "AP"** modes. ``` Wiphy phy0 wiphy index: 0 max # scan SSIDs: 8 max scan IEs length: 1000 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Available Antennas: TX 0 RX 0 Supported interface modes: * managed * AP ``` And also by creating one interface in monitor mode does not work. **Am I doing something wrong? There will be support for MultiAP links? And what about monitor mode?** Thanks in advance. Pablo.