RE220 - iOS14 Weak Security
Folks,
Since iOS14, I'm getting "Weak Security" warnings connecting to my RE220. I see there's a post in the Deco forums about a similar issue and there's a firmware update out for them (in beta). Do you have anything similar for the RE220?
https://community.tp-link.com/en/home/forum/topic/227662
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello everyone,
Here is a summary thread for Range Extender Weak security issue where you could find the latest firmware or beta firmware that fixed the problem:
[Solution] iPhone iOS14 recognizing the range extender wireless network as "weak security"
https://community.tp-link.com/en/home/forum/topic/232218?page=1
If your model is not listed, or you still experience the same issue, please leave your comment there with case details. We will look in to your inquiry as quickly as possible.
- Copy Link
- Report Inappropriate Content
Hello everyone,
Here is a summary thread for Range Extender Weak security issue where you could find the latest firmware or beta firmware that fixed the problem:
[Solution] iPhone iOS14 recognizing the range extender wireless network as "weak security"
https://community.tp-link.com/en/home/forum/topic/232218?page=1
If your model is not listed, or you still experience the same issue, please leave your comment there with case details. We will look in to your inquiry as quickly as possible.
- Copy Link
- Report Inappropriate Content
@Solla-topee My router is already configured to WPA2-Personal with AES Only. I have not changed any settings there.
The issue appears to be that since the RE220 supports TKIP, that I get that error. Clearly there needs to be a firmware update to address this.
I don't know if/how I can tell how my iOS device actually has connected to it.
Note that my RE300 seems fine.
- Copy Link
- Report Inappropriate Content
Hi All,
Seems as if this same TKIP versus AES Weak Security Issue extends across a multitude of TP-Link devices and users. Although possible in the 10s of 1000s of posts in this forum, that someone else has already reported the issue with the RE650 AC2600 WiFi Range Extender. I didn't have a week to read through them all. Besides I hope my 2 cents is worth a read by you all.
Like others, the issue with my RE650 was brought to my attention by the iOS 14 update. AES was implemented in 2002, and it was immediately known that it was superior to TKIP. So there really is no reason for any device purchased in the last decade not to support it. And since I have my ISP LAN router is set to WPA2 (AES), I know for a fact the failure is with the RE650. This also makes me think that it might be using AES to connect to the LAN, but not using AES for clients connecting to itself. This would explain why the new iOS update makes the recommendation to move to AES but still connects using TKIP. Can anybody else clarify this in some manner?
Do TP-Link representative ever jump in to clarify things for us? Not likely I suppose.
The specification sheet for RE650 (hardware version 1.0) as is my RE650, lists WPA2 as one of the supported encryption types but mentions PSK( aka TKIP). but no mention of AES. That's pretty much says it all. But when selecting hardware version 2.0, of the TP-Link download site, there is not a specification sheet available to verify if AES is implemented or not. There is only a user manual provided that does not mention AES explicitly, but however, it does indicate it will use and display whatever encryption is set by the LAN it is connected to. Which really means nothing unless someone can jump in to clarify if AES is supported. Do any of you all have a RE650 hardware version 2, and can report whether AES is being used to connect to their LAN?
There is available firmware upgrades for hardware version 1.0, but no mention of adding support for AES in their "fix" description. Do any of you RE650 ver. 1.0 owners have knowledge of AES support in the available firmware upgrades for hardware version 1.0?
If there just isn't any added firmware support for AES by TP-link for the multitude of device owners experiencing this issue, this RE650 will be the last TP-link device I, or any of my followers, will ever purchase. I wonder how many of you feel the same way.
- Copy Link
- Report Inappropriate Content
Good day.
Thank you very much for your time and patience.
Sorry for the delay.
For your RE220, may I know the current hardware and firmware version?
Is it RE220(EU)_V2_190924?
And please try to reflash the following firmware and reconfigure the RE vie web interface:
https://static.tp-link.com/2019/201911/20191129/RE220_V2_190924.zip
Since we have tested on our end, it would strictly follow the security mode of the front router;
Thank you very much.
- Copy Link
- Report Inappropriate Content
@Solla-topee I'm having the same issue on my RE220 (HW version 2.0).
I was on 1.0.3 Build 20201022 Rel. 66896, and have just flashed down to 1.0.1 Build 20190924 Rel. 45508(8583) using the bin file you provided. The same "Weak Security" message still shows in iOS 14.
- Copy Link
- Report Inappropriate Content
Hi, thank you for your patience.
As for the RE220 v2, you might need to update to the latest official firmware 1.0.3 Build 20201022 Rel. 66896 which has fixed this issue.
After that, if there is still weak security issue on the Apple devices, please refer to the following suggestions:
1. make sure the home router is WPA2-AES only;
2.reset the RE220 and set up again via the web interface, not Tether APP;
3.delete the previous wireless profile of RE220 and search for the new wireless profile and get connected.
4.check again whether the weak security issue still existed;
---if yes, please leave me a private message and I would forward your case to the senior engineers for further assistance.
Thank you very much and wait for your reply.
- Copy Link
- Report Inappropriate Content
@TP-Link Same thing still happening. AES showing up on main router A7 and not when connected to a hard-wired RE220 (Ethernet, AP mode).
- Copy Link
- Report Inappropriate Content
I'm having the same issue. Updated the firmware but it's still showing as weak security.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4103
Replies: 8
Voters 0
No one has voted for it yet.