Skip to content

pbr-1.2.3: bump PKG_RELEASE from 95 to 97 - #178

Merged
egc112 merged 1 commit into
1.2.3from
pbr-1.2.3-release-97
Sep 2, 2026
Merged

egc112 merged 1 commit into
1.2.3from
pbr-1.2.3-release-97

Conversation

@egc112

@egc112 egc112 commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

What changed since 1.2.3-r95.

Three faults, all of which stopped the service from starting. pbr validates its whole nft file in one pass, so any one of them meant FAILED TO START and no policy routing at all — not just the policy at fault.

  • Setting Default ICMP Interface broke the service when IPv6 is enabled. The IPv6 rule was written as ip6 protocol icmp, which nft refuses: IPv6 headers have no protocol field, and the IPv6 ICMP protocol is icmpv6. Anyone who set that option and had IPv6 on lost all policy routing. It is now emitted correctly.

  • A policy's Protocol setting is reported when it cannot do what it looks like it does. proto qualifies a port match rather than matching on its own, so setting it without a port silently dropped it and the policy routed every protocol instead of the one you chose. Setting it to a protocol that has no ports — icmp and most of the list — with a port produced a rule nft refuses. The first is now a warning naming the policy; the second rejects just that policy, so the rest of the ruleset survives.

  • The Protocol dropdown now offers only protocols that can worktcp, udp, sctp, dccp, udplite. The list was previously built from every line of /etc/protocols, and 41 of the 46 entries it offered could not work. A value an existing policy already holds is still shown, marked (unsupported), so opening the page does not silently change your configuration.

To route ICMP, use Default ICMP Interface on the Advanced tab rather than a policy — a policy cannot express it. If you want "all traffic of one protocol", set the protocol and give it the port range 0-65535.

Documentation for all of this is in the 1.2.3 README, which also corrects the chain option: input and postrouting were listed for years and have never worked — the valid values are prerouting, forward and output.

The compatibility number moves to 37, so pbr and luci-app-pbr must be updated together.

PKG_RELEASE on the 1.2.3 branch moves in steps of two and stays odd — …91, 93, 95, 97. r96 is not a skipped release; there is no even number in this series.

Paired with mossdef-org/luci-app-pbr#49

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@egc112
egc112 merged commit 12e09ca into 1.2.3 Sep 2, 2026
7 checks passed
@egc112
egc112 deleted the pbr-1.2.3-release-97 branch September 2, 2026 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant