Weird RouterOS problem

RouterOS General
1

Hi Folks, just thought I would ask about this to see if anybody had seen a similar problem to one I experienced last night.
I am running RouterOS 2.9.40 in Intel hardware, been running for 3 weeks now without issue.
Router has 3 main interfaces, public, private, and one other. We have about 5 public IP’s on the public interface so I wanted to add some comments to them so we had them documented in the router. As soon as I added a comment to the first one (the main IP) I lost connectivity, I was connected remotely. Upon going to the site to check the problem, I found that whenever I added a comment to an IP which was on the public interface, the whole interface went down. I had to disable and enable the interface to bring it back up. I also found that by this happening, it totally broke my source NAT rules for those IP’s. To fix the source NAT rules I had to disable and enable the public IP for each. I am running Realtek 8139 chipset NIC’s, and have been using them for a long time so I can’t imagine it’s them. I have checked the change logs and nothing it mentioned about anything remotely like this problem being fixed. I can upgrade to 2.9.42, but not sure if this will help.

I have replicated the problem multiple times now, and can’t find any reason why it might be happening, everything is normal, and nothing fancy is setup.

Has anybody seen this before or have any suggestions on what might be causing it ?

This is a production router in a small datacentre environment, so now I’m scared to change anything remotely just in case it shags itself.

Regards
Paul

2

Yes. Do not configure a link with winbox over which you send the configuration
to the router. I believe that sending config and change link config interfere.
Use ssh for these changes. We saw this on wireless llnks. Had to drive to
the tower to reconfigure the interface.

Stefan

3

Fair point, but I wouldn’t consider that I was changing the config really by just adding a comment. The router had been running for a couple of weeks before I added the simple comment. I should try to SSH to and and do the same thing next time I am on site just in case it is a winbox thing.

Thanks
Paul