iproute: fix documentation for ip rule scan order

Looks like the real issue is missing definition of priority.
This commit is contained in:
Phil Sutter 2016-09-08 12:33:03 +02:00 committed by Stephen Hemminger
parent 113fab78e4
commit 003f0fde69
1 changed files with 5 additions and 3 deletions

View File

@ -93,7 +93,7 @@ Each policy routing rule consists of a
.B selector
and an
.B action predicate.
The RPDB is scanned in order of increasing priority. The selector
The RPDB is scanned in order of decreasing priority. The selector
of each rule is applied to {source address, destination address, incoming
interface, tos, fwmark} and, if the selector matches the packet,
the action is performed. The action predicate may return with success.
@ -221,8 +221,10 @@ value to match.
.TP
.BI priority " PREFERENCE"
the priority of this rule. Each rule should have an explicitly
set
the priority of this rule.
.I PREFERENCE
is an unsigned integer value, higher number means lower priority. Each rule
should have an explicitly set
.I unique
priority value.
The options preference and order are synonyms with priority.