Since firmware RUTX_R_00.07.07.1, and not solved in RUTX_R_00.07.07.2 the web-interface is very slow when modem operations are involved. I have narrowed it down to operations that involve /api/modems/status. Here are two examples, one fast and one slow:
Because new users in this forum can only add two links in the text I have added a screenshot of it.
The 30-second delay you’re experiencing is quite significant. I’ve attempted something similar without success. Could you please provide more details about the circumstances when you obtained these results? Specifically, what do you mean by “modem operations are involved”? Are you referring to the modem actively sending data or something different?
It could be configuration-dependent. To test this, you can take a backup (to restore your device to its previous state, if desired) and perform a factory reset. This will help us determine if the issue was indeed caused by the configuration.
The issue is away when I reset to “System settings”. So it is definitely config related. The question now is which part of the config and why did it suddenly start when updating to RUTX_R_00.07.07.1 and no config changes? Of course I can configure everything again from the ground up, but that will take cost me some time.
I’m sorry, but we cannot share the source code. You can try looking in the /sbin/api file, but please note that it might not provide much information since it is a compiled Lua script.
I have the exact same issue on RUTX12. Started a couple of weeks ago with firmware update to RUTX_R_00.07.07.2 and did not improve after further updating to RUTX_R_00.07.07.03. I will do a reset to system settings and a re-config from the ground up to see if it solves the issue, but I am quite upset by this loss of time!
It is indeed a loss of time. I hope we can tie this down to a specific config option that is bugging us. Until now I cannot reproduce it. Are you using igmp proxy by any chance?
No I don’t even know what it is.
In any case, after doing last night the reset to system settings and re-config the problem appears to be resolved (until next time).