saf
May 7, 2026, 7:50am
1
I have a cAP ax which I haven’t used for 1 year (and 1 year ago I only used it via capsmap, for a few days)
Now it’s directly connected to my Linux desktop, which has 192.168.88.2 set on it’s interface.
I reset the configuration with netinstall-cli:
sudo ./netinstall-cli -r i eno1 routeros-7.22.2-arm64.npk wifi-qcom-7.22.2-arm64.npk
Successfully finished install device <correct)mac_address>
When I open http://192.168.88.1 in the browser, I see the web interface for a few seconds, then I get “This site can’t be reached”.
I also tried WinBox for Linux. After I plug in the power to the cAP ax, I see it in the Neighbors list as
<correct_mac_address> 0.0.0.0 Mikrotik 7.22.2 cAPGi-5HaxD2HaxD 00:00:30 ether1
But it disappears after a few seconds.
So… is my cAP ax broken?
Have you tried connecting to either ether2 or wireless? Don’t know what default settings work like.
saf
May 7, 2026, 8:14am
3
Yes! I haven’t even considered WiFi.
It’s weird that connecting via ether1 didn’t work, though.
Thank you!
Only for the record, no, it is quite normal in a "default" configuration, typycally on Mikrotik's (this may vary depending on the specific model):
ether1 is WAN <- but this is also ehertboot port, the only one you can use for netinstall
all other interfaces are asssembled into a bridge that is LAN
besides firewall protection, only LAN is allowed for mac winbox service
So access from ether1 is prevented.
By default, the device is configured as a wireless access point, with the first ethernet port (Eth1) configured as a DHCP client, and the second interface bridged together with the wireless interface. A DHCP server is configured on the bridge...
Manual says:
By default, the device is configured as a wireless access point, with the first ethernet port (Eth1) configured as a DHCP client, and the second interface bridged together with the wireless interface. A DHCP server is configured on the bridge interface.
So yes, eth2 is the thing.
saf:
So… is my cAP ax broken?
It is very difficult to brick Mikrotik Devices, they have two way of booting, the firmware RouterBoot and os RouterOS.