[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C5551D9AAB213A418B7FD5E4A6F30A0789291D62@ORSMSX108.amr.corp.intel.com>
Date: Tue, 24 Mar 2015 00:33:02 +0000
From: "Rose, Gregory V" <gregory.v.rose@...el.com>
To: roopa <roopa@...ulusnetworks.com>
CC: "stephen.hemminger@...tta.com" <stephen.hemminger@...tta.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"vadim4j@...il.com" <vadim4j@...il.com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Subject: RE: ip addr add command generates error
> -----Original Message-----
> From: roopa [mailto:roopa@...ulusnetworks.com]
> Sent: Monday, March 23, 2015 5:13 PM
> To: Rose, Gregory V
> Cc: stephen.hemminger@...tta.com; netdev@...r.kernel.org;
> vadim4j@...il.com; Brandeburg, Jesse
> Subject: Re: ip addr add command generates error
>
> On 3/23/15, 3:43 PM, Rose, Gregory V wrote:
> > The 'ip addr add' command used to use the following syntax:
> >
> > # ip addr add 10.0.0.2/24 brd 10.0.0.255 dev <eth>
> >
> > However, attempts to use that same command syntax with the current
> iproute2 tip gives the following error:
> >
> > Error: an inet prefix is expected rather than "20.0.0.2/24"
> >
> > This seems like a bug. The commit that introduces the issue is
> f3a2ddc124e09d3990b836e322ed39c76c35546e by Vadim Kochan. Reverting this
> commit fixes the problem.
> >
> > Is this change deliberate? It would break a lot of scripts if so.
> >
>
> looked like an unintended change. This was reported a few days back and I
> hit this too in another context and a patch
> https://patchwork.ozlabs.org/patch/451210/ is in the queue.
Patch looks good.
Thanks!
- Greg
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists