Mikrotik hAP AC tftp kernel image booting (fixed) - SFP (fixed) - PoE in (fixed) - PoE out (fixed) - Slow switch (not fixed)

Dear friends,

I am trying to boot latest OpenWrt 22.03.0-rc6* image for the hAP AC (RB962UiGS-5HacT2HnT).

https://downloads.openwrt.org/releases/22.03.0-rc6/targets/ath79/mikrotik/openwrt-22.03.0-rc6-ath79-mikrotik-mikrotik_routerboard-962uigs-5hact2hnt-initramfs-kernel.bin

Firmware is renamed to rb-nor-flash-16M-ac-initramfs-kernel.bin

DNS is served from a Mikrotik router with bootp support.
The TFTP server is a Synology NAS TFTP.
I am booting from eth1 as expected.

I can see that the file rb-nor-flash-16M-ac-initramfs-kernel.bin is fetched by network boot.
However, if I plug the eth2 ethernet connector to my laptop, and set address 192.168.1.10 I cannot ping 192.168.1.1.

Running wireshard shows no activity on the eth2 interface of the hAP AC.

Do you have any idea what is going wrong?
It seems that the hAP lacks proper network initialisation.

Kind regards,
French Fries

1 Like

Dear Friends,

After around 20 hours or playing and hacking around the hAP ac ... still no luck.

I spent the whole day trying to hack the Mikrotik hAP ac and could not find a way to boot it over OpenWRT. I played with various OpenWRT firmware 7.4.1 and 7.5 and bricked the device several times and had to reinstall using netinstall.

I followed the General Mikrotik installation using dnsmasq on a Debian station.

I could not get the hAP ac to boot using dhcp or boot configuration.

The problem is that I don't have serial console access. So I installed a USB to serial converter with null-modem. I can see console but only after booting. So I don't have access to the serial console boot menu.

So if anyone knows how to boot the Mikrotik hAP with firmware 7.4.1 over bootp I would be delighted. Switching this issue to development as it is obviously not a simpe install task.

Kind regards,

Downgrade bootloader and RouterOS to 6.xx version.

I will try one more time.

https://help.mikrotik.com/docs/display/RKB/Downgrading+RouterOS

Follow these steps to downgrade to an older version

Make sure you have npk packages of the same architecture type as your device.
Upload the older version npk files to the device with FTP, Webfig or Winbox.
Issue the command line command /system/package/downgrade
Issue the command /system/reboot

Seems easy.

Bingo, downgrading to RouterOS 6.49.6 worked like a charm.

I tried to network boot OpenWRT lastest RC and this did not work:

here is my script
cat loader.sh

#!/bin/bash
IFNAME=enp0s31f6
/sbin/ip addr replace 192.168.1.10/24 dev $IFNAME
/sbin/ip link set dev $IFNAME up

/usr/sbin/dnsmasq \
--no-daemon \
--listen-address 192.168.1.10 \
--bind-interfaces \
-p0 \
--dhcp-authoritative \
--dhcp-range=192.168.1.100,192.168.1.200 \
--bootp-dynamic \
--dhcp-boot=rb-nor-flash-16M-ac-initramfs-kernel.bin \
--log-dhcp \
--enable-tftp \
--tftp-root=$(pwd)

It results in a giant loop:

