Clive_A wrote

Hi @mwei 

Thanks for posting in our business forum.

I don't mean to argue with you. If you want to show me that the switch is not passing VLAN, can you wireshark it and capture frames for me? I can help you analyze it(screenshots of key info). Like I said, it does not seem to be a config issue on the switch. And other VLANs work which means the VLAN function is literally working. If VLAN is not working, then it is very likely to be a problem with the config. We rule out the config on the switch. AP supports tagged frame VLAN and multi-SSID. Then that's the DHCP server.

 

Methodology:

In your test environment, configure VLAN 10 20 30 40 50, whatsoever, set it untagged and connect your PC to the port and individually test 10 20 30 40 50 working.

If they work, then you come back and set 10 20 30 40 50 as tagged on your virtual machine/server. Connect the switch and set the port on the switch as tagged 10 20 30 40 50.

Set up port mirroring, and check VLAN based on this guide: Wireshark - VLAN capture setup

  @Clive_A 

Hi, I believe that the switch is passing the VLAN as my untagged testing worked with no issues. I can try to do the wireshark tomorrow if still needed. I did attempt to do a tcpdump when attempting to connect to the WiFi SSID for the VLAN(s) in question and it doesn't even look like DHCP request makes it over to the DHCP server somehow (nothing gets logged for the attempted connection/DHCP request). 

As for the methodology, makes sense and the first part/test works. The VLANs are tagged in my system/server but I am not sure on how to make sure the port on the switch is tagged for all the VLANs as I can only set it to one PVID and I'm assuming that PVID 1 should be meaning tagged for all VLANs? (port 1: WiFi/SSID ; port 8 gateway/router ; port 7 DHCP server):

Hi!

Please access my wireshark output from my test system that is attempting to connect to the SSID that is tagged for VLAN3 by following this google drive link as I am unable to attach to this reply:

https://drive.google.com/file/d/1DRn66DUXRf6yeYl5l3I0PBBQWHWijPOW/view?usp=drive_link

I am unable to run wireshark on the DHCP server as it is running Ubuntu Server (no GUI) but I did have /var/log/syslog up and it did not pick up any traffic or DHCP request(s) from the test system for the SSID that is tagged for VLAN3. Once the test system kept being unable to connect it automatically connected to another SSID that is tagged for VLAN40 (the wireshark should have captured that as well). 

Hoping this will maybe help shed some light on what might be happening or what I might be missing...*fingers crossed*.