summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorHangbin Liu <liuhangbin@gmail.com>2015-07-30 14:28:42 +0800
committerDavid S. Miller <davem@davemloft.net>2015-07-30 15:56:40 -0700
commit8013d1d7eafb0589ca766db6b74026f76b7f5cb4 (patch)
tree95fb6a6dd3b962157ff2a2d9ce2ab6bfb3e1ca59 /scripts
parent2f51a9b8adbb6ad06689ec28342e89f40acb97fc (diff)
downloadblackbird-op-linux-8013d1d7eafb0589ca766db6b74026f76b7f5cb4.tar.gz
blackbird-op-linux-8013d1d7eafb0589ca766db6b74026f76b7f5cb4.zip
net/ipv6: add sysctl option accept_ra_min_hop_limit
Commit 6fd99094de2b ("ipv6: Don't reduce hop limit for an interface") disabled accept hop limit from RA if it is smaller than the current hop limit for security stuff. But this behavior kind of break the RFC definition. RFC 4861, 6.3.4. Processing Received Router Advertisements A Router Advertisement field (e.g., Cur Hop Limit, Reachable Time, and Retrans Timer) may contain a value denoting that it is unspecified. In such cases, the parameter should be ignored and the host should continue using whatever value it is already using. If the received Cur Hop Limit value is non-zero, the host SHOULD set its CurHopLimit variable to the received value. So add sysctl option accept_ra_min_hop_limit to let user choose the minimum hop limit value they can accept from RA. And set default to 1 to meet RFC standards. Signed-off-by: Hangbin Liu <liuhangbin@gmail.com> Acked-by: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud