matthias
/
iproute2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

man: ip-rule.8: Further clarify how to interpret priority value 

Despite the past changes, users seemed to get confused by the seemingly
contradictory relation of priority value and actual rule priority.

Signed-off-by: Phil Sutter <phil@nwl.cc>
This commit is contained in:
Phil Sutter 2017-04-24 17:35:37 +02:00 committed by Stephen Hemminger
parent 35893864c8
commit 843fc90068
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/man8/ip-rule.8
View File

@ -95,7 +95,10 @@ Each policy routing rule consists of a
.B selector .B selector
and an and an
.B action predicate. .B action predicate.
The RPDB is scanned in order of decreasing priority. The selector The RPDB is scanned in order of decreasing priority (note that lower number
means higher priority, see the description of
.I PREFERENCE
below). The selector
of each rule is applied to {source address, destination address, incoming of each rule is applied to {source address, destination address, incoming
interface, tos, fwmark} and, if the selector matches the packet, interface, tos, fwmark} and, if the selector matches the packet,
the action is performed. The action predicate may return with success. the action is performed. The action predicate may return with success.
@ -225,7 +228,8 @@ value to match.
.BI priority " PREFERENCE" .BI priority " PREFERENCE"
the priority of this rule. the priority of this rule.
.I PREFERENCE .I PREFERENCE
is an unsigned integer value, higher number means lower priority. Each rule 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 should have an explicitly set
.I unique .I unique
priority value. priority value.