Problem with Tagged/Untagged port
Problem with Tagged/Untagged port
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
So why TP-LINK let all this configuration possible if it impossible on OC200 ????
So SDN Software is not well dev/adapted for OC200. I'm going to try under Windows with multiple interface.
I Dont see the purpose off OC200 if it cannot give ip adresses via DHCP (perhaps in vlan 1, but i have to test)
And so, give me a schematic of how i have to use to make it work. Surprise me. A switch is a switch and a router is a router. Does SDN software have magic wand to configure remotely TP-LINK switch and routers ???
- Copy Link
- Report Inappropriate Content
Hi @plavielle
This is a Controller to control other devices. It does not have any ability to work/replace a router/switch. These features are open but they are not effective even if you configured them.
Purpose of the OC200 is to control a bunch of devices in a centralized manner. You configure them on the Controller and the controller applies the settings to them. SDN software is the interface you are seeing on the OC200.
It's not a router and cannot replace the function of a router. Omada controller uses proprietary protocols to control/manage Omada-compatible devices.
- Copy Link
- Report Inappropriate Content
I begin to understand. Basically i I thought that OC200 was a more "intelligent/powerfull" device. But Effectively it can control all OMADA device, but no interest in my case, because i have allready switch/routers/firewall in place.
Sorry for these multiple questions. You can suppress my question, no interest for people.
So i'm going to replace my OC200 by a win7 VM, more easy to backup and no more problem with power outage (one OC200 dead after a simple on/off).
Thanks for all
- Copy Link
- Report Inappropriate Content
Hi @plavielle
Omada controller can enable you to remotely control your devices. But this is based on either you use our Omada cloud platform or you open up the port for your VM.
If you use the cloud platform, so you gotta bind your controller to the TP-Link ID.Then they'll be linked together and give you remote access to the controller.
- Copy Link
- Report Inappropriate Content
Okay. But like you see on my diagram, i only have one OC200 and EAP225.
My major problem was i was thinking that OC200 was able to act as a DCHP server (like we can think when we go in configuration lan), but in fact no.
So if you buy just OC200, and your corporate internal IP address is not 192.168.1.xx then you cannot make wifi work.
The documentation on product was not clear and software are not device specific, so this why tplink forum is so active.
In my cas i have understand where is my problem, so i'm going to take in care each time i'm going to change something on network.
i have 12 eap225-outdoor deployed and it works relatively well.
- Copy Link
- Report Inappropriate Content
VLAN 1 is the default and can't be changed or modified. The controller uses encryption methods to talk to devices over VLAN 1. You will also notice you can't change the ports for vlan1. Consider VLAN 1 as the management port.
I would try cisco config as
switchport trunk native vlan 1
switchport trunk allowed vlan 1
Switchport mode trunk
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@plavielle The OC200 is a configuration utility, you would typically manage all the aspects of your connected hardware using the OC200/300 when you set a DHCP for a lan the DHCP lease comes from the router for example not the controller (OC200).
Typically you have to have a router attached to get cloud access.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2360
Replies: 19
Voters 0
No one has voted for it yet.