public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: sbrivio@redhat.com, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [RFC  08/12] netlink: Subscribe to route changes in namespace
Date: Mon, 15 Dec 2025 21:38:08 +1100	[thread overview]
Message-ID: <aT_lENnpQx1epiCH@zatzit> (raw)
In-Reply-To: <20251215015441.887736-9-jmaloy@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3600 bytes --]

On Sun, Dec 14, 2025 at 08:54:37PM -0500, Jon Maloy wrote:
> We add subscriptions to RTMGRP_IPV4_ROUTE and RTMGRP_IPV6_ROUTE, so
> that we receive notifications when routes change on the namespace
> interface.

No, we'd need to listen in the host netns, so we can transfer those
route changes to the guest netns.

> When default routes change on the pasta interface, we update guest_gw
> (and our_tap_addr for IPv4) to reflect the new gateway. This handles
> both routes propagated from the host and routes configured manually
> by the user inside the namespace.
> 
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> ---
>  netlink.c | 49 ++++++++++++++++++++++++++++++++++++++++++++++---
>  1 file changed, 46 insertions(+), 3 deletions(-)
> 
> diff --git a/netlink.c b/netlink.c
> index 7492f17..a8d3116 100644
> --- a/netlink.c
> +++ b/netlink.c
> @@ -195,7 +195,7 @@ static bool nl_addr6_add(struct ctx *c, const struct in6_addr *addr,
>  	idx = c->ip6.addr_count++;
>  	c->ip6.addrs[idx].addr = *addr;
>  	c->ip6.addrs[idx].prefix_len = prefix_len;
> -	c->ip6.addrs[idx].permanent = 0;
> +	c->ip6.addrs[idxyes].permanent = 0;

Um... what?

>  	return true;
>  }
>  
> @@ -359,6 +359,49 @@ static void nl_linkaddr_msg_read(struct ctx *c, const struct nlmsghdr *nh)
>  				}
>  			}
>  		}
> +		return;
> +	}
> +
> +	if (nh->nlmsg_type == RTM_NEWROUTE || nh->nlmsg_type == RTM_DELROUTE) {
> +		bool is_new = (nh->nlmsg_type == RTM_NEWROUTE);
> +		const struct rtmsg *rtm = NLMSG_DATA(nh);
> +		struct rtattr *rta = RTM_RTA(rtm);
> +		size_t na = RTM_PAYLOAD(nh);
> +		unsigned int oif = 0;
> +		void *gw = NULL;
> +
> +		/* Only interested in default routes (dst_len == 0) */

No, we copy non-default routes as well.

> +		if (rtm->rtm_dst_len != 0)
> +			return;
> +
> +		for (; RTA_OK(rta, na); rta = RTA_NEXT(rta, na)) {
> +			if (rta->rta_type == RTA_GATEWAY)
> +				gw = RTA_DATA(rta);
> +			else if (rta->rta_type == RTA_OIF)
> +				oif = *(unsigned int *)RTA_DATA(rta);
> +		}
> +
> +		if (!gw)

We copy non-gateway routes too (and may well need to, because there's
typically at least one non-gw route needed to reach the gateway
itself).

> +			return;
> +
> +		/* Only handle our pasta interface */
> +		if (c->mode != MODE_PASTA || oif != c->pasta_ifi)
> +			return;

Again, we need to be listening in the host netns, so pasta_ifi makes
no sense.

> +
> +		if (rtm->rtm_family == AF_INET) {
> +			if (is_new) {
> +				c->ip4.guest_gw = *(struct in_addr *)gw;
> +				c->ip4.our_tap_addr = c->ip4.guest_gw;
> +			} else {
> +				c->ip4.guest_gw = (struct in_addr){ 0 };
> +				c->ip4.our_tap_addr = (struct in_addr){ 0 };
> +			}
> +		} else if (rtm->rtm_family == AF_INET6) {
> +			if (is_new)
> +				c->ip6.guest_gw = *(struct in6_addr *)gw;
> +			else
> +				c->ip6.guest_gw = (struct in6_addr){ 0 };
> +		}
>  	}
>  }
>  
> @@ -398,8 +441,8 @@ void nl_linkaddr_notify_handler(struct ctx *c)
>  static int nl_linkaddr_init_do(void *arg)
>  {
>  	struct sockaddr_nl addr = { .nl_family = AF_NETLINK,
> -		.nl_groups = RTMGRP_LINK | RTMGRP_IPV4_IFADDR |
> -			     RTMGRP_IPV6_IFADDR };
> +		.nl_groups = RTMGRP_LINK | RTMGRP_IPV4_IFADDR | RTMGRP_IPV6_IFADDR |
> +			     RTMGRP_IPV4_ROUTE | RTMGRP_IPV6_ROUTE };
>  
>  	if (arg)
>  		ns_enter((struct ctx *)arg);
> -- 
> 2.51.1
> 

-- 
David Gibson (he or they)	| 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 --]

  reply	other threads:[~2025-12-15 10:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15  1:54 [RFC 00/12] Support for multiple address and late binding Jon Maloy
2025-12-15  1:54 ` [RFC 01/12] ip: Introduce multi-address data structures for IPv4 and IPv6 Jon Maloy
2025-12-15  9:40   ` David Gibson
2025-12-15 22:05     ` Jon Maloy
2025-12-16  1:58       ` Jon Maloy
2025-12-16  3:14         ` David Gibson
2025-12-15  9:46   ` David Gibson
2025-12-15  1:54 ` [RFC 02/12] ip: Add ip4_default_prefix_len() helper function for class-based prefix Jon Maloy
2025-12-15  9:41   ` David Gibson
2025-12-15  1:54 ` [RFC 03/12] conf: Allow multiple -a/--address options per address family Jon Maloy
2025-12-15  9:53   ` David Gibson
2025-12-15  1:54 ` [RFC 04/12] conf: Apply -n/--netmask to most recently added address Jon Maloy
2025-12-15  9:54   ` David Gibson
2025-12-15 22:43     ` Jon Maloy
2025-12-15  1:54 ` [RFC 05/12] fwd: Check all configured addresses in guest accessibility functions Jon Maloy
2025-12-15 10:06   ` David Gibson
2025-12-15  1:54 ` [RFC 06/12] arp: Check all configured addresses in ARP filtering Jon Maloy
2025-12-15 10:07   ` David Gibson
2025-12-15  1:54 ` [RFC 07/12] netlink: Subscribe to link/address changes in namespace Jon Maloy
2025-12-15 10:32   ` David Gibson
2025-12-15 23:25     ` Jon Maloy
2025-12-16  3:21       ` David Gibson
2025-12-15  1:54 ` [RFC 08/12] netlink: Subscribe to route " Jon Maloy
2025-12-15 10:38   ` David Gibson [this message]
2025-12-15  1:54 ` [RFC 09/12] netlink: Add host-side monitoring for late template interface binding Jon Maloy
2025-12-15  1:54 ` [RFC 10/12] netlink: Add host-side route monitoring and propagation Jon Maloy
2025-12-15  1:54 ` [RFC 11/12] netlink: Prevent host route events from overwriting guest-configured gateway Jon Maloy
2025-12-15  1:54 ` [RFC 12/12] netlink: Rename tap interface when late binding discovers template name Jon Maloy

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=aT_lENnpQx1epiCH@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=dgibson@redhat.com \
    --cc=jmaloy@redhat.com \
    --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).