Thanks for the reply. How do I share the config ?I have it working, but in my case it isn't an ax3, but instead an RB4011 and an Audience. Share your config.
From the command line run: /exportThanks for the reply. How do I share the config ?
I would like to see that also. Actually,, I don't understand why Mikrotik doesn't address this as well in their Wiki.And would you mind sharing that info for others ?
/system reset-configuration no-defaults=yes
Internet ----------ETH1- Mikrotik CAPSMAN - ETH2 --------------- ETH1 - Mikrotik CAP
Really?What are you quotiing whole preceding post for? Does it help answering? Use "Post Reply" button. When you talk to somone do you repeat what was said before answering?
# jan/20/2023 20:51:47 by RouterOS 7.8beta2
# software id = KVAM-7GMC
/interface wifiwave2
# managed by CAPsMAN
set [ find default-name=wifi1 ] configuration.manager=capsman-or-local .mode=ap disabled=no
# managed by CAPsMAN
set [ find default-name=wifi2 ] configuration.manager=capsman-or-local .mode=ap disabled=no
/interface wifiwave2 security
add authentication-types=wpa2-psk,wpa3-psk name=sec1
/interface wifiwave2 configuration
add channel.skip-dfs-channels=all country=Latvia name=5ghz security=sec1 ssid=CAPsMAN_5
add country=Latvia name=2ghz security=sec1 ssid=CAPsMAN2
add country=Latvia name=5ghz_v security=sec1 ssid=CAPsMAN5_v
/interface wifiwave2 cap
set caps-man-addresses=127.0.0.1 discovery-interfaces=bridge_LV enabled=yes
/interface wifiwave2 capsman
set ca-certificate=auto enabled=yes package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled disabled=no master-configuration=2ghz radio-mac=00:00:00:00:00:00 supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration=5ghz radio-mac=00:00:00:00:00:00 slave-configurations=5ghz_v supported-bands=5ghz-ac
/interface/wifiwave2/capsman> print
enabled: yes
ca-certificate: auto
require-peer-certificate: no
package-path:
upgrade-policy: none
generated-ca-certificate: CAPsMAN-CA-18FD74FE92C0
generated-certificate: CAPsMAN-18FD74FE92C0
/interface/wifiwave2/capsman/remote-cap> print
Columns: ADDRESS, IDENTITY, STATE, BOARD-NAME, VERSION
# ADDRESS IDENTITY STATE BOARD-NAME VERSION
0 127.0.0.1 ax3 Ok C53UiG+5HPaxD2HPaxD 7.8beta2
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
/interface/wifiwave2/capsman/remote-cap> print
Columns: ADDRESS, IDENTITY, STATE, BOARD-NAME, VERSION
# ADDRESS IDENTITY STATE BOARD-NAME VERSION
0 MikroTik Ok RBD53iG-5HacD2HnD 7.7
1 127.0.0.1 ax3 Ok C53UiG+5HPaxD2HPaxD 7.8beta2
/interface/wifiwave2> print
Flags: M - MASTER; B - BOUND; I, R - RUNNING
Columns: NAME, CONFIGURATION.MODE
# NAME CONFIGURATION.MODE
;;; managed by CAPsMAN
0 MBI wifi1--2Ghz ap
;;; managed by CAPsMAN
1 MBI wifi2-5Ghz ap
AFAIK there will be no capsman forwarding.I really hope they'll add support for capsman forwarding in the next release, not the best solution to add vxlan/eoip everywhere and bridge cap interfaces locally
# feb/10/2023 17:28:23 by RouterOS 7.8rc1
# software id = KVAM-7GMC
#
# model = C53UiG+5HPaxD2HPaxD
/interface wifiwave2 datapath
add bridge=bridge_ disabled=no name=datapath_1
add bridge=bridge_ disabled=no name=datapath_10 vlan-id=10
/interface wifiwave2 security
add authentication-types=wpa2-psk disabled=no encryption="" ft=yes name=sec1
/interface wifiwave2 configuration
add channel.skip-dfs-channels=all country=Latvia datapath=datapath_1 disabled=no name=conf_1 security=sec1 security.ft=yes ssid=Aaaa
add channel.skip-dfs-channels=all country=Latvia datapath=datapath_10 disabled=no name=conf_10 security=sec1 security.ft=yes ssid=Aaaa_10
/interface wifiwave2 capsman
set enabled=yes package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled master-configuration=conf_1 slave-configurations=conf_10
# feb/10/2023 17:32:24 by RouterOS 7.8rc1
# software id = WYZC-DIZ1
#
# model = RBD53iG-5HacD2HnD
/interface bridge
add name=bridge1
/interface wifiwave2
# managed by CAPsMAN
# mode: AP, SSID: Aaaa, channel: 2427/n/Ce
set [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap disabled=no
# managed by CAPsMAN
# mode: AP, SSID: Aaaa, channel: 5240/ac/eeeC
set [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap disabled=no
/interface bridge port
add bridge=bridge1 interface=all
/interface wifiwave2 cap
set discovery-interfaces=bridge1 enabled=yes
Does this mean I need one physical device which acts as capsman for legacy wireless and one device as wifiwave2-capsman?The wifiwave2 package can be installed on some products, which ship with the bundled 'wireless' package, replacing it.
Installing the wifiwave2 package disables other means of configuring wireless interfaces. Before installation, make sure to back up any wireless and regular CAPsMAN configuration you may want to retain.
Magic mushrooms for lunch??But crowds (myself included) are thrilled by such a possibility and some even consider it "almost done".
Not needless and well appreciated!!I know, this answer is needless, but this situation is ridiculous.
/interface wifiwave2 channel
add frequency= name=silent
/interface wifiwave2 datapath
add bridge=BR-Casa disabled=no name=Wifi_Main
add bridge=BR-Mamma disabled=no name=Wifi_Mamma
add bridge=BR-Guest disabled=no name=Wifi_Guest
/interface wifiwave2 security
add authentication-types=wpa2-psk name=home
add authentication-types=wpa2-psk disabled=no name=guest
add authentication-types=wpa2-psk name=silent
/interface wifiwave2 configuration
add country=Italy datapath=Wifi_Main datapath.bridge=BR-Casa disabled=no name=home security=home ssid=
add country=Italy datapath=Wifi_Guest datapath.bridge=BR-Guest disabled=no name=guest security=guest ssid=
add channel=silent country=Italy datapath=Wifi_Mamma datapath.bridge=BR-Mamma disabled=no hide-ssid=yes name=silent security=silent ssid=
/interface wifiwave2 capsman
set enabled=yes package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled disabled=no master-configuration=home slave-configurations=guest
add action=create-dynamic-enabled disabled=no master-configuration=home radio-mac= slave-configurations=guest
add action=create-dynamic-enabled disabled=no master-configuration=home radio-mac= slave-configurations=guest,silent
/interface bridge
add name=bridge1
/interface wifiwave2
# managed by CAPsMAN
# mode: AP, SSID: , channel: 5680/ax/eCee
set [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap \
disabled=no
# managed by CAPsMAN
# mode: AP, SSID: , channel: 2462/ax/eC
set [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap \
disabled=no
/interface list
add name=WAN
add name=LAN
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wifi1
add bridge=bridge1 interface=wifi2
/interface list member
add interface=bridge1 list=LAN
/interface wifiwave2 cap
set discovery-interfaces=bridge1 enabled=yes
/ip address
add address=192.168.0.4/24 interface=bridge1 network=192.168.0.0
add address=192.168.0.4/24 interface=ether1 network=192.168.0.0
/ip dhcp-client
add disabled=yes interface=ether1
# DHCP client can not run on slave or passthrough interface!
add interface=ether1
/system clock
set time-zone-name=Europe/Rome
/system identity
set name="AP"
Is this temporary, while missing functionality will be added or it will be "Lost functionality"?Unfortunately, vlan-id is supported only on 802.11ax interfaces. Documentation has been adjusted.
same question here! Will this be released one day, or is it a permanent hardware limitation?Is this temporary, while missing functionality will be added or it will be "Lost functionality"?Unfortunately, vlan-id is supported only on 802.11ax interfaces. Documentation has been adjusted.
And how you suggest to set up Guest network on hap ac3 wave2 with Caps-man?
It's indeed unbelievably frustrating. Lost a good day on this trying to migrate a CAPsMANv1 setup to wifiwave2, before it was documented. Right, it should be considered alpha-stage so it is to be expected maybe. But I think the limitations should be made quite a bit more explicit still, under the wifiwave2 compatibility section, instead of expecting potential buyers or upgraders to sift through every parameter to see which features are not supported. An unqualified listing of e.g. Audience to me suggests full compatibility, especially given such a limitation is listed for the RB4011iGS+5HacQ2HnD.Unfortunately, vlan-id is supported only on 802.11ax interfaces. Documentation has been adjusted.
- https://mikrotik.com/product/hap_ax2Like the previous models, hAP ax² can be mounted vertically, horizontally, or even on the wall
Summary: RoS combined with crappy wifi/wifi wave2package is an INSULTINGLY poor companion to the fabulous RoS and pushes clients towards other solutions.
Trying to follow along with this on a RouterOS CHR virtual machine as the CAPsMAN for two hAP AX3 caps.Copied relevant sections of the export
CAPSMAN
====================
...
/interface wifiwave2
add configuration=2gConfig configuration.mode=ap disabled=no name=cap-wifi-2g
add configuration=5gConfig configuration.mode=ap disabled=no name=cap-wifi-5g
Script Error: action cancelled
input does not match any value of master-interface