[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c4b854ef-6646-7ae8-b4a7-cb04b7b73222@6wind.com>
Date: Fri, 25 Jun 2021 17:32:08 +0200
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: Pali Rohár <pali@...nel.org>
Cc: Marek Behún <kabel@...nel.org>,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
linux-kernel@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Russell King <rmk+kernel@...linux.org.uk>,
Stephen Hemminger <stephen@...workplumber.org>,
Phil Sutter <phil@....cc>
Subject: Re: Issues during assigning addresses on point to point interfaces
Le 25/06/2021 à 17:27, Pali Rohár a écrit :
[snip]
>>> Hello Nicolas!
>>>
>>> See my original email where I put also rtnetlink packets (how strace see
>>> them). Seems that there is a bug in handling them (or bug in iproute2)
>>> as setting just peer (remote) IPv6 address is ignored:
>>> https://lore.kernel.org/netdev/20210606151008.7dwx5ukrlvxt4t3k@pali/
>>>
>>> Do you have any idea if this is affected by that "issue in the uAPI"?
>>> And what is the way how to fix it?
>> What about forcing IFA_LOCAL address to :: in your case?
>
> It does not work. ip address returns error:
>
> $ sudo ip address add :: peer fe80::8 dev ppp0
> RTNETLINK answers: Cannot assign requested address
So this trick could probably be used to handle your case, without breaking
anything, as it's not a valid command today.
Regards,
Nicolas
Powered by blists - more mailing lists