@MagicMiguel 

Currently, I am waiting for firmware from technical support that disables the telnet port (23) and others that are unnecessary for the functioning and integrity of the Deco system.

It is unacceptable how slowly things are moving here, especially in the context of security issues. Just look at this thread and see how long it has been, and there are still no stable versions for most systems, only beta versions provided…

  @Denis55 

@MagicMiguel 

First, thank you for your attentive engagement with this post.  I can assure you that all publicly released beta firmware available here has No telnet or other ports enabled by default.

@Denis55 , please let me clarify that you are not currently using the beta firmware for the Deco X60. I truly appreciate your consistent collaboration with the engineer and would like to install the debug firmware to assist him in troubleshooting the issue. Security concern is always our top priority so I hope all discussions are grounded in factual information.

If any reported issues expose potential security risks, rest assured they will be promptly addressed in the next firmware upgrade. However, the current issue does not fall into that category and our engineers are still working hard to provide temporary workarounds and plan to enroll the beta fix in the future firmware release.

I can't provide a definitive reason why some models are still using beta versions instead of the official ones. The engineering team may have their own timeline, but please know that ensuring network security is a shared priority for all of us.

The community always strives to offer available solutions but we also face knowledge limitations and resource constraints. The local technical team and warranty policies are our powerful backup support, especially for aging models, such as Deco P9. @Nytram  If we fail to offer acceptable suggestions, claiming for replacement is always a recommended choice.

Your attention and understanding are highly appreciated.

Thanks again and Best regards.

  @David-TP 

A kind reminder!

Given that this post is very long and has numerous pages, if your similar issue isn’t resolved by the beta version mentioned here or if the beta firmware has introduced additional problems, it is recommended to start a new thread here with more details to ensure that your valuable feedback receives a timely response.

Thank you very much and best regards.

  @David-TP 

I am a straightforward person, and I say things as they are, to anyone, at any time. This may be a flaw of mine, or maybe not, but pay attention to what I am about to tell you. I sense a slight “frustration” in your response, and I believe I should be the one feeling “frustrated,” NOT YOU. However, I want us to discuss and clarify a few aspects before anything else, and I hope you will consider the following points—or not, if you don’t wish to. Nevertheless:

Please note that I did my best to provide accurate and well-tested feedback from someone with some technical knowledge. I'm not asking for rewards, but for all the detailed information I provided, I didn't receive any subscription discounts, vouchers, or anything other than thanks (my house is full of thanks 😅). Little things that matter, but TP-Link doesn't seem to place much value on these practices. I reported issues to you and the engineers, which as you know from my emails or community threads, were real and validated by the engineers. I was certainly not obliged to run such tests or experiments with different beta versions and waste my time on these issues, but I did it out of respect and love for this brand. I wanted to help where I could, based on my technical knowledge. Essentially, "I worked as a tester for this company for free" (as a joke) 😆, but I don't regret it, as I told you before. I love technology and I chose to do this voluntarily.

Remember, I am the one who paid for these devices, which are not cheap, and I have had an unresolved issue for months (MONTHS), which has only been addressed in beta. The beta version from this thread, as you know, is only a partial solution for the X60, as it introduces other problems (you are well aware of the feedback post about this version).

To clarify, you are mistaken on a few points: I currently have a BETA firmware provided by the engineers that addresses the issues highlighted in this public BETA version. As you know, you have access to the emails to review these conversations. Consider that I am lucky to have enough technical knowledge to attempt such solutions. But what are you doing as a company for people who, having bought your products from stores, face this problem and can’t even diagnose it? Do you think everyone knows to search communities or try beta firmware, etc.? NO, most consumers buy a product expecting it to work 100% without issues. To cut this short, if you don’t have the necessary resources or knowledge or enough time allocated to optimize these problems, there should have been an immediate firmware rollback, so users wouldn’t even notice the issue or, at worst, a hotfix applied within a few days.

However, it’s hard to believe that a company like TP-Link, which sells such devices (not cheap at all) and makes millions of dollars/euros from equipment sales and subscriptions, can’t resolve or doesn’t have the resources (as you claim) to fix such bugs over several months?! David, what are we talking about here? 😅 The entire technical team should have been focused solely on these critical issues, and the problem would likely have been resolved long ago.

What is suspicious, however, is how this bug suddenly appeared on all Deco systems (including the latest releases). On my old X20 system, I had no problem until a few months ago, and from what I remember, it appeared on a firmware that wasn’t even the latest. So, how did this bug “emerge”? I bought another system (the current X60) because of this issue, spending a lot of money, only to face the same problem.

Regarding security, David, what are we talking about? There is no official document explaining how to test and fully understand how HomeShield - Security+ works, including something as simple as blocking malicious web content. Let’s not delve deeper into the technical aspects, but as you know, I’ve also created a community thread on how this service works. Should I mention that users, especially those with Apple devices, can’t benefit from Security+ or parental control (a paid subscription - ATTENTION) because it doesn’t work due to Apple’s privacy measures? They have to disable features like “Limit IP Address Tracking” for these services to function. Yes, this isn’t entirely TP-Link’s fault, but you should have informed users about this before they paid for the subscription and worked with Apple (if possible) to find a solution. Practically, anyone could now pay for a HomeShield subscription that only partially works, wasting their money.

How does the idea sound to you that if I were to revert to the official firmware currently available, and let’s assume this BETA firmware didn’t even exist, I wouldn’t be able to use the Deco system I paid for over the past months, and the issue still exists? Does this seem normal to you? And I repeat… this problem is still present, David.

David, let's put aside any frustrations and focus on what matters: you, as a company, deliver exactly what you promise, so that people can benefit from what they paid for. Remember, these devices were not given away for free, people paid for them, and therefore your salaries are funded by us, the users, who expect you to deliver on your promises. You are largely a provider of internet solutions and equipment, David, and it does not reflect well if such a company cannot solve problems that should not even reach the end users.

I’m looking forward to receiving the new firmware, which I hope will be perfect and stable without any issues.

Please don’t be upset with me, I have nothing personal against you, and it's not entirely your fault. I truly appreciate your involvement. But don’t forget, I’m probably the one who should be upset about the money I’ve spent. I hope you understand this criticism is constructive. Wishing you the best! 😃

  @MagicMiguel 

I think you misunderstood a bit. Like you, based on this thread, I had access to this publicly released beta firmware, just like anyone else. I didn’t provide feedback because I was obliged to do so, but out of pure passion and the hope that the issues would be resolved and clearly understood by TP-LINK engineers. As I said, I did this and prefer to continue helping with feedback where my knowledge can be applied, of course, and I will keep doing it because that’s the kind of person I am—if I can help, I gladly help anyone. 😃

And yes... I believe I have covered some key points regarding how TP-LINK should take action in certain circumstances. I completely agree with you, and as I mentioned, this issue should have been resolved a long time ago.

MagicMiguel wrote

  @Denis55 

 

in addition to Denis' points, I would also like to point out that it sounds like he is in the position where he can spend months helping to beta test firmware. I was not. I work from home with no option to go into an office. I need a stable network at all times. Not only did I spend a lot of money on my 4 Decos, but then I had to spend more money on 4 new Eeros once this problem surfaced. That is around 1,000 USD total in networking equipment. The point has been made that if the issues cannot be fixed quickly due to resources, an immediate rollback should have happened so people can use their networks. The internet is a critical utility for many people. A networking company should be aware of this.