Since then (after following the advice on the thread) I moved away from capsman frowarding and it seems that roaming works ok even without it
. Other things happened and i shelved migrating for a while.
I've been testing the migration of the access points and I found that after creating a slave wifi profile with the same settings as the master, the slave profile is inaccessible while the master is accessible.
I performed a pretty simple setup - here is the setup - Capsman is running on a chr that sends the setup to a capax.
Any suggestions?/interface wifi datapath
add disabled=no name=guest vlan-id=1000
/interface wifi configuration
add country=Romania datapath=guest disabled=no name=2ghz security=guest ssid=\
test-2g
add country=Romania datapath=guest disabled=no name=5ghz security=guest ssid=\
test-5g
add country=Romania datapath=guest disabled=no name=test1 security=guest \
ssid=test
/interface wifi cap
set discovery-interfaces=admin enabled=yes
/interface wifi capsman
set ca-certificate=auto enabled=yes interfaces=admin package-path="" \
require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=5ghz \
name-format="" slave-configurations=test1 supported-bands=\
5ghz-n,5ghz-a,5ghz-ax
add action=create-dynamic-enabled disabled=no master-configuration=2ghz \
supported-bands=2ghz-n,2ghz-ax,2ghz-g
LE: I tried the same setup - but without a caps - and the same happens