A month ago I bought 3 CAP AX and crs326-24g-2s router. I wanted to make a capsman manager from the router. Unfortunately, I didn’t read that it is impossible to install the wifi wave2 package … (not enough space) I updated all devices to ROS 7.10, configured CRS as the main router, separated networks on vlans and decided to install/configure the manager on one of the accesspoints. As you can already guess since I’m writing - I couldn’t cope
Is it at all possible to configure Capsman so that one accesspoint is the manager and accesspoint and controls the next two?
Supposedly this can be done from the CLI, but I haven’t found any information.
Running CAPsMAN Manager on CAP ax is no problem at all, especially since it already comes with wifiwave2 package installed.
Keep in mind, however, that (new) wifiwave2 CAPsMAN is slightly different from “old” CAPsMAN, so make sure you’re not trying to apply CAPsMAN instructions to wifiwave2 CAPsMAN.
I have done my own configuration in several ways, both on the forum and on the wiki. Even doing the simplest configuration without vlans. I was getting to the end, I had the information “interface managed by capsman” but no SSID was displayed.
Without a crystal ball nobody is going to know what you did or did not do in your config …
terminal
/export file=anynameyouwish
Remove sensitive info like serial number, public wan ip, …
Post between code quotes for readability (5th option from the left)
I found one of the configs I was making.
At the moment, one AP is connected and it works on its own.
In this configuration I had information “no connection to CAPsMAN, managed locally”
I have to look back where it was stated by MT staff but it could be (for now ?) local radios can not be managed by capsman on wifiwave2.
You have to configure those locally (which is not that difficult since it will be more or less the same settings as for caps-radios).
Are the other caps connecting ?
PS 10 VLANs ? You may want to start a bit simpler to iron out the wrinkles.
I dont get it. Setting up a capax as an access point/switch is dirt simple while using capsman is a dogs breakfast especially for beginners.
If you cannot handle the simple, then attempting capsman is not a good plan.
(1) The CRS is NOT A ROUTER, its a switch with some routing power. Be advised if you have a 1 gig connection you got the wrong device.
I would say its a decent 300/300 ISP device…
(2) Your mistake is treating a cap like a router vice an ap/switch. No networks or even vlans are identified on the caps, only the management or trusted vlan is identified, aka the vlan from which the cap gets its IP address from!!
General Concept ( one bridge )
Do not identify any vlans in wifi settings!!!
Use ether2, as an OFF Bridge access to actually do the bulk of configuration safely prior to attaching the cap to the network at location.
In fact, if the cap is not readily accessible to remove/access to reprogram, ensure you run an ethernet cable from ether2 to a location where you can plug in a laptop to make changes. https://forum.mikrotik.com/viewtopic.php?t=181718
/interface bridge
add name=bridge1 protocol-mode=none vlan-filtering=yes { last entry on config }
/interface ethernet
set [ find default-name=ether2 ] name=offbridge
/interface vlan
add interface=bridge1 name=vlan210_MGMT vlan-id=210
/interface list
add name=management
/ip neighbor discovery-settings
set discover-interface-list=management
/interface list member
add interface=vlan210_MGMT list=management
add interface=offbridge list=management
/interface bridge port
add bridge=bridge1 ingress-filtering=yes frame-types=admit-only-vlan-tagged interface=ether1
add bridge=bridge1 ingress-filtering=yes frame-types=admit-priority-and-untagged interface=nameofwifi1 pvid=202
add bridge=bridge1 ingress-filtering=yes frame-types=admit-priority-and-untagged interface=nameofwifi2 pvid=203
add bridge=bridge1 ingress-filtering=yes frame-types=admit-priority-and-untagged interface=nameofwifi3 pvid=204
add bridge=bridge1 ingress-filtering=yes frame-types=admit-priority-and-untagged interface=nameofwifi4 pvid=205
/interface bridge vlan
add bridge=bridge1 tagged=bridge1,ether1 vlan-ids=210
add bridge=bridge1 tagged=ether1 untagged=nameofwifi1 vlan-ids=202
add bridge=bridge1 tagged=ether1 untagged=nameofwifi2 vlan-ids=203
add bridge=bridge1 tagged=ether1 untagged=nameofwifi3 vlan-ids=204
add bridge=bridge1 tagged=ether1 untagged=nameofwifi4 vlan-ids=205
/ip address
add address=X.X.X.Y/24 interface=vlan210_MGMT network=X.X.X.0 { IP address of cap on Management network - static DCHP lease on Router }
add address=192.168.55.1/24 interface=offbridge network=192.168.55.0 { address of off bridge access }
/ip dns
set allow-remote-requests=yes servers=X.X.X.1 { Note: Done so all dns requests use trusted subnet }
/ip route
add dst-address=0.0.0.0/0 gateway=X.X.X.1 comment=“ensures route avail through trusted subnet gateway”
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=management
As you can see once you get this down and working, configuration of the other two caps is clean and fast.
The only thing that really changes is the IP address of the cap itself and of course any other changes to the wifi each cap puts out.
Ok, I understand that this is practically the most common configuration omitting capsman.
I don’t have a problem with the above, although I mostly made bridges.
I have a problem as I wrote with capsman on ROS 7 and cap ax accesspoints
Maybe I’ll start from the beginning.
I have a CRS router and 3 CAP AX access points connected to it.
The wifiwave2 package is required to control the CAP AX. Unfortunately, I can’t install it on my router because the router doesn’t have enough memory.
I would like to run capsman on one of the accesspoints and connect the rest to it. I need to create several networks operating in the 2GHZ/5GHZ band ( SSID2G:WORK, SSID5G:WORK, SSI2G:GUEST, SSID5G:GUEST)
I want to use capsman to manage channels and roaming like in ROS6
All devices updated to ROS 7.10
