Tagged VLAN Issues (update: solved)
Hey all, I am having trouble with tagged traffic going out three EAP245 APs. I have left two unplugged for troubleshooting purposes so we'll just say its one for now. Trunked back to a PoE port on a TL-SG1016PE with three VLANs tagged and in addition management is tagged as well. Essentially trunked across the board (which I like compared to other managed APs that cannot tag management). I was tearing my hair out all week trying to figure out why I could not ping the gateway and must have checked config on the router, switch and Omada twenty times. My phone receives DHCP through the tagged VLANs but my laptop does not and actually has trouble even connecting. I have finally concluded that there is an issue with the tagged traffic and EAP245 because when I set an untagged port into the three VLANs (one per port) and a wired connection, there is zero trouble communicating with the gateway, DNS, internet, and (for now until implementing firewall rules), other VLANs. Along with this, I deleted all SSIDs and created one that is untagged on one VLAN (with Switchport untagged and PVID to match) and it works that way as well. Finally, tagged VLANs have no trouble passing to a second managed switch. There are not any controls in Omadas interface for say messing with ingress/egress so I am wondering if anyone has run into this before. I really want to stick with the EAP245. Any ideas?