Thank you for reaching out and bringing this issue to our attention.
Could you clarify whether it worked properly on previous firmware and on which one, because there weren’t any changes from the mobile backend side?
Nevertheless, in this case, to troubleshoot and investigate this specific matter effectively, we’ll need to continue this process privately, because sensitive/publicly non-shareable information, such as the troubleshoot file containing logs, configurations, serial numbers, etc., needs to be collected.
You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 15655 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in detail and help work towards a solution.
Since this issue might be related to the dropped root access starting from firmware 7.17, that could indeed be the cause here. For our developers to better understand and dive deeper into the matter, we’ll need to collect some information that cannot be shared publicly on the forum.
Could you please submit the form that was sent to you so we can proceed with the investigation? Thank you.
The developers can easily diagnose the problem to just check if the “udhcpc.user” called or not.
On the other hand, I can’t share any private information related to our company without cyber security permission and they will not accept because we don’t have a signed NDA with your company.
Anyway, I’m ready to answer any questions that may be raised from your developers.
I wanted to let you know that I’ve forwarded this specific issue to our developers for further analysis. Once the investigation is completed and more details are available regarding a potential fix in future releases, I’ll make sure to share the information here.