Re: [LEDE-DEV] [PATCH] netifd: allow negative neighlocktime values

2017-08-17 Thread Hans Dedecker
On Thu, Aug 17, 2017 at 1:27 PM, Alin Nastac wrote: > When -1 is written in /proc/sys/net/ipv4/neigh//locktime, If the locktime proc file accepts a negative value it makes sense to change the type of neigh4locktime from unsigned integer to integer. This will avoid cppcheck flagging this again as a

[LEDE-DEV] [PATCH] netifd: allow negative neighlocktime values

2017-08-17 Thread Alin Nastac
When -1 is written in /proc/sys/net/ipv4/neigh//locktime, kernel disables ARP trashing protection. A value of 0 does not completely disable this protection, a second ARP update being discarded if it is processed during the same jiffie as the first update. Signed-off-by: Alin Nastac --- system-li