Support for source port and destination port on routing policy

Bug #1924227 reported by Quentin Smith
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned

Bug Description

systemd-networkd exposes these as SourcePort and DestinationPort in the [RoutingPolicyRule] section.

While we're at it, there appear to be several other matchers that are missing as well.

Documented fields in netplan:
from
to
table
priority
mark
type-of-service

and the missing fields are:
IncomingInterface
OutgoingInterface
SourcePort
DestinationPort
IPProtocol
InvertRule
Family
User
SuppressPrefixLength
Type

Filtering by port number allows certain bandwidth-hungry applications to be sent on a different interface in dual-homed scenarios.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.