diff options
author | 2025-10-19 19:28:48 +0200 | |
---|---|---|
committer | 2025-10-22 19:05:38 +0200 | |
commit | ea4b5553c21bc99e8645133b6ac8fec90d53b190 (patch) | |
tree | 5e12b5b436e32c13154642bca2d509e71a8cd8b6 /check-certificates | |
parent | c62f2362517186f434570e2ed67c0d89844e1bdc (diff) | |
parent | b80b872e557e2513c7e9ee4c6f119e3ad56d4116 (diff) |
Merge branch 'netmask6' into nextHEADrouteros-7.21beta2-3nextmain
This branch is a follow-up on 9ceed0926a749c51ebc050d80cd33100ecdbcc5a
with clean solution. Read on for details...
The data type `ip6-prefix` used to hold what it was named for - an IPv6
prefix:
[user@mikrotik] > :put 2001:db8::dead:beef/32
2001:db8::/32
This changed with RouterOS 6.21beta2, which now allows that exact same
data type to hold something like "address with prefix length attached":
[user@mikrotik] > :put 2001:db8::dead:beef/32
2001:db8::dead:beef/32
My scripts (namely `fw-addr-lists`) relied on the old behaviour and broke.
The commit mentioned above was just a quick workaround, with rough edges,
and it could still fail.
Sadly RouterOS does not support bit shifting on IPv6 data types, so a
(completely) mathematical solution is out of scope.
This branch implements a new and better workaround, see the first commit
of branch (6ad6f9aa08d558ff2e8ff3010fe5daec3c600c4a) for details.
I opened a support ticket / feature request on this topic, let's see
what results it brings...
https://help.mikrotik.com/servicedesk/servicedesk/customer/portal/1/SUP-201881
Diffstat (limited to 'check-certificates')
0 files changed, 0 insertions, 0 deletions