@nasheayahu 

how on earth is anyone going to be able to help you with this information. you have a pfsence and eap and an omada controller, ok. you have created vlan on the omda controller you say. vlan must be created on your router, not the omada controller. then you have to create vlan on whatevers switches you have. 

  @MR.S "you have created vlan on the omda controller you say." No! Let me clarify, VLANs are created by pfSense, and I use the NETGEAR 8-Port Smart Managed Plus Switch for trunking.  I don't use Omada for nothing except controlling wireless connections.

  @nasheayahu 

but then I don't understand why you are on the TP-Link forum when you don't have TP-Link products. dhcp vlan which is controlled by pfsence and netgear is in my opinion the main problem with your setup.

and the omada controller runs on linux and does not get an updated ip.
IP on linux has nothing to do with the Omada controller settings.

You set the IP on linux in the linux setup if it does not get an ip from dhcp,
dhcp is controlled by your router.

ipconfig on linux you can usually find in a folder in this area on the linux server /etc/netplan
edit ip here if necessary.

It would be easier if you could show a screenshot of your problem. but to me it sounds like you are in the wrong forum.

  @MR.S Move me to the correct forum, you have me confused......

  @nasheayahu 

I cant move you to another forum :-)

but from what you write it sounds like you need help with pfsence or netgear. and omada controller is on a linux platform with wrong ip. have you checked the ip on your linux server? Does it have a fixed ip or does it get an ip from dhcp?

i gave you a hint where to look on linux server to see if you have fixed or dynamic ip on it, have you checked that?

there is no place to change the ip on the omada controller, it must be done on the server

  @nasheayahu As the other poster noted, more information about your setup would be helpful.  For example, what's the VLAN config of the ports where the controller, EAP and pfsense are connected?  Can you connect to the EAP in standalone mode and is the controller and EAP in the same network?

I have a similar config and it can work.  The controller and the eap should be in the same VLAN (network).  I set the controllers VLAN at the switch port's PVID.  For the EAP, the management VLAN needs to be set to match the controller and the Layer-3 Accessibility option enabled.  It's been a while, but as I recall, I got the EAP working on the network in standalone mode first, adopted it and then updated the VLAN/Layer-3 settings because it's reset to the defaults during adoption.

This article may also help: How to configure Management VLAN