We're seeing strange behavior in ROS v7.18.2 on hEX where an IPv6 route generated dynamically via SLAAC displays as Active in telnet/ssh, but is clearly not according to the IPv6 Route List in Winbox. Screenshot attached with discrepencies outlined in red (and yes the print detail was executed while the corresponding route in Winbox displayed blue as not active).
In the above case, the route is actually not active as reflected in Winbox. This is tripping up our automation as it is relying on seemingly incorrect information via ssh. We can not reliably reproduce the above; when it happens it seems quite random. Is this a known issue?