So what I did was just change the wireless networks to Separate Zones, created new DHCP for those zones and added the Interfaces and added the VLAN tag.
Problem is, now that you try to connect to them you can't pull DHCP.
I have the DHCP live log up, the firewall log, and wifi but not seeing any indication it's even trying to get a new IP.
Some things have changed. After working with tech support it seems if the wlan # interfaces are set to Ethernet VLAN, the wireless networks will not pull DHCP. Once I take it off and just do Ethernet Static they'll get DHCP just fine.
There is a cable from eth0 tagging 40-41, 45-46. Does the wlan# interface know to tag on that interface?
Also, the ports the AP's are plugged into are just set to untagged 40 and access port.
Hi, the WLANs will be tagged with whichever VLAN you assign to them.
If you want a WLAN to share a VLAN, you need to use the 'bridge to VLAN' option when creating the wireless network. If they are bridged, a single DHCP service in the UTM will work on both the wired and wireless networks. If you are not using the UTM for DHCP, things may be more complicated.
The thing is, I did have them set to Bridge to VLAN before and the problem was DHCP wasn't working properly. There is a bug though they said that when you click on Wireless Networks the IP could show wrong.
It worked before when I did Bridge to VLAN. What I might do is set the Guest Wireless to a VLAN and change the other two wifi networks back. I shouldn't need to tag anything on the actually switch port that the AP is plugged into or the AP itself. I'm assuming that the controller will handle all of that.
I had to revert everything back. Wifi quit working all together.
Deleted the WLAN interfaces (even for Guest) and they are all using eth0 now. Setup the AP ports for trunking and wireless started working. Still can't get an answer why I'm having such issues from support.
Even tried it on my UTM120. Same thing. If the wlan# interface is set to Ethernet VLAN, client will authenticate, but not get an address.
If I make the wireless network bridge to VLAN ID and then create an Ethernet VLAN interface and have it use eth0 as the hardware, just like the other networks use. Client pulls DHCP just fine.
You mentioned the WLAN's will be tagged whatever interface you give them.
So you can't use the wlan# interfaces at all if you want to do VLAN tagging. You have to basically create a wireless network and to Bridge to VLAN and then create an interface that is tied to a physical NIC on the UTM.
