Hi everyone.

I do have a question and I belong you'll be able to help me. But first, I wanna apologyse for my english, I'm french, so sorry for the mistakes

So, I do work for a company and I'm working on the OMADA software controler. The goal I have to reach is to be able to manage all the APs of the company on the OMADA controller.

Right now, I'm working on a local area with only, the controler installed on a computer with a Windows Server, 1 EAP 225-Outdoor, a HP switch and a computer to manage the switch.

My computer, the AP and the controler are in the same network, plugged on 3 untagged ports and their gateway is the adress of a VLAN from the HP switch. So nothing looking wrong on this part.

But, we all know that if I'm here, I have a problem.

So, my devices are in the same network, everyone can ping everyone, etc

But, I want my AP to share a different network from the one it's connected on. Here is an example, my AP has an IP address looking like 10.50.100.0 / 24 -- I want it to share an IP address from the 192.168.10.0 / 24 network.

I created a network on my controler in Settings --> LAN named Broadcast (it is the network I want to share) with the VLAN 10 and a WiFi SSID (with the same name than my LAN) linked to the VLAN 10 to. This SSID is share by my AP but I don't get an IP address from it. At this point, the AP doesn't share anything but an APIPA address (169.254.0.0 / 16).
 

Question :

- Does my controler need a different IP address that the one of the computer or this it takes the same to work ?

- Is the controler able to act like a DHCP server (it seems obvious to me that the configuration I did is here for this but maybe I'm wrong) or do I need a router (which I don't have rn) to be the DHCP server ?

- Can I use my HP switch for the solution or do I MUST have TP-Link switches and routers ?

- Do I have to tag anything on my switch ?

I think that is all I need rn, I hope someone, will understand my situation and be able to help me with it.

I wish you all a good day.

Thanks