@mehmeh 

 

It seems the VLAN tagged data did not go though to the switch. You have all switches show "connected" on the controller right?

 

Check the Network-LAN settings, choose all the router ports if possible:

 

EDIT: BTW did you set up the legal dhcp server？ Try disable it if possible

  @mehmeh 

 

on the ER605 there are only 2 cables connected 1 to the WAN and 1 to LAN 

so I don't think it matters,  but anyway I did it and it didn't resolve the issue. 

 

 

Legal DHCP server options is not ticked for any of my 4 networks. 

 

my full network is OMADA based,  

so nothing is managed 'outside' of without omada. 

 

The mess started with updating the switches (without fault)  when I got up in the morning nothing of my IOT devices ( wifi) worked anymore. 

maybe some inactive or incosistent config got activated somehow.   

As indicated before the IOT (wired) seem to still keep working.   (I verified I could still reach the IOT device)    I just noticd my wired IOT device is on the (LAN network not on the supposedly IOT )  which is unexpected => PORT 10 of my switch has the IOT profile but in the clients page is on 'LAN'

 

Tahomalink

192.168.3.202

CONNECTED

LAN

TL-SG2218 Port 10

 

Name: Port 10

Profile:

IoT

• Profile Overrides

Profile:

IoT

 

 

so maybe its the tagging on SSID's and EAP's connectied to the switch ( all linked to the 2210MP ) 

but the port profiles have not been changes,  since this network was setup at the start ( end 2021) . 

All the Vlan's were created at that time  and I know for fact they were working. 

 

 

I alos seem to get these messages in the logs :

 

The configurations of device TL-SG2218 are different from the configurations from the controller. Go to TL-SG2218-Manage Device Page and click Force Provision to synchronize the configurations of the device with the controller.	Jan 06, 2023 11:32:41
The configurations of device TL-SG2210MP are different from the configurations from the controller. Go to TL-SG2210MP-Manage Device Page and click Force Provision to synchronize the configurations of the device with the controller.

 

 

 

 

 

  @mehmeh 

 

*bump*

 

everything is still fubared , 

Since I made the first post..... 

 

as indicated before rolling back FW's and configs ( recent and m2 or 3 months ) old didn't fix it. 

 

I repeat the only Vlan that still works is the 'main' one. 

Just to 'work' I moved some wireless clients to the 'main' network SSID  , but this is not an option for other devices like printers and IOT devices....

 

 

  @mehmeh Just some thoughts that may or may not work.

While a bit intensive, have you tried a factory reset on the OC200, and then restore with settings only to the last backup or even full hand input of settings?  Having an config mismatch issue between the switch and OC200, has me wondering if the Omada database in the OC200 has become corrupted.  TPLink has done a number of DB changes over the past year, so the potential is there.  Also how full is the OC200 memory, is it close to being full?

  @mehmeh 

 

Try disable the VLANs on the controller, and enable again. Or remove the switch from the controller(the Forget option), then re-adopt the switch.

  @mehmeh 

 

Before I try this destructive solutions.   

 

For the once of Somnus,   

IF I forgot the switch , it will get reset , but would this mean I need to configure my switch configuration ( like Port mappings  , Vlan profiles etc...) 

or do I forget and then put back an old config.   ?  or do I need to start from scratch. 

 

Because if I start to do this destructive actions,   my network might/will be heavily impacted. 

although degraded and my IOT devices not working at least by moving my  work related devices to the home network

I can telework and still connect (via VPN to my employer )  <= its it's so it doesn't care about my local network topology. 

But not having anything anymore .... that's risky during the work week. 

 

 

 

  @mehmeh 

 

This is just pure BS.   

I spend again some time to try to fix this.   

Deleted my extra Vlan's and recreated them, played with Port profiles , played with Vlan on switches  ( maybe just to trigger a correct order of saving or overwriting the invalid config somehow)

reset the switches / forget / adopt etc... 

 

The only network that still works is my main.    Vlans don't do anything it seems ,   Vlan on port don't do anything.    , Any SSID which is using a none main Vlan do no work (but the switch apperently don't care about Vlan's anymore ).    As said devices on wired connection on Vlan profiles , ignore the setting and reside on the LAN.   Clients on SSid's with a vlan attached , connect don't recieve an IP. 

 

it's mind blowing that I reported this 2 weeks back.    And the only thing I see happening is that other ppl are also reporting it. 

Anyway after today fooling around , I problably messed up so many things. 

 

 I reverted to an old backup -one that worked basically since the start- => which doesn't work  ( even though switches are FW's are rolled back)

 

The only thing that I haven't tried , to basically Factory reset every single device on my setup => so start completely from scratch.  

 

 

 

 

 

 

  @mehmeh 

 

Can someone give me a detailed 'step - per step' guide to my Vlan's up and running.

 

What needs to be done clearly , what can't be done and what needs to be redone and which actions MAY NOT be done. 

 

because resetting my Controller is for me removing ALL settings from it ?  removing Vlan's and recreating doesn't seem to work from me. 

 

this morning I installed the 'beta FW of the ER605

ER605(UN)_v1_1.2.2_Build 20230118 (Beta)

 

Router ER 605		CONNECTED	TL-R605 v1.0	1.2.2	24m 2s
		192.168.3.2	CONNECTED	TL-SG2210MP v1.0	1.0.6	7day(s) 21h 39m ...
		192.168.3.4	CONNECTED	TL-SG2218 v1.0	1.1.2	7day(s) 21h 37m ...
	APa	192.168.3.5	CONNECTED	EAP245(EU) v3.0	5.0.6	3day(s) 17h 34m ...
	AP 2	192.168.3.40	CONNECTED	EAP245(EU) v3.0	5.0.6	7day(s) 21h 38m ...

 

  @mehmeh 

 

You can back up the config file before resettings of the Controller.

 

Here is the guide about how to create the networks:

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

  @mehmeh 

 

it doesn't work for me. 

 

tonight again I have done the following ( I didn't reset any device )

- delete ACL 

- delete port profiles 

- delete Vlan's  

 

the network stuff which was left was the SSID's and the main Vlan and some other config ( fixed Ip , random schedules , etc... ) 

I then rebooted the network , I double checked all stuff was gone. 

 

I then followed  your guide to recreate the Vlan's ,  portprofiles (only to 1 port for IOT ) for testing ,   SSid's

The ONLY port I gave a Vlan profile was a wired IOT device.   all ports where on 'all' 

 

Rebooted the network 

And nothing was it its vlan.   clients do not get get Ip's

 

 

Tahomalink

CONNECTED

LAN

<removed mac  Port 10

 2nd collumn is empty since it can't get an ip

 

Port 10

Profile:

Vlan_IoT

 

• Profile Overrides

 

connecting my mac book to the SSID of the IOT ,  it fails to get an ip 

and 'auto configures' a none working one

 

MacBook <removed> 169.254.149.51 CONNECTED <removed>-IOT

 

 

so as I already removed the config , reset the switches ,  and re-adopted to get this mess sorted 

I would like to recieve a way how to get our this mess .....