Your AP's are on swconfig, so /etc/config/network should look something like below. Of course, this is your 1st AP assigned to static IP 10.10.10.2 (your RT3200 is 10.10.10.1 in prior example). Your second AP needs to be 10.10.10.3, etc.
On my AP, port 6 is the CPU for the lan port(s) and port 0 is the CPU for the wan port; hence you'll see these ports tagged with every lan or wan port, respectively. You'll need to evaluate your device's setup and adjust accordingly if different.
Notice I've disabled startup of the wan interfaces (option auto '0') - this is a dumb AP, so we don't want those running. The wan is on VLAN 2. The lan, importantly, is on vlan 1, same as on your RT3200 in the previous post. And the same VLAN id's need to be used for IOT1 IOT2 and GST (10, 20, 30) too.
Notice all the VLANs are coming in tagged to port 1 (except your lan, which comes down the wire untagged as I've set things up). This is the AP lan port the Ethernet cable from your RT3200 is assumed to be plugged into. I've assumed port 2 is assigned to the wan on your AP. Now that I think about it, it's probably the reverse, but I don't have your device, so adjust accordingly.
Notice I'm assigning the vlan id's manually with:
option vid '10'
etc., instead of relying on it defaulting to a sequential number (which in this case does not match the vid on your RT3200 and would be a problem - the vid's must match up across your network!) as used in
option vlan '3'
Probably your AP's are new enough that this isn't a necessary habit, but older fast Ethernet chips will only accept values up to 16 or 128 for option vlan 'n'. Certainly your RT3200 is new enough, so I didn't bother with this for the RT3200 and just used, for example, option vlan '30' for vid '30', without specifying the vid explicitly. You can probably do the same on your AP's.
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fda6:1d4a:a73c::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1.1'
config device
option name 'eth1.1'
option macaddr 'c0:56:27:xx:xx:xx'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '10.10.10.2'
option gateway '10.10.10.1'
option netmask '255.255.255.0'
option ip6assign '60'
config device
option name 'eth0.2'
option macaddr 'c0:56:27:xx:xx:xx'
config interface 'wan'
option device 'eth0.2'
option proto 'dhcp'
option auto '0'
config interface 'wan6'
option device 'eth0.2'
option proto 'dhcpv6'
option auto '0'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '1 6t'
option vid '1'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '2 0t'
option vid '2'
config switch_vlan
option device 'switch0'
option vlan '3'
option ports '1t 6t'
option vid '10'
config switch_vlan
option device 'switch0'
option vlan '4'
option ports '1t 6t'
option vid '20'
config switch_vlan
option device 'switch0'
option vlan '5'
option ports '1t 6t'
option vid '30'
config interface 'IO1'
option proto 'dhcp'
option device 'br-IO1'
config interface 'IO2'
option proto 'dhcp'
option device 'br-IO2'
config interface 'GST'
option proto 'dhcp'
option device 'br-GST'
config device
option name 'br-IO1'
option type 'bridge'
list ports 'eth1.10'
config device
option name 'br-IO2'
option type 'bridge'
list ports 'eth1.20'
config device
option name 'br-GST'
option type 'bridge'
list ports 'eth1.30'
in /etc/config/dhcp, add
option ignore '1'
under the lan dhcp server - you don't want another dhcp server assigning ip addresses on your home network lan from every dumb AP. And of course, don't set up dhcp servers for your other vlans on your AP's. You've already got them on your RT3200.
Finally, set up your wireless. This should be easy enough to do in LuCI. Set up an interface for each SSID (home, IOT1, IOT2 - whatever you want to call them) and select the network that wifi interface should be attached to (lan, IO1, IO2, GST should be available as drop downs ).
I include the same firewall setup on my AP's as on my main router for consistency (there is no difference between swconfig and DSA here), and I leave firewall running (I do not disable firewall on my AP's). It shouldn't' be necessary, and it's wasted resources - a dumb AP shouldn't need a firewall running on it. But it's there as a template if I ever use them for something other than a dumb AP.
Good luck!
.
)