I am new to the forum, in general I am new to MikroTik devices, specifically I have 2 devices: 1 chatoux ax 5g, 1 CAP ax. both devices are positioned indoors, the chatoux configuration was challenging considering that I had never used ROS, but I managed to make everything work. when I added the CAP ax, I realized that the Wifi configuration applied to chatoux was perhaps not the right one. I redid both configurations again, CAP ax is now connected correctly and everything works but with some limitations and 1 problem. on chatoux multiple SSIDs are configured, each SSID has its own vlan id with dhcp server, I am still experimenting before making the whole environment productive. every time I disable/enable cap in the Wi-Fi interface on CAP ax, the virtual interfaces change name progressively. wifi3 and wifi4 disappear, becoming wifi5 and wifi6, w7 and w8, w9 and w10, and we continue to increase every time the cap is used. the network still works correctly apart from some decrease in throughput. the other problem is that the virtual interfaces on chatoux are many more, but only 1 and 2 are imported from the CAP ax the others are ignored. for ease I will report both configurations so as to have some useful advice from you, my final goal is to have total coverage of the house for both mobile and fixed devices, I need total coverage for IoT devices (n.17) with a dedicated network, for the most part the devices use 2.4ghz -n but some could also use 5g. the second network is made up of 6 devices all are 5g ax and ac, in a guest network that do not communicate with each other (3 Smart TV + 3 iphone/ipad). the third network will be a Wi-Fi access point to chatoux ax and cap ax without using eth1. network n.4 will be intended for a desktop PC, a notebook and a printer, all in Wi-Fi. a network n.5 will still have to be implemented to host a mini PC with proxmox and several VM's but this will be on eth4 port. the eth5 port on chatoux is 2.5g, I would like to use it in the future for an incoming WAN with Ftth and failover system on LTE interface, but this will come later.
I apologize for the setup a bit messed up, I'll do a clean setup when everything works properly

Why 3 bridges?
Why 7 VLANs?
Why 15 pools?
Why 16 wifi configuration profiles?

You should start with cleaning up the clutter...

Why 3 bridges?
Why 7 VLANs?
Why 15 pools?
Why 16 wifi configuration profiles?

You should start with cleaning up the clutter...

yes i need to clean it, i just explored different configuration possibilities to learn ROS features faster, could this be the cause of the two problems i am having?

Solved all the problem, the Static Slaves setting in the CAP of my cap ax had to be enabled, I can add n vlans and multiple ssids now without problems, even the bandwidth problem seems to be solved. I'll still post my cleaned up configuration and with some screenshots, if it can help someone who needs this.

UPDATE: everything works... except my vlan 103 on the CAP ax, this still doesn't work

Much better now, good job!

CAPsMAN
you have misconfiguration on wifi2 interface datapath.bridge=*5B should be datapath.bridge=bridge

This shouldn't be needed, bridge port will be added dynamically (that's why you are setting datapath.bridge)


CAP
You don't have datapath (or datapath.bridge) set on both master interfaces.
You don't need to use slaves-static, you had that in the first config and I wanted to know why...

Same as before, bridge port will be added dynamically, but in this case you are missing the datapath.bridge on both wifi interfaces.

As you are hinted, remove dhcp client for ether1

Much better now, good job!

CAPsMAN
you have misconfiguration on wifi2 interface

Code: Select all

/interface wifi
set [ find default-name=wifi2 ] channel.frequency=2412-2472 \
    .skip-dfs-channels=10min-cac configuration=cfg-2-phy-ax \
    configuration.hide-ssid=no .manager=local .mode=ap .ssid=wifi6-dom \
    datapath.bridge=*5B .interface-list=dynamic .vlan-id=101 disabled=no \
    interworking.network-type=private security=sec-dom \
    security.authentication-types=wpa2-psk .ft=yes .ft-over-ds=yes

datapath.bridge=*5B should be datapath.bridge=bridge

Code: Select all

/interface bridge port
add bridge=bridge comment=defconf interface=wifi1 pvid=101
add bridge=bridge interface=wifi2 pvid=101

This shouldn't be needed, bridge port will be added dynamically (that's why you are setting datapath.bridge)


CAP
You don't have datapath (or datapath.bridge) set on both master interfaces.
You don't need to use slaves-static, you had that in the first config and I wanted to know why...

Code: Select all

/interface bridge port
add bridge=bridge-wifi interface=wifi1 pvid=101
add bridge=bridge-wifi interface=wifi2 pvid=101

Same as before, bridge port will be added dynamically, but in this case you are missing the datapath.bridge on both wifi interfaces.

Code: Select all

/ip dhcp-client
add interface=vlan-110-mgmt
# DHCP client can not run on slave or passthrough interface!
add interface=ether1

As you are hinted, remove dhcp client for ether1

I should have adjusted the points you pointed out to me, but it still doesn't work for VLAN 103, can you check if I have done all the steps correctly?

What does it mean? Are you able to connect to the network but "internet isn't working" or you are not able to connect to the network at all?

What does it mean? Are you able to connect to the network but "internet isn't working" or you are not able to connect to the network at all?

after the changes it still is not managed wifi 5 and 6 on Chatoux via CAPsman, this does not allow CAP ax to import the configuration for wifi 3 and 4 for my vlan-103, as you can see from the photo vlan-102 works properly and routes traffic via CAPax towards Chatoux (maybe it needs to be done manually?). in the meantime my wifi 3 and 4 on Chatoux has become wifi 27 and 28 on CAPax and will continue to increase with each new connection
to be clear the problem is that my MHome SSID network on vlan-103 is not found via the CAPax, only the one on Chatoux is visible.

this does not allow CAP ax to import the configuration for wifi 3 and 4

I overlooked that, you shouldn't create wifi interfaces manually, that's CAPsMAN's job. Post fresh configs after that...