From: "Pali Rohár" <pali@kernel.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
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:27:37 +0200 [thread overview]
Message-ID: <20210625152737.6gslduccvguyrr77@pali> (raw)
In-Reply-To: <d3dd210c-bf0f-7b48-6562-23e87c2ad55a@6wind.com>
On Friday 25 June 2021 17:06:21 Nicolas Dichtel wrote:
> Le 25/06/2021 à 10:40, Pali Rohár a écrit :
> > On Thursday 24 June 2021 14:57:41 Nicolas Dichtel wrote:
> >> Le 24/06/2021 à 12:45, Marek Behún a écrit :
> >>> On Sun, 6 Jun 2021 17:10:08 +0200
> >>> Pali Rohár <pali@kernel.org> wrote:
> >>>
> >>>> Hello!
> >>>>
> >>>> Seems that there is a bug during assigning IP addresses on point to
> >>>> point interfaces.
> >>>>
> >>>> Assigning just one local address works fine:
> >>>>
> >>>> ip address add fe80::6 dev ppp1 --> inet6 fe80::6/128 scope link
> >>>>
> >>>> Assigning both local and remote peer address also works fine:
> >>>>
> >>>> ip address add fe80::7 peer fe80::8 dev ppp1 ---> inet6 fe80::7
> >>>> peer fe80::8/128 scope link
> >>>>
> >>>> But trying to assign just remote peer address does not work. Moreover
> >>>> "ip address" call does not fail, it returns zero but instead of
> >>>> setting remote peer address, it sets local address:
> >>>>
> >>>> ip address add peer fe80::5 dev ppp1 --> inet6 fe80::5/128 scope
> >>>> link
> >>>>
> >>>
> >>> Adding some other people to Cc in order to get their opinions.
> >>>
> >>> It seems this bug is there from the beginning, from commit
> >>> caeaba79009c2 ("ipv6: add support of peer address")
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=caeaba79009c2
> >>>
> >>> Maybe some older user-space utilities use IFA_ADDRESS instead of
> >>> IFA_LOCAL, and this was done in order to be compatible with them?
> >> If I remember well, there was an issue in the uAPI.
> >> IFA_LOCAL is supposed to be the address of the interface and IFA_ADDRESS is
> >> supposed to be the endpoint of a point-to-point interface.
> >> However, in case of IPv6, it was not the case. In netlink messages generated by
> >> the kernel, IFA_ADDRESS was used instead of IFA_LOCAL.
> >> The patch tried to keep the backward compatibility and the symmetry between msg
> >> from userland and notification from the kernel.
> >
> > 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
Here is strace output:
sendmsg(3, {
msg_name={
sa_family=AF_NETLINK,
nl_pid=0,
nl_groups=00000000
},
msg_namelen=12,
msg_iov=[{
iov_base={
{
len=64,
type=RTM_NEWADDR,
flags=NLM_F_REQUEST|NLM_F_ACK|NLM_F_EXCL|NLM_F_CREATE,
seq=1624633811,
pid=0
},
{
ifa_family=AF_INET6,
ifa_prefixlen=128,
ifa_flags=0,
ifa_scope=RT_SCOPE_UNIVERSE,
ifa_index=if_nametoindex("ppp0")
},
[
{
{
nla_len=20,
nla_type=IFA_LOCAL
},
inet_pton(AF_INET6, "::")
},
{
{
nla_len=20,
nla_type=IFA_ADDRESS
},
inet_pton(AF_INET6, "fe80::8")
}
]
},
iov_len=64
}],
msg_iovlen=1,
msg_controllen=0,
msg_flags=0
}, 0) = 64
recvmsg(3, {
msg_name={
sa_family=AF_NETLINK,
nl_pid=0,
nl_groups=00000000
},
msg_namelen=12,
msg_iov=[{
iov_base=NULL,
iov_len=0
}],
msg_iovlen=1,
msg_controllen=0,
msg_flags=MSG_TRUNC
}, MSG_PEEK|MSG_TRUNC) = 84
recvmsg(3, {
msg_name={
sa_family=AF_NETLINK,
nl_pid=0, nl_groups=00000000
},
msg_namelen=12,
msg_iov=[{
iov_base={
{
len=84,
type=NLMSG_ERROR,
flags=0,
seq=1624633811,
pid=3698
},
{
error=-EADDRNOTAVAIL,
msg={
{
len=64,
type=RTM_NEWADDR,
flags=NLM_F_REQUEST|NLM_F_ACK|NLM_F_EXCL|NLM_F_CREATE,
seq=1624633811,
pid=0
},
{
ifa_family=AF_INET6,
ifa_prefixlen=128,
ifa_flags=0,
ifa_scope=RT_SCOPE_UNIVERSE,
ifa_index=if_nametoindex("ppp0")
},
[
{
{
nla_len=20,
nla_type=IFA_LOCAL
},
inet_pton(AF_INET6, "::")
},
{
{
nla_len=20,
nla_type=IFA_ADDRESS
},
inet_pton(AF_INET6, "fe80::8")
}
]
}
}
},
iov_len=84
}],
msg_iovlen=1,
msg_controllen=0,
msg_flags=0
}, 0) = 84
next prev parent reply other threads:[~2021-06-25 15:27 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 [this message]
2021-06-25 15:32 ` Nicolas Dichtel
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=20210625152737.6gslduccvguyrr77@pali \
--to=pali@kernel.org \
--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=nicolas.dichtel@6wind.com \
--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).