Banana Pi BPI-Wifi6 router board with Triductor TR6560 + TR5220 wifi SOC

sinovoip · June 5, 2023, 9:08am

Banana Pi BPI-Wifi6 router board with Triductor TR6560 + TR5220 wifi SOC , support OpenWRT ,we also design it support PoE function

Banana%20Pi%20BPI-Wifi6%201

Banana Pi BPI-Wifi6 Router design with Triductor TR6560 + TR5220 wifi SOC, it is a standard wifi6 router solution. Built-in high-performance dual-core ARM Cortec A9 processor for WIFI message forwarding or intelligent business processing, built-in high-performance LSW and hardware NAT, supporting up to 5Gbps message forwarding,Integrated 5GE PHY, one RGMII,Supports one RGMII expansion port, provides 1000Mbps network access capability, and supports two WAN ports. Support hardware intelligent QoS. Support dual-band 2.4G 40M 2*2 +5G160M2.2 DBDC WIFI,Wifi protocol version support to IEEE 802.11ax, backward compatible 802.11a /b/g/n/ac, can support the highest rate of 3Gbps, 2G will reach 573.5Mbps, while 5G will reach 2401.9Mbps， support PoE interface ,add PoE module to support PoE function.

Key Features:

Dual core ARM cortec A9 1.2G Hz
Integrated 5GE PHY, one RGMII
Supports 6 GE MACs,1000M/100M/10M rate mode and standard MIB statistics
Supports IEEE802.11a/b/g/n/ac/ax wireless LAN communication protocol
Support Wifi AP mode and STA mode
Support WPA,WPA2, WPA3 encryption and decryption, pay Chinese WAPI standard

Banana%20Pi%20BPI-Wifi6%203

Why did Banana Pi community develop this product:

wifi6 has been widely popularized in the market, and the telecom operators have large-scale applications. The current router is provided as a finished product, and users cannot add their own special applications on it. The wifi6 board developed by Banana Pi community. In close cooperation with chip manufacturers, apart from the industry and telecom carrier market, we adopt a relatively open source approach and open complete code, so that users can do a variety of self-defined applications on the router. Promote the development of the Internet of Things market

Hardware interface:

Banana%20Pi%20BPI-Wifi6%20interface

PS: we also to do a case for this board , So it can also be sold as a standard wifi6 router

online wiki documents , we will keep update:

https://wiki.banana-pi.org/Banana_Pi_BPI-Wifi6_Router

source code on github:

sinovoip · June 8, 2023, 8:00am

sinovoip · July 5, 2023, 2:25am

Case design for Banana Pi BPI-Wifi6 Router boards

sinovoip · August 21, 2023, 1:34am

source code on github:

sinovoip · August 24, 2023, 1:32am

OpenWRT image

sinovoip · December 16, 2023, 4:05am

phpaiva · January 28, 2024, 9:27pm

In this issue you can see the huge limitations of the WiFi Driver (which is closed source).

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.

sinovoip · May 29, 2024, 10:27am

terri1769 · June 9, 2024, 4:04pm

Seem to be unable to complete opkg update as the specified target folder does not exist. Any fix for this?

root@OpenWrt:~# opkg update
Downloading https://downloads.openwrt.org/releases/22.03.0/targets/tr6560/generic/packages/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.0/targets/tr6560/generic/packages/Packages.gz

Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/base/Packages.gz
Updated list of available packages in /var/opkg-lists/tgp_base
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/base/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/tgp_luci
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/luci/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/tgp_packages
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/tgp_routing
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/routing/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/tgp_telephony
Downloading https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/telephony/Packages.sig
Signature check passed.
Collected errors:
 * opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.0/targets/tr6560/generic/packages/Packages.gz, wget returned 8.
root@OpenWrt:~#

Marcelo_C · July 16, 2024, 9:37pm

I have the same problem. Any help please?

zuowei8 · July 17, 2024, 2:58am

Because OpenWRT offical Software can’t support Triductor TR6560 + TR5220 wifi SOC, you need modify the opkg’s configuration file.

file: /etc/opkg/distfeeds.conf remove the below two lines from configuration file:

  src/gz tgp_core https://downloads.openwrt.org/releases/22.03.0/targets/tr6560/generic/packages

  src/gz tgp_base https://downloads.openwrt.org/releases/22.03.0/packages/arm_cortex-a9/base

test log:

terri1769 · July 17, 2024, 5:38pm

Thanks. That seems to get the lists refreshed but kmod-wireguard is missing which is a required dependency for Wireguard. Is this firmware capable of running Wireguard?

zuowei8 · July 18, 2024, 2:29am

the BSP repo: GitHub - BPI-SINOVOIP/THG6500-TAX2-OPENWRT-BSP you may add kmod-wireguard, then compile your image.