I wanted a normal SSID and a Hidden SSID for IOT Devices. When I use on both networks the same datapath with forward then I don’t get a ip from dhcp.
I created then a new datapath with the same bridge interface and forward. This didn’t work either, now i had to disable the datapath on the dp-wifi so it works.
I have 5 AP they all are configured to use CAPSMAN. I have one SSID “STANDARD” for all Mobiles etc.
Now I wanted a slave SSID “IOTDevice” for my IOT devices, with a different passwort, so that when i need to change the password on Stnadard i don’t have to change all IOT devices.
Then I used the same Datapath on the IOTDevice SSID
name=“dp-lan” client-to-client-forwarding=yes bridge=br-lan local-forwarding=yes
And I got no IP from DHCP…i found out when I make a new datapath without forwarding it works on the slave. Tough when I turn of on the SSID Standard, my AP can’t connect anymore to CAPSMAN..they come and go.
…I’d use a different VLAN for each SSID. Works for me on the same datapath/bridge…the setting is done in CAPsMAN → Configuration for each SSID.
Each VLAN needs to be set-up in the main Router (and/or switches) as well, of course.
As my iot devices are on 2.4ghz network and I use 5ghz for, basicaly, everything else I have setup vlans whit the same ssid. Then I isolated2.4ghz network, so no China can spy my stuff.