Latest Firmware Issues
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Latest Firmware Issues
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I installed the latest firmware yesterday and clients are unable to connect to the AP if the SSID does not have a VLAN set. If I select Enable VLAN and use a vlan id i have no issues. Can you please look into it?
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
When you did the upgrade, are you using an OC200 controller which still runs the older 3.1.4 code? Notes on the FW update state to use the newer controller version of 3.2.1 which has not been posted yet for the OC200. I had the same issues as you where the unit looks 100% correctly configured, yet multiple devices like the RING will not connect. When they do connect, they get a 169.254.x.x or 255.255.255.x IP address. I had to downgrade for now. Hoping that once 3.2.1 is available for the OC200 to try again.
Thank you TP-Link for launching software and identifying that you need new controller software, BUT NOT RELEASING THE SOFTWARE for the controller.
- Copy Link
- Report Inappropriate Content
JTF wrote
When you did the upgrade, are you using an OC200 controller which still runs the older 3.1.4 code? Notes on the FW update state to use the newer controller version of 3.2.1 which has not been posted yet for the OC200. I had the same issues as you where the unit looks 100% correctly configured, yet multiple devices like the RING will not connect. When they do connect, they get a 169.254.x.x or 255.255.255.x IP address. I had to downgrade for now. Hoping that once 3.2.1 is available for the OC200 to try again.
Thank you TP-Link for launching software and identifying that you need new controller software, BUT NOT RELEASING THE SOFTWARE for the controller.
I run my controller software as a docker image on my NAS. So i dont think that was the problem.
- Copy Link
- Report Inappropriate Content
@steve_togo FIOS came out with an extender which works really well everywhere in my house. I've tried it now for a few days. I'm keeping it and selling my 2 EAP225-outdoor units. anyone interested contact me...a great price.
- Copy Link
- Report Inappropriate Content
JTF wrote
Notes on the FW update state to use the newer controller version of 3.2.1 which has not been posted yet for the OC200.
Wrong. It states that Omada controller 3.2.1 is recommended, but you can use any version of Omada controller with latest firmware (and even with oldest firmware) of an EAP. I use EAP225 with firmware 2.6.0 on OC200 and on Omada software controllers from version 2.7.0 to 3.2.1. Only new features of newer firmwares yet to be introduced in newer Omada controller versions require the controller version recommended in the FW update section.
So, let's see which new controller-related features have been introduced with firmware V2.6 / V1.6:
- None
Pleaase get the facts right.
When they do connect, they get a 169.254.x.x or 255.255.255.x IP address.
So this devices don't get an IP address by your DHCP server running elsewhere. Seems like a wrong network setup unrelated to an EAP.
If you would have read all posts of this thread, you would have noticed that there was a bug in former EAP firmwares which caused untagged Ethernet frames to be sent to various SSIDs which is now fixed. If your network setup depends on a buggy behavior of the EAP firmware, it won't work anymore with latest firmware (and BTW it could have been insecure in older firmware versions depending on the particular setup).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3245
Replies: 14
Voters 0
No one has voted for it yet.