From: Phil Sutter <p...@nwl.cc> Date: Tue, 1 Dec 2015 22:45:15 +0100
> Setting a value bigger than 255 resulted in using only the lower eight > bits of that value as it is assigned to the u8 header field. To avoid > this unexpected result, reject such values. > > Setting a value of zero is technically possible, but hosts receiving > such a packet have to treat it like hop_limit was set to one, according > to RFC2460. Therefore I don't see a use-case for that. > > Setting a route's hop_limit to zero in iproute2 means to use the sysctl > default, which is not the case here: Setting e.g. > net.conf.eth0.hop_limit=0 will not make the kernel use > net.conf.all.hop_limit for outgoing packets on eth0. To avoid these > kinds of confusion, reject zero. > > Signed-off-by: Phil Sutter <p...@nwl.cc> Applied, thanks Phil. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
