HofkoSK wrote

Hello,

 

in iOS Omada app I've block device to connect internet and after unblock device can't get IP address from DHCP. I can't reach any settings from Omada web gui to allow device work correctly. Device Omada takes as unlocked. Is there any solution for this problem? I have snapshot of OC server, but the recovery this way is not correct.

 

It's insane when I need block device temporary blocked and I'm pushed the button and it's permanently. Button does not inform about this, firewall policies are hidden...

 

Tested scenarios:

- device is in Omada not blocked

- delete and add new entry is not working

- if I plug to same cable another device everything working fine

- when I connect device to another DHCP server, device get IP address correctly and connect to internet correctly too

- if I plug cable from Omada, device get address 169.254.82.0 with mask 255.255.0.0 and GW 0.0.0.0

- when I set up IP correct settings manually, can't reach network, router and internet

 

Thanks a lot.

Hi  @HofkoSK ,

I just had a test on my end, but can't see the same issue.

- So I have a device is in Omada not blocked;

-On the APP, login the controller-->Clients-->find the devices and hit BLOCK. 

-The device can't connect the network now;

-Then I go to Clients--Blocked list, release the device;

-Device can connect the network again without issue

Could you please check if you are loging the controller via Cloud? (via Internet) Or you are on the local access to the controller?

I suspect the function is working, but if you are login via Internet, there could be some lagging.

  @Hank21 thanks for your test, but it's not same. If I block/unblock device from WEB GUI, everything works fine. When I block device from my iPhone Omada app and unblock from WEB GUI I get addres from 169.254.82.0 and device is not in my DHCP defined range. Omada on iPhone show device unblocked too, but is not working.

I never seen same behavior on other producers and I think device is still blocked by FW to reach DHCP or internet, because when I set up device manualy, device can't connect to other device or router or internet. Same device via WiFi work fine. Its a controller problem or router problem. Config is in my signature.