Skip to content

v1.4.0

Choose a tag to compare

View all tags
@WekaJosh WekaJosh released this 01 Sep 16:18
· 1 commit to main since this release
v1.4.0
1c1ca04

Changes

  • IP rule priorities now allocate from 10000 instead of 100 (stepping 10 per rule). Priorities below 10000 stay free for VPN, firewall-mark, and admin policy rules that should evaluate first; the base matches cloud tooling conventions (amazon-ec2-net-utils uses 10000+ifindex) and remains well before the main table lookup at 32766.
  • All persistence backends now set the rule priority explicitly. The NetworkManager dispatcher and ifupdown backends previously issued ip rule add without a priority, letting the kernel pick -- so a rule re-added at boot or link-up could land at a different precedence than the one configure created. All four backends now derive the same priority from shared constants.

Upgrade note

Already-configured systems keep their working rules at the old priorities (validation matches rules by source IP and table, not priority), so updating the tool does not churn a running system. To renumber an existing box:

sbr-config --rollback
sbr-config --configure

Release on top of v1.3.1.

Assets 2
Loading