I have various routing marks mangles for different wan gateways, and whenever the router was rebooted, the assigned route appears blue and route is not working. The route mark name still appears under the drop down list but its as if the name is not linking to the mangle name correctly. The lights are buring but there is nobody home.
The gateways is reachable. The new-routing-mark name still exist under the routing table, but each entry shows blue. It’s like its not linking to the name stated in the mangle rule correctly. Once I change the name under mangle and adjust the routing entry to the new adjusted name, the route entry turns black and it works.
The entries in the routing table being blue does not mean they are not linking to the mangle table, it means
the router decides they are not usable due to unreachable gateway.
Remember you must always have a route to the gateway in the main table as well.
I understand. While the routes appear blue, the gateways are defiantly ping-able, it only when I change the mangle new-routing-mark (adding a number, high-fin, underscore est) and change the routes to new name, it turns black and works. This work perfectly in the past, this possible bug started when I upgraded to 6.35 and every time when I reboot the router.
There have been reports like this with 6.35.1 but maybe this is a special condition that affected that version already?
Try to do a /export file=backup then a “reset configuration” with “no defaults” and specify the backup.rsc as load after.
This will clear the entire config and rebuild it from the ascii config commands. This should get rid of any internal
inconsistencies in the binary config.