From: Phil Sutter <phil@nwl.cc>
Date: Thu, 8 Sep 2016 10:33:03 +0000 (+0200)
Subject: iproute: fix documentation for ip rule scan order
X-Git-Tag: v4.8.0~12
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=003f0fde6959b0f759fd1cc27201eb367753443e;p=thirdparty%2Fiproute2.git

iproute: fix documentation for ip rule scan order

Looks like the real issue is missing definition of priority.
---

diff --git a/man/man8/ip-rule.8 b/man/man8/ip-rule.8
index 3508d8090..13fe9f7f8 100644
--- a/man/man8/ip-rule.8
+++ b/man/man8/ip-rule.8
@@ -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.