interface: add strong host mark routing#87
Draft
dhrm1k wants to merge 1 commit into
Draft
Conversation
dhrm1k
marked this pull request as draft
July 16, 2026 02:57
Add an optional mark and mask to an interface and install matching rules for its IPv4 and IPv6 routing tables. Include the mapping in interface status so firewall4 can route replies through the interface they arrived on. Signed-off-by: Dharmik Parmar <dharmikparmar2004@yahoo.com>
dhrm1k
force-pushed
the
strong-host-mark-routing
branch
from
July 19, 2026 03:03
e5f7590 to
ed1ff48
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an optional mark and mask to a network interface and install matching
policy-routing rules for its
ip4tableandip6table.For example:
The mapping is also included in the interface status returned by netifd.
This is the routing half of the strong-host work discussed in
firewall4 issue #93. A
follow-up firewall4 change will use the mapping to remember the ingress WAN in
the conntrack mark and restore the packet mark on replies.
The option is disabled by default. Without the firewall4 change, existing
configurations are unaffected and the rule only has an effect when another
component sets the configured packet mark.