i’ve run into a problem setting up my hap ax² and ax³ with capsman. I’m running a L009UiGS with the wifiwave2 package. I configured some vlans and connected the ax² with a trunk port direct with the l009.
The capsman is configured on the l009 and the ax² detects the capsman and i’m able to provision the ax² but in the moment the l009 creates the interfaces, it says instant “— no connection to CAPsMAN”.
On the ax² side it says it says always “— managed by CAPsMAN”.
I configured the ax² in the first try by myself. After reconfiguring a few times i made a reset and cecked CAPs mode with the same result.
Here are my CAPsMAN settings.
And here are the CAP settings.
Datapath is configured for my wireless network vlan.
If i setup the configuration same like the l009 and set the manager of the interfaces to local all works fine. The devices connected via the datapath to my bridge and all wifi devices in my network get an ip from the dhcp in the correct vlan.
I don’t get it why the ax² which is directly connected via a 0,5m cable can’t connect correctly. Maybe i’m looking for too long over the problem and can’t see were i configured something wrong.
I’m relative new to mikrotik devices and hope some of you guys can help me.
The discovery interface is my management vlan (id 100). the capsman is running on the same vlan. The capsman can see the cap the whole time. See picture below.
Thats what you meant right?
Why no vlan filtering on bridge? If i deactivate the vlan filtering, i loose the ability to use the ethernet ports for other vlans in my understanding.
I tried it. See below.
CAPsMAN
CAP
Bridge
CAP settings
The result is the same. The cap says managed by capsman and the capsman says no connection to capsman. And the Remote CAP is the complete time seen on the L009. I would understand this if there are any switch in between but its only a 0,5m cable. The wireless interfaces won’t do anything unless is set it to local and it works fine.
Ah, missed the part on AX2 and ether ports.
If you want to use those ether ports as well, you are indeed better off to specify the uplink port as trunk and have VLAN filtering on.
But I believe you will have to specify a VLAN interface with the correct pvid attached to bridge for the wireless parts on that cap.
In my setup (recently moved to capsman at home) I use my AX2/AX3 devices only has AP, no ether devices attached.
Something to test further with …
I have the ax² connected via trunk port with my L009. All VLANs are available. My VLAN for the wifi is VLAN ID 20.
My configured datapath for the slave interfaces is pointing to vlan 20.
I don’t understand at which point my config is wrong.
For my understanding i’ve configured the bridge etc. to work with the ethernet ports. At this point i configured the datapath and the cap settings to connect to the capsman. I thougt this should work. The cap joined the capsman but both wireless interfaces won’t start to work unless i configured all manually and set the manager to local. At this point the interfaces connect to the bridge via the configured datapath.
Actually, you need to remove everything related to wifiwave2 setup except for caps part.
Everything set up locally, will get preference over whatever comes from capsman !
As a test, reset device to caps mode (remember to keep user).
See if wifi works then.
Only then add the ethernet part.
I thougt i get all from capsman but the datapath need to be configured on cap because there is a point in the cap settings “Slaves Datapath”. The name of the bridge could be anything on the cap side.
Edit: Should the connection to the cap be configured as trunk port?
Edit 2: I made the reset. The connection from the l009 side is a trunk port. The connection from the cap is untouched. i can’t reach it. but it shows up in the remote cap on the l009 after i set the capsman interface to my bridge. i’m able to provision the cap but it says “no connection to capsman”.