I have a 2.9.31 system that was just put into production and I ran into what I believe is a critical bug in WinBox. I am running Ethernet in, Ethernet out of the box and when I was building the routes, through the box I was wondering why they were not coming up at Active/Static. After implementing the system and seeing that it was not working, I found that rebuilding the routes in the console worked just fine, but if I add the routes within WinBox, I would lose connectivity because all of the routes would show Static only, no longer Active. When I checked the settings on the route that was added through the console, I show Scope 255/Target Scope 10, however, the default settings on a new route added in WinBox are Scope 10/Target Scope 0.
Is there any reason why I should be experiencing troubles with this? I never ran into it before and I am concerned that it could pose problems if a person not aware of this bug tries to change the routes on our system.