VLAN and switch config challenges

I have just set up a Cloud Gateway Ultra

  • Port 1 is on VLAN 100
  • Port 2 on VLAN 20
  • Port 3 on VLAN 30

I have 3 SSIDs, on on VLAN 100, one on 20 and one on 30

Each of the above ports is plugged into a port with corresponding VLAN on a cisco switch. Plugging a device into any ports, gets the correct IP for the VLAN that the port is in.

Of my three SSIDs the one on 100 does not give serve clients an IP address but the other two do.

The WAP s are connected to a trunked port that is configured as follows:

interface GigabitEthernet1/0/4
description UniFi AP
switchport trunk native vlan 100
switchport trunk allowed vlan 20,30,100
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpduguard disable
end

Googling, I am told this is because “Your SSID on VLAN 100 is being sent tagged, but the switch expects it untagged.” and that I should try

interface GigabitEthernet1/0/4
switchport trunk native vlan 999
switchport trunk allowed vlan 20,30,100,999

When I do that, things seem to work for a minute and then eveyting stops and the WAPs are no longer avaialble until I set the switch config back ti native vlan 100.

I very seldom play with switches so am a tad out of my depth right now. I think though there is something else I am missing but not sure what. This did work when I was using pFsense as my router.

I am not clear on the goal, do you want the each SSID to broadcast just that VLAN? If so then why allow the other VLANs? Or is the AP need a different VLAN for its management and then broadcast one of the other VLANs?

Why are you using three ports between the UCG-Ultra and the Cisco switch, one for each VLAN, instead of a trunk port allowing all three VLANs? You won’t get additional bandwidth that way, as far as I am aware the four ports that default as LAN on the UCG-Ultra are connected to an internal switch which only has a 1Gb connection to the CPU that is the real router. Same as the UDM-Pro’s topology. Anyway, you’re adding complexity when a single cable with all the VLANs is more standard.

as for what you found, yes your Google results are correct, although another way to solve this issue is to set the SSID for VLAN 100 to actually be for VLAN 1 (remove the VLAN tagging), then when the traffic hits the switch it will be translated from no-tag to VLAN 100 due to the “switchport native vlan 100” config.

1 Like

I am probably not explaining well, making it too complicated, or both. I have always done it like this i.e. Three networks, one for LAN, IoT and DMZ. Each network then has its own VLAN. On the Unifi Gateway Port 1 for LAN, Port 2 for IoT and Port 3 for DMZ.

On the cisco switch,Ports 1 (VLAN 100),3 (VLAN 20) & 5 (VLAN 30) are the uplinks to the Unifi Gateway (ports1, 2 & 3 respectively)

For the SSIDs, IoT SSID is on the IoT Network, DMZ SSID on DMZ network and LAN SSID on Lan network

The uplink to the WAP therefore needs to deal with three different networks/VLANs.

I am not sure why then the Google result did not work for me. I did try using VLAN 1 instead of 999 as I assumed that is the Native/Default network.

Ok so I got it working using (where 50 is my management)

interface GigabitEthernet1/0/4
description UniFi AP
switchport trunk native vlan 50
switchport trunk allowed vlan 20,30,50,100
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpduguard disable
end

Thanks for helping to clear my fog.

Not to go througn Tom’s videos again to secure the firewall etc :slight_smile: