I noticed that my RB411U with a GSM modem lost a network connections. It turned out that it had some vital parts of the ppp-client configuration are mysteriously missing. Initially I got that issue with ROS v5.2 and for the MT satisfaction pumped up the version of it to v5.22, only to see the same thing.

Nothing has been done to that unit than some power losses here and there. So, to test out that bug I mis-configured a system watchdog, so it will pretty much constantly (once after ~3 minutes) reboot the unit:
That is what is being configured into the ppp-client for the GSM modem: That is what will happen to it some (numerous?) reboots later: I do not know when that configuration change took place, but sampling of the configuration was done within less than 24 hours.

I can not say that the system watchdog is causing that configuration erasing, but I recall as not having that issue before I choose to implement that.
I doubt that it has anything to do with the GSM modem brand (it has Option GTM378 in it) and is some sort of long standing bug within the ROS.
How to make the ppp-client configuration not to get changed by mere power cycling the unit?

not a resolve to the actual problem, but to make it work, make a script, adding Your setting's every time the ppp drops or something like that.

please contact support@mikrotik.com - we will provide you with a test release which most likely will fix it.
For now you can test out RouterOS v6.0rc6 and report back with the results.

not a resolve to the actual problem, but to make it work, make a script, adding Your setting's every time the ppp drops or something like that.

Yeah, I had that idea as well, but it should not be the proper way.

please contact support@mikrotik.com - we will provide you with a test release which most likely will fix it.
For now you can test out RouterOS v6.0rc6 and report back with the results.

OK, may I assume that the ROS v5 series has come to the end and no improvements/fixes will land there?

@Ivoshiee
If possible, try to change default PPP Client name 'ppp-out1' to different one.
From my experience, after reboot ROS sometimes recognizes connected modem as new one
and adds new, disabled PPP Client with default 'ppp-out1' name.
Maybe it causes configuration erasing due to some bug.

HTH,

please contact support@mikrotik.com - we will provide you with a test release which most likely will fix it.
For now you can test out RouterOS v6.0rc6 and report back with the results.

OK, may I assume that the ROS v5 series has come to the end and no improvements/fixes will land there?

v5.23 will have a fix for this issue but it isn't released yet, that is why you can test v6.0rc6 which has that fix already. Or contact support for a test release of v5.23

please contact support@mikrotik.com - we will provide you with a test release which most likely will fix it.
For now you can test out RouterOS v6.0rc6 and report back with the results.

OK, may I assume that the ROS v5 series has come to the end and no improvements/fixes will land there?

v5.23 will have a fix for this issue but it isn't released yet, that is why you can test v6.0rc6 which has that fix already. Or contact support for a test release of v5.23

I've done that, but does that issue was known before or the fix was quick one to make?

Also, the Watchdog Timer is broken for both v5 and v6 series.
The "watchdog-timer=no" does not have any effect as long as there a watch-address to play with. To truly get rid of the watchdog timer I have to remove watch-address as well.

I've done that, but does that issue was known before or the fix was quick one to make?

We had such report from one customer and we were able to reproduce that issue locally. We fixed that issue after v5.22 was released. The fix is already in v6.0rc6 and in pre-release of RouterOS v5.23.Contact support if you want that pre-release version.

I've done that, but does that issue was known before or the fix was quick one to make?

We had such report from one customer and we were able to reproduce that issue locally. We fixed that issue after v5.22 was released. The fix is already in v6.0rc6 and in pre-release of RouterOS v5.23.Contact support if you want that pre-release version.

Sadly it is not fixed even in the v6.0rc7.
http://ranume.radionet.ee/rb411u-still_ ... uppout.rif is the support.rif for your hacking pleasure.

Should I stick to the v6.0rc6 or does the supposed fix is being implemented in subsequent releases as well?

I've upgraded the box to the v6.0rc11, but I am not very hopeful about it.

Edit:
I've upgraded almost all my 25+ RB411U units to the ROS v6.0rc11, I've yet too see that issue. Maybe it is indeed fixed or more likely still not and it will bite me soon enough.

Was the issue fixed for you?

Matej

The v6.0rc11 did almost fix it or at least for the majority of these devices - I happened to see it occasionally even with the later releases, but I had to stop upgrading anything beyond the v6.0rc13 because later versions removed my Option GTM378 card support. The MT didn't respond to my requests to reinstate the Option GTM378 support or why it was dumped and so I haven't even tried any recent versions. No change log is listing those changes and arguing with them over it is quite pointless.

OK, thanks for the info...

Matej