@Whoaru99 

I experienced a similar issue while attempting to set up a VLAN. My goal was to establish an internet connection for a device on the VLAN. To achieve this, I created the VLAN and untagged port 1, where the device was connected. I also tagged port 18, where my wireless router was connected. Under port configuration, I added port 1 to the new VLAN. I intended for the wireless router to handle NAT and set up a DHCP Relay for my Windows DHCP Server. The device on the new VLAN successfully acquired an IP address from the DHCP server. Under the L3 feature, I assigned a static IP address to the new VLAN and ensured that it was included in IPv4 routing. Despite these efforts, I was unable to ping or traceroute devices between VLANs.

Upon inspecting the wireless router’s routing table, I discovered that the new subnet was not present. I created a static route for the new subnet and refreshed the routing table. This allowed me to ping the new VLAN from devices on a different VLAN. However, devices on the new VLAN were still unable to connect to the internet. Despite my efforts, I was ultimately unsuccessful in resolving this issue.

It’s worth noting that the switch, wireless router, and DHCP server all reside on the same subnet and on the default VLAN. The new VLAN has its own subnet.

I hope this information is helpful in addressing your situation.

  @Whoaru99 

Also, looking at your diagram everything appears to be right.  It seems "dumb switches" perform better routing than "smart switches." Oh, the irony!