From: Stephen Hemminger <stephen@networkplumber.org>
To: Marcus Furlong <furlongm@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 query
Date: Sun, 21 Feb 2016 12:05:25 -0800 [thread overview]
Message-ID: <20160221120525.24769852@xeon-e3> (raw)
In-Reply-To: <CAH4CTx4zv_zEgdJYLehReC=JU0-uuWgVNRyLgSjS5CwhY8c2iA@mail.gmail.com>
On Fri, 19 Feb 2016 20:12:04 +1100
Marcus Furlong <furlongm@gmail.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.
next prev parent reply other threads:[~2016-02-21 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 9:12 iproute2 query Marcus Furlong
2016-02-21 20:05 ` Stephen Hemminger [this message]
2016-02-23 0:19 ` Marcus Furlong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160221120525.24769852@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=furlongm@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).