Hi @GeneraalSpeknek,

Is the diagram correct? It looks like the controller is physically wired between the router and switch. If so, that would cause a lot of issues.

  @D-C 

Hey, the OC200 controller is wired to the gateway (Switch A). So it is router -> gateway -> oc200.

@GeneraalSpeknek, short answer is I think you're replacing the default vlan with the test vlan. Both need to talk between devices.  See this guide, it should help.

https://community.tp-link.com/en/business/threads/topic/664314

  @D-C 

I've checked your link, don't know where I'm going wrong. I'm using the default "All" profile:

(Test vlan is in tagged networks). This profile I set on the port going from gateway/switch A to switch B:

Next on Switch B, I want the connected device on port 2 to be on the test vlan, so it needs to get an IP within the 99.0.0.X range:

But when I save it, device loses internet connection and never gets an IP. Am I missing something in the URL you send me?

Edit 1: I also checked if all my VLAN's were enabled, they are:

Edit2: I noticed that my hardwired devices, even though they do have an IP and internet, don't show up with an IP in Omada, they do show up as connected:

Internet works fine on it whenever it stays on "default" vlan.

@GeneraalSpeknek, sorry if I'm missing it, but what's the test switch profile look like. It should have the test (99) vlan as the native vlan and untagged member.

  @D-C 

First of all I want to say, I appreciate the help thus far :).

I've checked my VLAN and it seems to be what you suggested:

Don't know if I'm missing anything else here

@GeneraalSpeknek, I do my best to help and improve my networking karma.

The device connection B-2 need so be untagged member and native network of 99.  (That you did)

Then ports along the path to the router need vlan 99 tagged.  B-1, A-2, A-(Router Port) (looks like that 's done via the All profile)

Is switch A connected to router's WAN/LAN6 physical port?

  @D-C 

Hey hey,

Switch A is indeed connected to wan/lan6 on the router. I've even tried marking all the checkboxes there.

  @GeneraalSpeknek, not sure it this would  be a problem, but the network your using is not a reserved public network address and also noticed that the DHCP range starts on the interface IP.  Can you try changing to the network address to 10.99.0.1/24, and update the DHCP range to 10.99.0.2 - 10.99.0.254?