It’s not the cause of the bug;
Some customers reported that 4.x was automatically upgraded and some configurations were lost which they did not know before the upgrade;
As a result, GLiNet needs to withdraw the firmware release and adjust the upgrade strategy;