"lock to ap" does it work?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions."lock to ap" does it work?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi
I recently upgraded my Omada Controller to v5.9.9.
I have enabled "lock to ap" on some of my devices.
However, one of the device that is locked to an EAP110 v4, has already connected to a different access point. Any idea why this is happening?
I have the following devices on my network:
EAP 225 (US) v3.0, firmware 5.0.9
EAP 265 HD (US) v1.0, firmware 5.0.6
EAP 110 (EU) v4.0, firmware 5.0.4
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi All,
We have released some EAP Beta Firmware which has added the PPSK, Lock to AP, 802.11r fast roaming, and a number of new features, you may subscribe to this post for more latest firmware information.
All feedback is welcome, including lettings we know about successful device upgrades and you may post a new thread here or comment here.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@KimcheeGUN oh right, didn't realise we needed to wait for firmware for that to work. That's a shame.
- Copy Link
- Report Inappropriate Content
This will be a great feature, especially for some IoT devices that don't roam as well as other newer, more modern Wifi-capable clients. Is there any indication as to when new firmware will be released to support this feature?
Note that in order for this feature to work, once the AP device firmware supports it, the client will likely need to be disconnected (or powered off) and reconnected in order to lock to a specific EAP.
- Copy Link
- Report Inappropriate Content
Same problem with EAP650(US) v1.0 and EAP670(US) v1.0 with firmware 1.0.6
Lock to AP NOT WORKING
HOPE TP LINK WILL FIX IT ON NEXT FIRMWARE.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Nitin-Lohchab Ok..., that explains a lot of things..., so if I understand this right, the option is there on the controller BUT, it needs to be there on the device firmware also, which hasn't been done yet. I have 4 access points :
- EAP225 v3 running 5.05 firmware
- EAP670 v1 running 1.0.6 firmware
- EAP225-Outdoor v1 running 5.0.5 firmware
- EAP225-Outdoor v3 running 5.1.0 firmware
And I have a Shark vacuum 3 feet right under my EAP670 that is locked to that EAP670, but it keeps connecting to my EAP225-Outdoor with a signal of -80 dBm..., weird....
- Copy Link
- Report Inappropriate Content
Hi All,
We have released some EAP Beta Firmware which has added the PPSK, Lock to AP, 802.11r fast roaming, and a number of new features, you may subscribe to this post for more latest firmware information.
All feedback is welcome, including lettings we know about successful device upgrades and you may post a new thread here or comment here.
- Copy Link
- Report Inappropriate Content
I'm on software controller version 5.12.2 with an er605 v2.0 on firmware 2.2.0, an eap610 v2.0 on firmware 1.0.2, and 2x eap670 v1.0 on firmware 1.0.6.
i tried enabling lock to ap on all of my iot devices, but they're still moving to different APs.
should i be downgrading to 5.9.31? I can't even find 5.12.2 on the website now?
- Copy Link
- Report Inappropriate Content
Hello @Strikingviking2,
We have released the Beta firmware which added support for the "Lock To AP" feature for EAP610 v2 and EAP670 v1, please refer to this post for more details.
- Copy Link
- Report Inappropriate Content
i updated my EAP610's to this firmware and two of them refused to allow clients to connect. was this a known issue? i had to revert my firmware back.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 4779
Replies: 13
Voters 1
