From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: iproute2 query Date: Sun, 21 Feb 2016 12:05:25 -0800 Message-ID: <20160221120525.24769852@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Marcus Furlong Return-path: Received: from mail-io0-f180.google.com ([209.85.223.180]:33826 "EHLO mail-io0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750708AbcBUUFQ (ORCPT ); Sun, 21 Feb 2016 15:05:16 -0500 Received: by mail-io0-f180.google.com with SMTP id 9so158873747iom.1 for ; Sun, 21 Feb 2016 12:05:15 -0800 (PST) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 19 Feb 2016 20:12:04 +1100 Marcus Furlong 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.