Interface RuleShowOptions

Select the destination port value to match. Supports port range.

Select the source prefix to match.

Select the fwmark value to match.

Select the incoming device to match.

If the interface is loopback, the rule only matches packets originating from this host. This means that you may create separate routing tables for forwarded and local packets and, hence, completely segregate them.

Select the ip protocol value to match.

Pertains to layer 3 master device-based routing, particularly relevant when using Virtual Routing and Forwarding (VRF) tables.

Invert the rule.

Sselect the outgoing device to match. The outgoing interface is only available for packets originating from local sockets that are bound to a device.

The priority of this rule.

PREFERENCE is an unsigned integer value, higher number means lower priority, and rules get processed in order of increasing number.

Each rule should have an explicitly set unique priority value. The options preference and order are synonyms with priority.

The routing protocol who installed the rule in question. As an example when zebra installs a rule it would get RTPROT_ZEBRA as the installing protocol.

Select the source port value to match. Supports port range.

The routing table identifier to lookup if the rule selector matches. It is also possible to use lookup instead of table.

Select the destination prefix to match.

Select the TOS value to match.

Attribute is used to match packets based on their tunnel ID, typically relevant for VXLAN (Virtual eXtensible Local Area Network) or other tunneling protocols that utilize tunnel IDs. The tunnel ID helps identify individual tunnels in scenarios where multiple tunnels are used.

The type of this rule.

Select the uid value to match.