Support fwmark and iif on the RoutingEntryRule
Bug #1900866 reported by
Adam Dyess
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-advanced-routing |
Fix Released
|
Undecided
|
Adam Dyess |
Bug Description
I would like the following advanced-
[{
"type": "table",
"table": "main"
},{
"type": "table",
"table": "Public"
},{
"type": "rule",
"fwmark": "1/0xF",
"iif": "bond0",
"table": "main",
"priority": 110
},{
"type": "rule",
"fwmark": "1/0xF",
"table": "Public"
"priority": 111
}]
to create the rules:
ip rule add fwmark 1/0xF iif bond0 table main priority 110
ip rule add fwmark 1/0xF table Public priority 111
Related branches
charm-advanced-routing:bug/1900866
- Drew Freiberger (community): Approve
- Peter Sabaini (community): Approve
- Paul Goins: Approve
-
Diff: 222 lines (+134/-6)4 files modifiedsrc/lib/routing_entry.py (+46/-4)
src/lib/routing_validator.py (+38/-2)
src/tests/unit/test_RoutingConfigValidator.py (+32/-0)
src/tests/unit/test_RoutingEntryRule.py (+18/-0)
summary: |
- Support fwmark and iff on the RoutingEntryRule + Support fwmark and iif on the RoutingEntryRule |
description: | updated |
Changed in charm-advanced-routing: | |
assignee: | nobody → Adam Dyess (addyess) |
Changed in charm-advanced-routing: | |
status: | New → Fix Released |
milestone: | none → 21.01 |
To post a comment you must log in.
this would enable routing decisions based on fwmark-ing and input interfaces