Hi there,
I've run into a fairly serious problem with some RUTXR1 routers on firmware version RUTX_R_00.07.01.4.
After making some configuration changes, then doing a backup and rebooting, they seem to sometimes be losing some network configuration.
After configuring 4 routers for a client, I shut them down by pulling the power, then realised I hadn't saved a backup. I booted them up again, successfully logged into them all, saved a config backup through the web interface, and shut them down about 5-10 seconds after making the config backup (again, by pulling the power out).
3 of those 4 routers were inaccessible after booting up again. I could not log into them on their configured IP addresses, and they had to be factory reset, and then have the saved config I took reapplied, after which they worked fine.
After spending probably 2 days trying to replicate and diagnose the fault, I've been able to reproduce it quite a few times, but have not been able to come up with a process to 100% reproduce it. A few things seem to be always consistent though:
- It always involves a config backup preceding the reboot
- A soft reboot through the web interface has never triggered the fault for me - only pulling the power
- The backup file taken immediately before rebooting is correct, and does not match the network configuration running when the fault occurs
When the fault occurs, I can usually log into the router on its default IP address (though the lan interface should normally be disabled), and I can see that the /etc/config/network file is very similar to factory defaults, and missing a large chunk of the configuration which should be there
Problem is present in several different routers of the same model/firmware, and persists through flashing new firmware.
Nothing that looks interesting to me shows up in any of the logs when this occurs, so the only real working theory I have is that some part of the flash memory is being mishandled during a configuration backup and getting corrupted when the power is pulled.
I can provide a saved configuration and some detailed instructions if someone from Teltonika is able to try to replicate this please.
Until we can determine exactly what is going wrong, our workaround is to save config and do a soft reboot after every configuration change, which is fairly intrusive for minor things.
Thanks,
Sam
