For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 18483-1.
That’s good news but there are probably hundreds? of affected devices out there… I have 10 affected devices and no time for remote sessions. Please just make the fix / firmware available to us or publish it directly.
To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 18483-2 .
I filled the form - but for what? It only asked for email, username, ticket-id and description. Well, now you have my email, username and ticket-id and a meaningful description.
We have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 18483-3 .
Our R&D team has developed a beta version of the modem firmware, and we are currently looking for users who are still experiencing this issue to test the firmware and verify whether it resolves the problem.
If you are willing to participate, we can arrange a remote session with our R&D team to install the firmware and investigate the issue further.
Please let me know if you would be available for such a session.
It would be even greater to release this beta version (including a clear path back to the previous firmware) officially which would allow the ordinary user to try it out without any remote session. That would for sure get much more people trying it out I guess.