sudo sh ./loader.sh 
[sudo] Mot de passe de xxxx : 
dnsmasq: démarrage avec le DNS désactivé (version 2.86)
dnsmasq: options Ă  la compilation : IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, plage d'adresses IP 192.168.1.100 -- 192.168.1.200, durée de bail 1h
dnsmasq-tftp: TFTP root est/home/mario/tftp  
dnsmasq-dhcp: 3554951172 la gamme DHCP disponible est : 192.168.1.100 -- 192.168.1.200
dnsmasq-dhcp: 3554951172 Classe de vendeur ('Vendor Class') : Mips_boot
dnsmasq-dhcp: 3554951172 DHCPDISCOVER(enp0s31f6) 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 3554951172 options: enp0s31f6
dnsmasq-dhcp: 3554951172 DHCPOFFER(enp0s31f6) 192.168.1.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 3554951172 options demandées : 1:netmask, 3:router
dnsmasq-dhcp: 3554951172 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 3554951172 serveur suivant : 192.168.1.10
dnsmasq-dhcp: 3554951172 sent size:  1 option: 53 message-type  2
dnsmasq-dhcp: 3554951172 sent size:  4 option: 54 server-identifier  192.168.1.10
dnsmasq-dhcp: 3554951172 sent size:  4 option: 51 lease-time  1h
dnsmasq-dhcp: 3554951172 sent size:  4 option: 58 T1  30m
dnsmasq-dhcp: 3554951172 sent size:  4 option: 59 T2  52m30s
dnsmasq-dhcp: 3554951172 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 3554951172 sent size:  4 option: 28 broadcast  192.168.1.255
dnsmasq-dhcp: 3554951172 sent size:  4 option:  3 router  192.168.1.10
dnsmasq-dhcp: 2447658472 la gamme DHCP disponible est : 192.168.1.100 -- 192.168.1.200
dnsmasq-dhcp: 2447658472 Classe de vendeur ('Vendor Class') : Mips_boot
dnsmasq-dhcp: 2447658472 DHCPDISCOVER(enp0s31f6) 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2447658472 options: enp0s31f6
dnsmasq-dhcp: 2447658472 DHCPOFFER(enp0s31f6) 192.168.1.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2447658472 options demandées : 1:netmask, 3:router
dnsmasq-dhcp: 2447658472 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 2447658472 serveur suivant : 192.168.1.10
dnsmasq-dhcp: 2447658472 sent size:  1 option: 53 message-type  2
dnsmasq-dhcp: 2447658472 sent size:  4 option: 54 server-identifier  192.168.1.10
dnsmasq-dhcp: 2447658472 sent size:  4 option: 51 lease-time  1h
dnsmasq-dhcp: 2447658472 sent size:  4 option: 58 T1  30m
dnsmasq-dhcp: 2447658472 sent size:  4 option: 59 T2  52m30s
dnsmasq-dhcp: 2447658472 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 2447658472 sent size:  4 option: 28 broadcast  192.168.1.255
dnsmasq-dhcp: 2447658472 sent size:  4 option:  3 router  192.168.1.10

I spent the whole day trying to TFTP boot.
I did verify that I could tftp the file from command line.
My station has no firewall (it is disabled) and is connected with a wire to the hAP ac eth1 port (WAN).

It is the hAP ac not fetching OpenWRT.

I only have experience with a single MikroTik device - the RB5009UG+S+IN - but once I set a 192.168.88.x IP on the system running the TFTP server, and a corresponding DHCP range, TFTP started working.

The newer bootloader only uses BOOTP and will not boot properly with any options for some reason. I am on Windows and patched tftpd64 to support it, perhaps a similar patch can be made for dnsmasq or there is a config to turn off all unneeded options.

1 Like

Hello,

I can confirm bootp success with:

  • Adress range 192.168.88.0/24
  • RouterOS v 6.49.6
  • OpenWRT v19.07.09

Under OpenWRT v19.07.09 the hAP AC only offers a/b/n on the first radio.
The second radio with ac support is not seen by the system.
The sfp port is not recognised.

Before flashing OpenWRT and upgrading, I need to confirm that only v19.08.09 works. So I will confirm various testing before installing OpenWRT.

Here is the TFTP log:

