Hi@bigal_12ms，

Yes, you will lose all settings, because the controller will erase all settings once it adopts your devices. It is recommended that you can do the pre-configure on the Controller, and then connect all devices.

How to configure Multi-Networks & Multi-SSIDs on Omada SDN Controller

Essence Posts Summary — Omada Configuration Videos

  @bigal_12ms 

It's not that crazy, but you will have to manually replicate in the Pfsense what the controller would have configured in a managed TPlink router.  In your case it's the other way around, based on your config of the Pfsense router, you need to build a mirror image of that in the controller, so you define all your subnets, all your VLANs, ACLs etc.  However, you can ignore the WAN settings, the DHCP and IP reservations, port forwarding/DMZ, etc that would get pushed to the Omada router's config.  In short, you just need enough base config in order to re-establish your current functionality in your Omada switches and APs.  Going forwards, if you make a change, say to add an SSID and subnet/VLAN, you will need to do that in both the controller and on your Pfsense.

  @bigal_12ms 

You can adopt 1 device at a time.  So you can 'test' your overall config on less critical parts of your infrastructure first and work your way up to the main distribution switch.  Personally I'd start out with a single AP and see if it performs the same after adoption as it did in standalone (this will test your config of LAN subnets and assigned VLAN, as well as your SSID definition and VLAN mappings).  You may want to read up on 'Management VLANs', but at least understand the default mgmt vlan is 1, so don't use that for other services/subnets.

If you are super paranoid, you can take a standalone backup each device before you adopt it :)

  @bigal_12ms 

A firmware update would reset the AP to it's default state.  Did you backup and then restore each APs config?  Is your controller on a 192.168.0.X/24 subnet...because that is where all the firmware updated APs will be.

  @bigal_12ms 

The default for the Management VLAN is untagged and belonging to subnet 192.168.0.0/24.  You need to make sure that the switch ports that the OC200 and APs are connected to are members of VLAN 1 and that their PVID is VLAN 1 (ie VLAN 1 is untagged on those ports), and for the AP ports, you want to make sure that they are also members of VLAN 50 and VLAN 100 (tagged).

When debugging, I typically plug my laptop into one of the OC200 ports and use the other port to connect it to the upstream switch or router.  I then validate what IP my laptop has and what IP the controller gets.  Then I try to reach the device I would like to managed...first determine its IP (pfsense list of connected devices?) and then if I can reach it via ping.  If the IP of the controller is different from the AP, then I need to change the PVID of the AP switchport to be the same as that of the controller.