Two IPv6-related Bugs in the New Versions 7.16 and 7.16.1

RouterOS General
1

Device Model: RB450G (mipsbe)
RouterOS Version: 7.16 or 7.16.1

Bug 1: After placing the PPPOE-OUT interface into VRF, there is a high probability that its IPv6 Link Local address will be in a “invalid” state, resulting in the automatically added IPv6 default route also being in an “inactive” state. Removing the PPPOE-OUT interface from VRF resolves this issue. Downgrading RouterOS to 7.15.3 eliminates the problem.
20241016055522.jpg
Bug 2: After successfully assigning an IPv6 address to the internal bridge, any modifications made to the address trigger the following error message when selecting “Apply” or “OK”: “Couldn’t change IPv6 Address xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 - pool allocated address prefix bits should be zero (6).” Downgrading RouterOS to 7.15.3 resolves the issue.
20241016055644.jpg

2

Same error here, Mikrotik Version 7.17.2, RB5009.

/ipv6/address/set advertise=no [find comment =“TEST”]

failure: pool allocated address prefix bits should be zero

3

Bug1 has been resolved in the new version, but I’m sorry, I don’t quite remember which version it started from. :laughing:

Bug2 originated from this modification in 7.16:

*) ipv6 - do not allow adding address with invalid prefix when using pool;

It has been resolved in the latest 7.19rc2:

*) ipv6 - fixed EUI-64 false error message on address update when “from-pool” option is used;