sudo sh ./loader.sh 
dnsmasq: démarrage avec le DNS désactivé (version 2.86)
dnsmasq: options Ă  la compilation : IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, plage d'adresses IP 192.168.88.100 -- 192.168.88.200, durée de bail 1h
dnsmasq-tftp: TFTP root est/home/mario/tftp/  
dnsmasq-dhcp: 2163033904 la gamme DHCP disponible est : 192.168.88.100 -- 192.168.88.200
dnsmasq-dhcp: 2163033904 Classe de vendeur ('Vendor Class') : Mips_boot
dnsmasq-dhcp: 2163033904 options: bootp, enp0s31f6
dnsmasq-dhcp: 2163033904 BOOTP(enp0s31f6) 192.168.88.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2163033904 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 2163033904 serveur suivant : 192.168.88.10
dnsmasq-dhcp: 2163033904 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 2163033904 sent size:  4 option: 28 broadcast  192.168.88.255
dnsmasq-dhcp: 2163033904 sent size:  4 option:  3 router  192.168.88.10
dnsmasq-tftp: envoyé /home/mario/tftp/rb-nor-flash-16M-ac-initramfs-kernel.bin à 192.168.88.158
dnsmasq-dhcp: 2069454208 la gamme DHCP disponible est : 192.168.88.100 -- 192.168.88.200
dnsmasq-dhcp: 2069454208 Classe de vendeur ('Vendor Class') : udhcp 1.30.1
dnsmasq-dhcp: le client 2069454208 fourni le nom : OpenWrt
dnsmasq-dhcp: 2069454208 DHCPDISCOVER(enp0s31f6) 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2069454208 options: enp0s31f6
dnsmasq-dhcp: 2069454208 DHCPOFFER(enp0s31f6) 192.168.88.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2069454208 options demandées : 1:netmask, 3:router, 6:dns-server, 12:hostname, 
dnsmasq-dhcp: 2069454208 options demandées : 15:domain-name, 28:broadcast, 42:ntp-server, 
dnsmasq-dhcp: 2069454208 options demandées : 121:classless-static-route
dnsmasq-dhcp: 2069454208 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 2069454208 serveur suivant : 192.168.88.10
dnsmasq-dhcp: 2069454208 sent size:  1 option: 53 message-type  2
dnsmasq-dhcp: 2069454208 sent size:  4 option: 54 server-identifier  192.168.88.10
dnsmasq-dhcp: 2069454208 sent size:  4 option: 51 lease-time  1h
dnsmasq-dhcp: 2069454208 sent size:  4 option: 58 T1  30m
dnsmasq-dhcp: 2069454208 sent size:  4 option: 59 T2  52m30s
dnsmasq-dhcp: 2069454208 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 2069454208 sent size:  4 option: 28 broadcast  192.168.88.255
dnsmasq-dhcp: 2069454208 sent size:  4 option:  3 router  192.168.88.10
dnsmasq-dhcp: 2069454208 la gamme DHCP disponible est : 192.168.88.100 -- 192.168.88.200
dnsmasq-dhcp: 2069454208 Classe de vendeur ('Vendor Class') : udhcp 1.30.1
dnsmasq-dhcp: le client 2069454208 fourni le nom : OpenWrt
dnsmasq-dhcp: 2069454208 DHCPREQUEST(enp0s31f6) 192.168.88.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 2069454208 options: enp0s31f6
dnsmasq-dhcp: 2069454208 DHCPACK(enp0s31f6) 192.168.88.158 74:4d:28:ce:6a:8b OpenWrt
dnsmasq-dhcp: 2069454208 options demandées : 1:netmask, 3:router, 6:dns-server, 12:hostname, 
dnsmasq-dhcp: 2069454208 options demandées : 15:domain-name, 28:broadcast, 42:ntp-server, 
dnsmasq-dhcp: 2069454208 options demandées : 121:classless-static-route
dnsmasq-dhcp: 2069454208 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 2069454208 serveur suivant : 192.168.88.10
dnsmasq-dhcp: 2069454208 sent size:  1 option: 53 message-type  5
dnsmasq-dhcp: 2069454208 sent size:  4 option: 54 server-identifier  192.168.88.10
dnsmasq-dhcp: 2069454208 sent size:  4 option: 51 lease-time  1h
dnsmasq-dhcp: 2069454208 sent size:  4 option: 58 T1  30m
dnsmasq-dhcp: 2069454208 sent size:  4 option: 59 T2  52m30s
dnsmasq-dhcp: 2069454208 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 2069454208 sent size:  4 option: 28 broadcast  192.168.88.255
dnsmasq-dhcp: 2069454208 sent size:  4 option:  3 router  192.168.88.10
dnsmasq-dhcp: 2069454208 sent size:  7 option: 12 hostname  OpenWrt

On the converse, I could not get it to boot OpenWRT 22.03.0-rc6

sh ./loader.sh 
dnsmasq: démarrage avec le DNS désactivé (version 2.86)
dnsmasq: options Ă  la compilation : IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, plage d'adresses IP 192.168.88.100 -- 192.168.88.200, durée de bail 1h
dnsmasq-tftp: TFTP root est/home/mario/tftp/  
dnsmasq-dhcp: 120154460 la gamme DHCP disponible est : 192.168.88.100 -- 192.168.88.200
dnsmasq-dhcp: 120154460 Classe de vendeur ('Vendor Class') : Mips_boot
dnsmasq-dhcp: 120154460 options: bootp, enp0s31f6
dnsmasq-dhcp: 120154460 BOOTP(enp0s31f6) 192.168.88.158 74:4d:28:ce:6a:8b 
dnsmasq-dhcp: 120154460 nom de fichier 'bootfile' : rb-nor-flash-16M-ac-initramfs-kernel.bin
dnsmasq-dhcp: 120154460 serveur suivant : 192.168.88.10
dnsmasq-dhcp: 120154460 sent size:  4 option:  1 netmask  255.255.255.0
dnsmasq-dhcp: 120154460 sent size:  4 option: 28 broadcast  192.168.88.255
dnsmasq-dhcp: 120154460 sent size:  4 option:  3 router  192.168.88.10
dnsmasq-tftp: envoyé /home/mario/tftp/rb-nor-flash-16M-ac-initramfs-kernel.bin à 192.168.88.158

