Router Timing Out

RouterOS Scripting
1

Hello,

I wasn’t sure if I should post this here or in general discussion, but here it is…

We have a lot of RB493s that we have been using a script to configure. Recently we added some new functionality to the script and we started noticing that the router would begin to timeout and disconnect when managing it with Winbox. We thought it was possibly the link, but that checked out ok. Then I thought it was my computer, again fine. What we would notice is that we could configure the router, and sit there and ping it, and it would never/rarely timeout. As soon as we logged in via winbox however, it would timeout usually within the first minute. So obviously the problem is the script, and the new functions we added right? So we ‘reset-config’ and loaded a copy of the old script which never had this problem… again timeout after a few seconds of managing it.

Is there a possibility that something in the new script is broken… (not sure what as it doesn’t error while importing and taking the time to go through it after the import everything looks good).. and whatever is broken in it is persistent after the ‘reset-config’ causing the router while running the old configuration script to behave the same way?

Anything else we may be overlooking/not aware of?

This is using RouterOS 6.19, and we have tried with a really old version of winbox and the latest.

We are kinda stuck and would really like to get our file with the new features in production asap. Any help is appreciated.

Thanks!!

Understanding the Bridge Better
2

Any MikroTik router in between the one you’re managing and your Winbox management PC?

If so, maybe that other router has some sort of “hacker protection” that’s being falsely triggered. I would’ve initially guessed the same sort of protection on the router itself, but if it’s persisting after an old restore, then it sounds like it’s not originating at the device itself.

3

No router in the middle.

We ‘reset-config’ and just manually setup some basics, ip on ether1, default route etc… router behaves normally. Its gotta be in the script I’m thinking..

We are going to chop it up into 4-5 pieces and run each piece and try to narrow down where the strange behavior may be coming from.

4

After chopping up the script, I believe I have found an issue with my ‘Bridge’ configuration/implementation.

I have created a new topic in ‘General’ to discuss this issue: http://forum.mikrotik.com/t/understanding-the-bridge-better/85637/1

Thanks for taking the time to read and reply.