New wAP AC (RBwAPG-5HacD2HnD)

no worries, I installed via Mikrotik TFTP

1 Like

The wAP R ac (RBwAPGR-5HacD2HnD) seems to be identical to the new wAP ac, except the miniPCIe-Header is populated (plus SIM slot, LTE antennas, miniPCIe shielding/cooling plate, LTE LED next to PWR & USR). But the board looks the same and is also marked “wAPGR 5HacD2HnD © routerboard.com”. FCC ID is also TV7WAPGR5AC2D. I bought my devices in March 2020.

I’m not sure this warrants a new wiki page, but I can provide photos and missing information.

1 Like

cool, that's nice, in my opinion a separate entry should be made. Maybe @tmomas can confirm what the usual procedure is.

Yep, separate page please.

Hi

tried with openwrt-ipq40xx-mikrotik-mikrotik_cap-ac-initramfs-kernel.bin, but it does not seem to work.

Anyone having a working firmware for this model ?

RouterOS firmware is 6.46.8

What exactly did you do?

Please read and go through all the steps: https://openwrt.org/toh/mikrotik/common

You also need to flash the corresponding sysupgrade.bin file.

the same as with MikroTik wAP AC (RBwAPG-5HacT2HnD). All 140+ of them. :slight_smile:

but with 5hacD2hnd model...
The file openwrt-21.02.0-rc2-ipq40xx-mikrotik-mikrotik_hap-ac2-initramfs-kernel.bin was served via tftpd to correct IP (as seen in tftpd logs), but the device does not boot with 192.168.1.1, just dhcp IP with all IP services closed/disabled(?) on that IP....

i also tried with cap-ac-initramfs....

different chip, please be careful (check specs, and model number)

What RouterOS version was on those RBwAPG-5HacD2HnD ? More than 6.44 ?
Do you still have those HAP AC2 builds anywhere ? The link from your post gives no results...

Yes, ROS was 6.48.5.

And yes, I also have those builds. Do you want me to upload them? Where?

BusyBox v1.31.1 () built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r14057-a28b8fecf6
 -----------------------------------------------------
root@OpenWrt:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r14057-a28b8fecf6'
DISTRIB_TARGET='ipq40xx/generic'
DISTRIB_ARCH='arm_cortex-a7_neon-vfpv4'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r14057-a28b8fecf6'
DISTRIB_TAINTS='no-all'
root@OpenWrt:~# cat /etc/openwrt_version
r14057-a28b8fecf6
root@OpenWrt:~# uname -a
Linux OpenWrt 5.4.52 #0 SMP Thu Aug 6 10:54:51 2020 armv7l GNU/Linux

google drive w/ link access ?

haha, I don't use it. Here there are: uImage.elf and sysupgrade.bin.

tell me, if it worked, otherwise I will upload another build

Works with https://openwrt.org/toh/mikrotik/hap_ac2 files, but you need to use secondary eth port to connect to 192.168.1.1.

DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='22.03.0'
DISTRIB_REVISION='r19685-512e76967f'
DISTRIB_TARGET='ipq40xx/mikrotik'
DISTRIB_ARCH='arm_cortex-a7_neon-vfpv4'
DISTRIB_DESCRIPTION='OpenWrt 22.03.0 r19685-512e76967f'
DISTRIB_TAINTS=''

root@OpenWrt:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.10.138 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r19685-512e76967f) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Sat Sep 3 02:55:34 2022
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: MikroTik hAP ac2

Some issues with MAC address for eth1/eth0 since MAC is randomly set.
Issue listed in Mikrotik HAP AC2 "RBD52G-5HacD2HnD-TC" MAC address issue

I'm having some issues when i tried to install on a 5hacD2hnd, tftp server ip 192.168.1.2 - right?

Anyone having success with VLAN tagging on this AP?
Using 22.03.3 i did get tagged vlan on br-lan via eth0, but i just can't get eth1 (wan) to accept untagged/untagged vlan on same port.

