Hi,
We are running RouterOS 5.14. Very simple setup with a single interface with a configured global IPv6 address, directly connected to an established IPv6 network. RA and advertise etc are off. After adding the address the correct dynamic route appears in the routing table for that /64. Firewall is completely permissive but when attempting to ping another device on that /64 the error no route to host is returned.
This can be fixed by adding an identical static route to the routing table. The ping then works. Interestingly if the static is then removed the ping continues to work for a period of time.
I have read others that have discussed similar bugs in the RouterOS stack but these all relate to v4. It does not appear in the current bug tracker list. This is rather odd behaviour does anyone have a similar experience?
many thanks
Rob
Welcome to the brokenness that is v5 routing module ;-(
I’ve stopped submitting bugs for v5’s routing - supposedly there is a mythical new routing-test (new routing engine) due at some stage… and I’m placing high hopes on that.
Issues we’ve had in no particular order:
- OSPFv3 suddenly not working;
- switching between multiple IPs (on same interface) as source address
- main table simply not updating;
- stale routes remaining indefinitely in the table (I know that this is related to the route still being used - but we need a way to remove routes that are clearly invalid - such as by a BGP withdraw etc)
- Cannot propagate BGP in iBGP from eBGP – and no, using OSPF for this is not an option on many networks
So, in summary - I hope you get the issue resolved, but doubt it in the short term.
BUT of course submit the fault via support@mikrotik.com
– maybe you prompt the release of the stream of routing fixes 