File is sent to the hAP ac and then nothing happens.

I used the following image:
openwrt-22.03.0-rc6-ath79-mikrotik-mikrotik_routerboard-962uigs-5hact2hnt-initramfs-kernel.bin (first attempt)
and OpenWRT snapshot (second attempt)

Not having console on the hAP AC is a real pain.
After two days of hacking I am becoming quite discouraged.

So my question is: should I install OpenWRT 19.07 and then sysupgrade?

I'd go that route, since you got recovery through the bootloader working. Do sysupgrade without keeping settings though, from 19.07.

Thank you very much. Installing 19.07 and then upgrading to lastest release candidate It works like a charm.

1 Like

WPA3-SAE is also supported and works on the hAP AC, which is a good surprise as a lot of people on Mikrotik website claimed that the hAP AC would never support WPA3.

The hAP ac has three radio devices and I could only test two radio devices. But first test shows very good wireless speed under WPA3:

iperf3  -P4 -c 192.168.10.12
Connecting to host 192.168.10.12, port 5201
[  5] local 192.168.10.102 port 56250 connected to 192.168.10.12 port 5201
[  7] local 192.168.10.102 port 56266 connected to 192.168.10.12 port 5201
[  9] local 192.168.10.102 port 56276 connected to 192.168.10.12 port 5201
[ 11] local 192.168.10.102 port 56290 connected to 192.168.10.12 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  19.6 MBytes   165 Mbits/sec    0    837 KBytes       
[  7]   0.00-1.00   sec  15.5 MBytes   130 Mbits/sec    0    700 KBytes       
[  9]   0.00-1.00   sec  8.13 MBytes  68.2 Mbits/sec    0    421 KBytes       
[ 11]   0.00-1.00   sec  13.6 MBytes   114 Mbits/sec    0    690 KBytes       
[SUM]   0.00-1.00   sec  56.9 MBytes   477 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    0    837 KBytes       
[  7]   1.00-2.00   sec  10.0 MBytes  83.9 Mbits/sec    0    700 KBytes       
[  9]   1.00-2.00   sec  11.1 MBytes  93.3 Mbits/sec    0    634 KBytes       
[ 11]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    0    701 KBytes       
[SUM]   1.00-2.00   sec  43.6 MBytes   366 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec    0    837 KBytes       
[  7]   2.00-3.00   sec  10.0 MBytes  83.9 Mbits/sec    0    700 KBytes       
[  9]   2.00-3.00   sec  9.88 MBytes  82.8 Mbits/sec    0    706 KBytes       
[ 11]   2.00-3.00   sec  10.0 MBytes  83.9 Mbits/sec    0    701 KBytes       
[SUM]   2.00-3.00   sec  41.1 MBytes   345 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  10.0 MBytes  83.9 Mbits/sec    0    837 KBytes       
[  7]   3.00-4.00   sec  11.2 MBytes  94.4 Mbits/sec    0    737 KBytes       
[  9]   3.00-4.00   sec  10.0 MBytes  83.9 Mbits/sec    0    740 KBytes       
[ 11]   3.00-4.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[SUM]   3.00-4.00   sec  41.2 MBytes   346 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec    0    837 KBytes       
[  7]   4.00-5.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[  9]   4.00-5.00   sec  10.0 MBytes  83.9 Mbits/sec    0    740 KBytes       
[ 11]   4.00-5.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[SUM]   4.00-5.00   sec  41.2 MBytes   346 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   5.00-6.00   sec  11.2 MBytes  94.4 Mbits/sec    0    837 KBytes       
[  7]   5.00-6.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[  9]   5.00-6.00   sec  11.2 MBytes  94.4 Mbits/sec    0    740 KBytes       
[ 11]   5.00-6.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[SUM]   5.00-6.00   sec  42.5 MBytes   357 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   6.00-7.00   sec  10.0 MBytes  83.9 Mbits/sec    0    837 KBytes       
[  7]   6.00-7.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[  9]   6.00-7.00   sec  8.75 MBytes  73.4 Mbits/sec    0    740 KBytes       
[ 11]   6.00-7.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[SUM]   6.00-7.00   sec  38.8 MBytes   325 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   7.00-8.00   sec  10.0 MBytes  83.9 Mbits/sec    0    837 KBytes       
[  7]   7.00-8.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[  9]   7.00-8.00   sec  10.0 MBytes  83.9 Mbits/sec    0    740 KBytes       
[ 11]   7.00-8.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[SUM]   7.00-8.00   sec  40.0 MBytes   336 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   8.00-9.00   sec  10.0 MBytes  83.9 Mbits/sec    0    837 KBytes       
[  7]   8.00-9.00   sec  10.0 MBytes  83.9 Mbits/sec    0    737 KBytes       
[  9]   8.00-9.00   sec  11.2 MBytes  94.4 Mbits/sec    0    783 KBytes       
[ 11]   8.00-9.00   sec  10.0 MBytes  83.9 Mbits/sec    0    781 KBytes       
[SUM]   8.00-9.00   sec  41.2 MBytes   346 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   9.00-10.00  sec  11.2 MBytes  94.4 Mbits/sec    0    837 KBytes       
[  7]   9.00-10.00  sec  10.0 MBytes  83.9 Mbits/sec    0    775 KBytes       
[  9]   9.00-10.00  sec  10.0 MBytes  83.9 Mbits/sec    0    783 KBytes       
[ 11]   9.00-10.00  sec  11.2 MBytes  94.4 Mbits/sec    0    816 KBytes       
[SUM]   9.00-10.00  sec  42.5 MBytes   357 Mbits/sec    0             
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   116 MBytes  97.2 Mbits/sec    0             sender
[  5]   0.00-10.02  sec   112 MBytes  94.1 Mbits/sec                  receiver
[  7]   0.00-10.00  sec   107 MBytes  89.5 Mbits/sec    0             sender
[  7]   0.00-10.02  sec   104 MBytes  87.1 Mbits/sec                  receiver
[  9]   0.00-10.00  sec   100 MBytes  84.2 Mbits/sec    0             sender
[  9]   0.00-10.02  sec  97.2 MBytes  81.3 Mbits/sec                  receiver
[ 11]   0.00-10.00  sec   106 MBytes  89.0 Mbits/sec    0             sender
[ 11]   0.00-10.02  sec   103 MBytes  85.9 Mbits/sec                  receiver
[SUM]   0.00-10.00  sec   429 MBytes   360 Mbits/sec    0             sender
[SUM]   0.00-10.02  sec   416 MBytes   348 Mbits/sec                  receiver

