Hi @words 

Thanks for posting in our business forum.

2.2.2 was originally not intended to be pushed via the cloud. So, due to some reasons, we don't want as many people to download this firmware and install it. This version aims to fix the security and other aspects to enhance the security.

I am not able to tell you the reasons behind this change was not in the original firmware release internally. 2.1.5 beta or later version should change this back.

At the time when people asked why there is a 2.2.2 and a beta 2.1.5, I explained in that thread that 2.2.2 will be a special one for some security reasons. (This security issue would not hurt anyone. HTTPS is forced does not mean it is vulnerable.) 2.1.5 is on the right track of the firmware updates.

Indeed, this might be confusing. But it is the team's decision. Please follow the 2.1.5 beta and its later stable release. Or downgrade previous firmware and import your backup. (Reset > Downgrade > Import backup > Turn on HTTPS > Upgrade to 2.2.2, or skip the upgrade to 2.2.2 and use beta 2.1.5.)

Skip this version and downgrade to the official release. Or use the 2.1.5 beta.

You need to turn on the HTTPS on the previous backup which I mean to say in Scenario 1. It would be downgrading first and then enabling HTTPS. I think the dev never thought this HTTPS would be disabled.. By default, it is enabled.

Hi @words 

Thanks for posting in our business forum.

words wrote

  @Clive_A your post it definitly confusing, it would be helpful to have table highlighting the features that the beta 2.1.5 and the release 2.2.2 have so one can understand what is different and why would use one versus ther other. What is "some security issue"? Perhaps this should be in that table.

 

-I didn't see anywhere a response to my question; does a factory reset also turn on HTTPS by default? Otherwise there is not much poing in doing a reset as I still won't have access. How does one do a factory reset with the button, I can't find this in the installation manual or any other documents for this product.

 

-Firmware 2.2.2 should be pulled, and instead the TPlink team should release 2.2.3 firmware which FORCES https to ON during the upgrade; that would be the right thing to do here

 

-I didn't upgrade via the cloud, I run the 605 standalone and subscribe to the forums to see when there is an update, this is why I upgraded.

 

I'll be switching back to 2.1.2 and staying there.

I am not the decision maker on the release note. The dev does. I am also an employee who needs to follow the confidentiality in the company. Even if I know it, I cannot tell you but conclude that it is "security fixes" and "no harm to your network security".

You want a 100% crystal clear in every change the dev made. I am not able to get that information and even if I have, I also need to check if I am authorized to tell you that. The dev would not include every detail or change in the release note if you look through the notes since ER605 V1. I have feedback on this matter so hope the dev will write notes better.

If you are on 2.2.2 firmware, the HTTPS is on no matter what. It was confirmed by the dev that this 2.2.2 aims to add up the security. And said would stop forcing HTTPS in the future firmware.

The manual indeed does not write how to reset on hardware version 2. That's gonna be another feedback to the team responsible for the manual writing.

The reset is universal to basically every device that has a hardware reset button. For ours, press and hold the reset button (for 5 seconds or so), the LED will flash and all LED will disappear and come back on. Wait for the device to reboot and reset to the factory default.

The dev does not intend to pull this firmware. I don't know if I have said this on other threads that this is a specially-made firmware for certain purposes. I was not informed to delete the thread either.

Hi @dhyaneshwar94 

Thanks for posting in our business forum.

dhyaneshwar94 wrote

  @Clive_A 

what are the steps to downgrade firmware?

 

If I just reset the router will it work?