From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] netlink: Drop point-to-point peer information when we copy addresses
Date: Tue, 23 Apr 2024 11:02:43 +1000 [thread overview]
Message-ID: <ZicIs_U6KMwaqyH6@zatzit> (raw)
In-Reply-To: <20240411221800.548178-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
On Fri, Apr 12, 2024 at 12:18:00AM +0200, Stefano Brivio wrote:
> If the template host interface is of type tun, and it's configured
> with a point-to-point peer address (that's what happens for example
> with openvpn and '--topology net30'), pasta will copy the peer
> information onto the namespace interface.
>
> But the namespace interface is not actually a point-to-point tunnel,
> and we won't resolve the peer address via ARP either, so we have
> to drop this information to get the expected behaviour (traffic
> regularly sent over our tap interface).
>
> Link: https://github.com/containers/podman/issues/22320
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> netlink.c | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/netlink.c b/netlink.c
> index 89c0641..73aaa4b 100644
> --- a/netlink.c
> +++ b/netlink.c
> @@ -792,8 +792,8 @@ int nl_addr_dup(int s_src, unsigned int ifi_src,
>
> seq = nl_send(s_src, &req, RTM_GETADDR, NLM_F_DUMP, sizeof(req));
> nl_foreach_oftype(nh, status, s_src, buf, seq, RTM_NEWADDR) {
> + struct rtattr *rta, *rta_local = NULL;
> struct ifaddrmsg *ifa;
> - struct rtattr *rta;
> size_t na;
>
> ifa = (struct ifaddrmsg *)NLMSG_DATA(nh);
> @@ -804,12 +804,33 @@ int nl_addr_dup(int s_src, unsigned int ifi_src,
>
> ifa->ifa_index = ifi_dst;
>
> + for (rta = IFA_RTA(ifa), na = IFA_PAYLOAD(nh); RTA_OK(rta, na);
> + rta = RTA_NEXT(rta, na)) {
> + if (rta->rta_type == IFA_LOCAL) {
> + rta_local = rta;
> + break;
> + }
> + }
> +
> for (rta = IFA_RTA(ifa), na = IFA_PAYLOAD(nh); RTA_OK(rta, na);
> rta = RTA_NEXT(rta, na)) {
> /* Strip label and expiry (cacheinfo) information */
> if (rta->rta_type == IFA_LABEL ||
> rta->rta_type == IFA_CACHEINFO)
> rta->rta_type = IFA_UNSPEC;
> +
> + /* Different values for IFA_ADDRESS and IFA_LOCAL mean
> + * that IFA_LOCAL is the locally configured address, and
> + * IFA_ADDRESS is the peer address for a point-to-point
> + * interface. But our namespace interface isn't really a
> + * point-to-point tunnel, and we can't resolve that peer
> + * address via ARP: simply drop it, and keep the local
> + * address.
Could we just unconditionally remove IFA_ADDRESS properties (by
setting them to IFA_UNSPEC)? That we we could avoid having two passes
through the attributes.
> + */
> + if (rta->rta_type == IFA_ADDRESS && rta_local) {
> + memcpy(RTA_DATA(rta), RTA_DATA(rta_local),
> + RTA_PAYLOAD(rta));
> + }
> }
>
> rc = nl_do(s_dst, nh, RTM_NEWADDR,
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-23 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 22:18 [PATCH] netlink: Drop point-to-point peer information when we copy addresses Stefano Brivio
2024-04-23 1:02 ` David Gibson [this message]
2024-04-23 8:09 ` 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=ZicIs_U6KMwaqyH6@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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).