From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Alexey Kuznetsov" <kuznet@ms2.inr.ac.ru>,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
linux-kernel@vger.kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Russell King" <rmk+kernel@armlinux.org.uk>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Phil Sutter" <phil@nwl.cc>
Subject: Re: Issues during assigning addresses on point to point interfaces
Date: Fri, 25 Jun 2021 17:32:08 +0200 [thread overview]
Message-ID: <c4b854ef-6646-7ae8-b4a7-cb04b7b73222@6wind.com> (raw)
In-Reply-To: <20210625152737.6gslduccvguyrr77@pali>
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
prev parent reply other threads:[~2021-06-25 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 15:10 Issues during assigning addresses on point to point interfaces Pali Rohár
2021-06-24 10:45 ` Marek Behún
2021-06-24 12:57 ` Nicolas Dichtel
2021-06-25 8:40 ` Pali Rohár
2021-06-25 15:06 ` Nicolas Dichtel
2021-06-25 15:27 ` Pali Rohár
2021-06-25 15:32 ` Nicolas Dichtel [this message]
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=c4b854ef-6646-7ae8-b4a7-cb04b7b73222@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali@kernel.org \
--cc=phil@nwl.cc \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stephen@networkplumber.org \
--cc=yoshfuji@linux-ipv6.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).