lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 21 Feb 2016 12:05:25 -0800 From: Stephen Hemminger <stephen@...workplumber.org> To: Marcus Furlong <furlongm@...il.com> Cc: netdev@...r.kernel.org Subject: Re: iproute2 query On Fri, 19 Feb 2016 20:12:04 +1100 Marcus Furlong <furlongm@...il.com> wrote: > Hi, > > Just wondering if the following command should work: > > # ip route add 192.168.27.27/24 dev eth0 scope link src 192.168.27.27 > RTNETLINK answers: Invalid argument > > However, this command works: > > # ip route add 192.168.27.0/24 dev eth0 scope link src 192.168.27.27 > > 192.168.27.0/24 and 192.168.27.27/24 describe the same subnet? > > Regards, > Marcus. > It is the kernel complaining, not ip command. The kernel will not accept 192.168.27.27/24 as route since it is a full network address, not an network prefix.
Powered by blists - more mailing lists