@Clive_A 

 

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 ???

  @Clive_A 

 

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

  @Clive_A 

 

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.

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

That's not the problem. When you use OC200 in LAN configuration, there is an option to configure DHCP. OC200 is not capable of acting as a DHCP server so, why to leave this option in this device. This firmware or Omada software was not clear. The option of DHCP should appear when, in your device list, you have a switch or router capable of doing this role

  @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.

It's like i talk to a wall. Please dont reply anymore. I work actively since 3 years with english people (usa in particular) and you dont have the same thinking than european people. So please admin close that thread.