wAP ax Access Pts ship with ether1 unbridged by default

Hello,

Wanted to bring up something I ran into after unboxing my new APs (wAP ax wAPG-5HaxD2HaxD) yesterday. Got them to pair with my L009, however these do not work OOTB. In fact, it took me about 4 hours to figure out why they had no internet access at all. Even when hooked directly to modem I got nothing and couldn’t update the firmware. I couldn’t even ping the switch it was connected to.

It turns out that these units ship with the following interfaces bridged: ether2, wifi1, wifi2. I’m sure from the title you can tell that by adding ether1 to the existing bridge, these units come to life. But why would they ship these in such a state? I don’t know enough about networking to piece it together. Is there some other application these are intended for where having the POE LAN unbridged makes sense?

The whole default configuration should be seen, but my guess is that the ether1 - regardless its PoE capabilities - is intended as WAN (like on most other Mikrotik devices).

I.e. the Wap Ax can be used as a stand-alone access point AND router, as opposed to a “pure AP” with all ports bridged together.

If you have a copy of the default configuration, it would be nice if you could post it or contact tangent, so that it can be added to the collection of the reference default configs:
https://tangentsoft.com/mikrotik/dir/defconf

The old Wap model:
https://tangentsoft.com/mikrotik/file?name=defconf/RBwAP2nDr2.rsc
seemingly has a default configuration with wlan as LAN and ether1 as WAN BUT no bridge (but it has only one ethernet).

100% correct.
Default they are configured as a normal router with WAN on ether1.
Quite often those wAP devices are used in capsman environments (just like cAP AX and alike) where setting them to caps mode will bridge all interfaces.

Even QuickSet is extremely limited on this device (Home AP Dual being the only option which simply makes it act as a router as well).
So good thing most seasoned MT users don’t use QuickSet anyhow :laughing:

Since this new hap Ax has PoE on ether1 means that in a “normal” AP install:

  1. the device will be powered by PoE
  2. there will only be one ethernet cable arriving to it (and it will go to ether1)

So ether 1 and ether2 can be simply exchanged, putting ether1 into the bridge (and thus LAN) and leaving ether2 unconnected (and set as WAN), right?

Or maybe it would be smart to use ether2 as “emergency access” or “trusted”.

All valid options. Whatever you want.
The power and pitfall of ROS …

What I do for such devices (also cap AX)

  • make new user with admin rights
  • remove default admin user
  • reset to caps mode keeping users
  • add VLAN interface to bridge
  • DHCP client to VLAN interface
  • activate ROMON on all ports
  • Change system name as needed
  • add NTP client
  • and that’s it.
    Wifi part is done in capsman controller.