This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Problem with Tagged/Untagged port
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi.
I have a problem with my configuration.
In the network configuration "default site/parameters/wired network/Lan" i cannot setup Tagged/Untagged parameter. I explain.
My management VLAN as ID 66 and all my "WIFI" network as Other ID. So Omada controller and all EAP are on the same branch in Untagged VLAN 66
to avoid person in "Default" Vlan (generally 1) can acces Network Infrastructure
But nowhere in the omada controller configuration, you can tell port 1 is untagged.
The "LAN" profile is define in VLAN 1, but it appear to be "tagged" : if i setup DHCP in LAN config, EAP cant get IP address.
If someone at TP-Link can read this i thank it a lot.
Hi @plavielle
Thanks for posting in our business forum.
Sorry that I don't understand you very well. The fact you stated above is right.
To determine whether a port is untagged or tagged, you check the port Profile. Native VLAN = PVID and the rest of tag/untag are literal meanings.
In this picture, PVID = Guest VLAN, Untagged = Guest, Tagged = Test, and Test 2. If this profile is applied to a port, then the port works as stated.
Since you have already enabled Management VLAN(VLAN 66), why put the EAP in VLAN 1? If you want it to stay in VLAN 1, disable Management VLAN on the device config then.
I dont understand the logic of tplink configuration, but this is my config.
Omada OC200 port 1 is connected on cisco switch on untagged port in VLAN 66. If put on an another port untagged in vlan 66 on this switch an AEP225, it cannot receive dchp ip. So How can i make it works.
And if i put somewhere in VLAN 66 a dhcp server (like my firewall) EAP can get dchp address. So what is the good configuration for Omada OC200 ???
OC200-ETH1 is connected to a Cisco SG250-8 on port 8 in Acces Mode Untagged in VLAN 66
Cisco Switch port 1 is connected on Infra in Trunk Mode (without VLAN 1, not needed)
EAP225 is connected on Cisco switch Port 7. The port on cisco is Trunk with native VLAN 66
If i configure DHCP on my FIREWALL, all is ok. If i configure DHCP on OC200 = FAIL
I think SDN Software was not "well tune" for OC200. I'm going to try to mount a Win7 VM with 4 Eth (one in each vlan) to see if it's a DEV problem
Ok reson I ask is that all yout settings work only on omda routers and switches. so everything you do in wired network section is only applyed to omdad device, not to cisco or other non omda device
so you ar in wrong forum, you have to go to cisco forum or forum for you firewall.
