aboutsummaryrefslogtreecommitdiffstats
BranchCommit messageAuthorAge
mainmod/notification-email: ignore errors (for now...)Gravatar Christian Hesse4 days
nextcontrib/checksums.sh: output to stdout...Gravatar Christian Hesse20 hours
routeros-v6adopt all required certificate changesGravatar Christian Hesse14 months
stagingdoc/mod/ssh-keys-import: reverse old and newGravatar Christian Hesse4 days
 
TagDownloadAuthorAge
routeros-7.21beta2-4commit 20987221d9...Gravatar Christian Hesse4 days
routeros-7.21beta2-3commit ea4b5553c2...Gravatar Christian Hesse9 days
routeros-7.21beta2-2commit 9ceed0926a...Gravatar Christian Hesse3 weeks
routeros-7.21beta2-1commit 5ffa85f8bf...Gravatar Christian Hesse3 weeks
routeros-7.20beta4-1commit c3010af4ed...Gravatar Christian Hesse4 months
routeros-7.20beta2-1commit 6130c94cc1...Gravatar Christian Hesse5 months
routeros-7.18rc1-2commit e08bb2192d...Gravatar Christian Hesse5 months
change-138commit 86ad41f6b6...Gravatar Christian Hesse5 months
routeros-7.19-1commit 86ad41f6b6...Gravatar Christian Hesse5 months
routeros-7.18-1commit 6331505dbe...Gravatar Christian Hesse8 months
[...]
 
AgeCommit messageAuthorFilesLines
4 daysmod/notification-email: ignore errors (for now...)•••Errors are returned since RouterOS 7.21beta2. We keep the current logic for now, as we want to support older RouterOS versions. This is something to be reworked later... HEADrouteros-7.21beta2-4mainGravatar Christian Hesse1-2/+5
9 daysMerge branch 'netmask6' into next•••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 routeros-7.21beta2-3Gravatar Christian Hesse3-10/+52
11 daysmod/ipcalc: support IPv6•••Well, some of these values do not make a lot of sense for IPv6... Something to be cleaned up later. Gravatar Christian Hesse1-6/+17
11 daysfw-addr-lists: use $NetMask6Gravatar Christian Hesse1-4/+4
11 daysglobal-functions: $NetMask6: implement simple caching•••The calculation is quite complex for something that needs to be done frequently, for example by `fw-addr-lists`. The number of possible netmasks is limited, so let's cache the results that were calculated already. Gravatar Christian Hesse1-1/+13
11 daysglobal-functions: introduce $NetMask6•••RouterOS does not support bit shifting on IPv6 data types, so we have to split the problem: * each 16 bit block is calculated separately, as number * the complete netmask is assembled in a loop, as string * the final string is casted to correct data type Gravatar Christian Hesse1-0/+19
12 daysMerge branch 'netmask4' into nextGravatar Christian Hesse3-3/+21
2025-10-16fw-addr-lists: normalize IPv4 addressesGravatar Christian Hesse1-2/+9
2025-10-16mod/ipcalc: use $NetMask4Gravatar Christian Hesse1-1/+4
2025-10-16global-functions: introduce $NetMask4Gravatar Christian Hesse1-0/+8
[...]
 
Clone
https://git.eworm.de/cgit/routeros-scripts
https://github.com/eworm-de/routeros-scripts
https://gitlab.com/eworm-de/routeros-scripts