I have an RB500 running RouterOS 3.7.

I have my RB500 set up so that the default route will ping its gateway with the "check-gateway=ping" parameter.

Every time I lose connectivity on that route, I get the following messages in the syslog:

Apr 28 14:16:04 sentry route,event Next hop gateway up
Apr 28 14:16:24 sentry route,event Next hop gateway down
(14:16:24 is when the connection came back up, just to be clear)
Apr 28 14:19:05 sentry route,event Next hop gateway up
Apr 28 14:19:45 sentry route,event Next hop gateway down
(141945 is when the connection came back up ...)
Apr 28 14:26:16 sentry route,event Next hop gateway up
Apr 28 14:26:57 sentry route,event Next hop gateway down

Notice anything funny about it? The messages are inverted. It first shows the gateway going up, and then down. Instead, it should be showing Down, and then back up again.

Can someone check the source code and make sure these messages are as they should be, or, its possible (highly unlikely, as this seems like a simple concept) that I'm misunderstanding it.

Thanks,

[bump]

Has anyone else noted this?? I can't be the only one using the check-gateway feature !!!

I saw this too. The MT reported the next-hop as "down" and then went thru the process of adding the route to the routing table. I could see the steps where it inserted the route and set it for redistribution (all steps that would happen when the next hop was available).

It seems like someone just got the up/down messages backwards. Could be quite confusing if you're troubleshooting.

OK, so since we got some bit of verification that it is showing "next hop gateway down" when it goes up, and vice-versa, how do we get Mikrotik to take note of it for change in a next release?

send an email to support@mikrotik.com. these forums don't always get 'tracked' like a ticket does.