tried via eth1.X or bridge filtering.
is "switch" section just for eth0 port or are bridge vlan filtering and "switch" section mutualy exclusive ?

edit:

might find some info here IPQ40xx Switch Config "Strangeness" (swconfig) - #109 by debug

It's labeled wan but really isn't, it's used as fourth lan port in my case.

anyone checked this?

new wAP AC wireless phy issue

Why is the phy interface assignment different from the old wAP AC?
How to switch it back ?
Who can help? @p34t

old: phy0=5, phy1=2.4
new: phy0=2.4, phy1=5

Impact: complicated scripting

22.03.5
old: as usual
new: snapshot from 2023-05-29

new wAP AC

# iw dev
phy#1
        Interface phy1-ap0
                ifindex 8
                wdev 0x100000002
                channel 52 (5260 MHz), width: 80 MHz, center1: 5290 MHz
phy#0
        Interface phy0-ap0
                ifindex 9
                wdev 0x2
                channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz

old wAP AC

# iw dev
phy#1
        Interface wlan1
                ifindex 6
                wdev 0x100000002
                channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
phy#0
        Interface wlan0
                ifindex 7
                wdev 0x2
                channel 112 (5560 MHz), width: 80 MHz, center1: 5530 MHz

Thanks
Odon
2023-05-29T22:00:00Z

tried 23.05.0-rc2 and snapshot.

i just can get VLANs to work.
one VLAN per one bridge with eth0.X as list-ports

Machine model: MikroTik hAP ac2 (RBwAPG-5HacD2HnD)

It has two eth ports

eth0 is also PoE powered - it is listed as 'wan' port on eth0 "switch"
eth1 is listed as 'lan1' port on eth0 "switch"

in 22.3.5 it works with bridge filtering (br-lan and then br-lan.X as interfaces).

My section of VLAN setting for 23.05.0-rc2:

I use vlan 333 only on wifi-iface/ssid and as untagged on "lan" port on this AP so i can get to it via LAN cable or via WLAN if anything else fails [dhcp,...]:

wan {eth0} port gets guest tagged vlan 67 network.
lan1 {eth1} port has mgmt_local untagged vlan 333 network.

I added wan to bridge br-lan so i can do bridge vlan filtering.

config device 'device1'
	option bridge_empty '1'
	option name 'br-lan'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'
	list ports 'wan'
        option type 'bridge'

config device 'device10'
	option ifname 'br-lan'
	option name 'br-lan.67'
	option type '8021q'
	option vid '67'

config device 'device11'
	option ifname 'br-lan'
	option name 'br-lan.333'
	option type '8021q'
	option vid '333'

config bridge-vlan 'bridge_vlan4'
	option device 'br-lan'
	list ports 'wan:t'
	option vlan '67'

config bridge-vlan 'bridge_vlan7'
	option device 'br-lan'
	list ports 'lan1:u*'
	option vlan '333'

config interface 'lan_guest'
	option proto 'none'
	option device 'br-lan.67'
	option force_link '1'
	option defaultroute '0'
	option delegate '0'

config interface 'mgmt_local'
	option proto 'static'
	option device 'br-lan.333'
	option ipaddr '192.168.2.2'
	option netmask '255.255.255.0'
	option delegate '0'
	option defaultroute '0'

config wifi-iface 'mgmt_local'
	option device 'radio0'
	option disabled '0'
	option mode 'ap'
	option ssid '$hostname'
	option key 'triplexxx'
	option encryption 'psk2+ccmp'
	option network 'mgmt_local'
	option isolate '1'

config wifi-iface 'guest5'
	option device 'radio1'
	option disabled '0'
	option mode 'ap'
	option ssid 'guest'
	option key '123123123z'
	option encryption 'psk2+ccmp'
	option network 'lan_guest'
	option isolate '1'

So far so good.