iperf Done.

The average speed is 350-360 Mbit/s which is near maximum speed of AC networks with two radios.

Also I could connect using ssh on the hAP ac and monitor CPU usage, which is close to 1% during test. So everything which was written about the hAP ac being slow and consuming CPU resources is pure nonses. It is indeed a very good and up-to-date device.

I think Mikrotik should contact the writer of the article about the hAP ac being slow and ask him to remove the article OR device to suit him for false information. I cannot elaborate on that but it is probably an article being written by a competitor.

1 Like

Finally I now need to test SFP module support of the hAP ac.
How can I test SFP support and do I need to recompile OpenWRT for proper support?

Install the ethtool-full package to test.

The hAP AC is CPU bottlenecked even with 2 chain devices - notice your screenshot shows 97% in SIRQ which is processing hardware interrupts, i.e. maxed out. No idea why they put a 3 chain radio in it when the CPU can't use it.

PS - if using it as a pure AP, you can get some additional throughput by removing all netfilter / conntrack modules.

1 Like

Thank you for all this valuable information.

I did some testing on an ARM8 4 core AP and found that SIRQ was near 25%, so this means that the AP is constantly interrupting. As wireless is (probably) a single core process, I don't know if this really means something. So it does not bother me to see nearly 100% interruption.

I installed ethtool-full but don't know which command to run to find the SFP port.
If I run ifconfig -a the SFP port is not listed.

Also, I would like to configure PoE out on ethernet port 5 (LAN 4 in OpenWRT).
The hAP AC is able to provide chain PoE out on port 5 when PoE in is provided. Mikrotik describes this as "passive PoE". This can be used to chain 2 APs together.

There is a module kmod-i2c-gpio but don't know if this is suitable.

SFP port works and is labelled "eth1".
I added it to br-lan and used an ethernet module to validate it works.

Therefore SFP port is supported.
Great news !!!