From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>,
Paul Holzinger <pholzing@redhat.com>
Subject: [PATCH v3 6/7] pasta: Disable neighbour solicitations on device up to prevent DAD
Date: Fri, 16 Aug 2024 09:39:17 +0200 [thread overview]
Message-ID: <20240816073918.1483136-7-sbrivio@redhat.com> (raw)
In-Reply-To: <20240816073918.1483136-1-sbrivio@redhat.com>
As soon as we the kernel notifier for IPv6 address configuration
(addrconf_notify()) sees that we bring the target interface up
(NETDEV_UP), it will schedule duplicate address detection, so, by
itself, setting the nodad flag later is useless, because that won't
stop a detection that's already in progress.
However, if we disable neighbour solicitations with IFF_NOARP (which
is a misnomer for IPv6 interfaces, but there's no possibility of
mixing things up), the notifier will not trigger DAD, because it can't
be done, of course, without neighbour solicitations.
Set IFF_NOARP as we bring up the device, and drop it after we had a
chance to set the nodad attribute on the link.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
---
netlink.c | 22 ++++++++++++----------
pasta.c | 11 ++++++++++-
2 files changed, 22 insertions(+), 11 deletions(-)
diff --git a/netlink.c b/netlink.c
index 06a3816..9592b1b 100644
--- a/netlink.c
+++ b/netlink.c
@@ -689,11 +689,10 @@ int nl_addr_set_ll_nodad(int s, unsigned int ifi)
.ifa.ifa_family = AF_INET6,
.ifa.ifa_index = ifi,
};
- unsigned ll_addrs = 0;
+ uint32_t seq, last_seq = 0;
+ ssize_t status, ret = 0;
struct nlmsghdr *nh;
char buf[NLBUFSIZ];
- ssize_t status;
- uint32_t seq;
seq = nl_send(s, &req, RTM_GETADDR, NLM_F_DUMP, sizeof(req));
nl_foreach_oftype(nh, status, s, buf, seq, RTM_NEWADDR) {
@@ -713,19 +712,22 @@ int nl_addr_set_ll_nodad(int s, unsigned int ifi)
*(uint32_t *)RTA_DATA(rta) |= IFA_F_NODAD;
}
- nl_send(s, nh, RTM_NEWADDR, NLM_F_REPLACE, nh->nlmsg_len);
- ll_addrs++;
+ last_seq = nl_send(s, nh, RTM_NEWADDR, NLM_F_REPLACE,
+ nh->nlmsg_len);
}
if (status < 0)
- return status;
+ ret = status;
- seq += ll_addrs;
+ for (seq = seq + 1; seq <= last_seq; seq++) {
+ nl_foreach(nh, status, s, buf, seq)
+ warn("netlink: Unexpected response message");
- nl_foreach(nh, status, s, buf, seq)
- warn("netlink: Unexpected response message");
+ if (!ret && status < 0)
+ ret = status;
+ }
- return status;
+ return ret;
}
/**
diff --git a/pasta.c b/pasta.c
index e8883bd..1142f03 100644
--- a/pasta.c
+++ b/pasta.c
@@ -303,10 +303,15 @@ void pasta_ns_conf(struct ctx *c)
strerror(-rc));
if (c->pasta_conf_ns) {
+ unsigned int flags = IFF_UP;
+
if (c->mtu != -1)
nl_link_set_mtu(nl_sock_ns, c->pasta_ifi, c->mtu);
- nl_link_set_flags(nl_sock_ns, c->pasta_ifi, IFF_UP, IFF_UP);
+ if (c->ifi6) /* Avoid duplicate address detection on link up */
+ flags |= IFF_NOARP;
+
+ nl_link_set_flags(nl_sock_ns, c->pasta_ifi, flags, flags);
if (c->ifi4) {
if (c->ip4.no_copy_addrs) {
@@ -353,6 +358,10 @@ void pasta_ns_conf(struct ctx *c)
strerror(-rc));
}
+ /* We dodged DAD: re-enable neighbour solicitations */
+ nl_link_set_flags(nl_sock_ns, c->pasta_ifi,
+ 0, IFF_NOARP);
+
if (c->ip6.no_copy_addrs) {
rc = nl_addr_set(nl_sock_ns, c->pasta_ifi,
AF_INET6, &c->ip6.addr, 64);
--
@@ -303,10 +303,15 @@ void pasta_ns_conf(struct ctx *c)
strerror(-rc));
if (c->pasta_conf_ns) {
+ unsigned int flags = IFF_UP;
+
if (c->mtu != -1)
nl_link_set_mtu(nl_sock_ns, c->pasta_ifi, c->mtu);
- nl_link_set_flags(nl_sock_ns, c->pasta_ifi, IFF_UP, IFF_UP);
+ if (c->ifi6) /* Avoid duplicate address detection on link up */
+ flags |= IFF_NOARP;
+
+ nl_link_set_flags(nl_sock_ns, c->pasta_ifi, flags, flags);
if (c->ifi4) {
if (c->ip4.no_copy_addrs) {
@@ -353,6 +358,10 @@ void pasta_ns_conf(struct ctx *c)
strerror(-rc));
}
+ /* We dodged DAD: re-enable neighbour solicitations */
+ nl_link_set_flags(nl_sock_ns, c->pasta_ifi,
+ 0, IFF_NOARP);
+
if (c->ip6.no_copy_addrs) {
rc = nl_addr_set(nl_sock_ns, c->pasta_ifi,
AF_INET6, &c->ip6.addr, 64);
--
2.43.0
next prev parent reply other threads:[~2024-08-16 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:39 [PATCH v3 0/7] Prevent DAD for link-local addresses in containers Stefano Brivio
2024-08-16 7:39 ` [PATCH v3 1/7] netlink: Fix typo in function comment for nl_addr_get() Stefano Brivio
2024-08-16 7:39 ` [PATCH v3 2/7] netlink, pasta: Split MTU setting functionality out of nl_link_up() Stefano Brivio
2024-08-16 7:39 ` [PATCH v3 3/7] netlink, pasta: Turn nl_link_up() into a generic function to set link flags Stefano Brivio
2024-08-16 7:39 ` [PATCH v3 4/7] netlink, pasta: Disable DAD for link-local addresses on namespace interface Stefano Brivio
2024-08-17 7:59 ` David Gibson
2024-08-17 8:37 ` Stefano Brivio
2024-08-17 8:41 ` Stefano Brivio
2024-08-16 7:39 ` [PATCH v3 5/7] netlink, pasta: Fetch link-local address from namespace interface once it's up Stefano Brivio
2024-08-16 7:39 ` Stefano Brivio [this message]
2024-08-16 7:39 ` [PATCH v3 7/7] netlink: Fix typo in function comment for nl_addr_set() Stefano Brivio
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=20240816073918.1483136-7-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).