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: [PATCH v2 3/9] conf: Refactor conf_print() for multi-address support
Date: Mon, 19 Jan 2026 18:25:59 +1100 [thread overview]
Message-ID: <aW3ch-zkZTQHVgqk@zatzit> (raw)
In-Reply-To: <20260118221612.2115386-4-jmaloy@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3995 bytes --]
On Sun, Jan 18, 2026 at 05:16:06PM -0500, Jon Maloy wrote:
> As a preparation for multiple address support, we refactor the
> conf_print() function to handle this properly.
>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> ---
> conf.c | 78 +++++++++++++++++++++++++++++++++-------------------------
> 1 file changed, 45 insertions(+), 33 deletions(-)
>
> diff --git a/conf.c b/conf.c
> index 9fc5dca..3ecd1a0 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -1199,20 +1199,28 @@ static void conf_print(const struct ctx *c)
> buf4, sizeof(buf4)));
>
> if (!c->no_dhcp) {
> - uint32_t mask;
> -
> - mask = htonl(0xffffffff <<
> - (32 - c->ip4.addrs[0].prefix_len));
> -
> - info("DHCP:");
> - info(" assign: %s",
> - inet_ntop(AF_INET, inany_v4(&c->ip4.addrs[0].addr),
> - buf4, sizeof(buf4)));
> - info(" mask: %s",
> - inet_ntop(AF_INET, &mask, buf4, sizeof(buf4)));
> - info(" router: %s",
> - inet_ntop(AF_INET, &c->ip4.guest_gw,
> - buf4, sizeof(buf4)));
> + for (i = 0; i < c->ip4.addr_count; i++) {
> + const struct inany_addr_entry *e;
> + uint32_t mask;
> +
> + e = &c->ip4.addrs[i];
> + if (!(e->flags & INANY_ADDR_CONFIGURED) &&
> + c->ip4.addr_count > 1)
> + continue;
This doesn't seem right - addresses taken from the host will also be
used for DHCP.
> +
> + mask = htonl(0xffffffff << (32 - e->prefix_len));
> +
> + info("DHCP:");
> + info(" assign: %s",
> + inet_ntop(AF_INET, inany_v4(&e->addr),
> + buf4, sizeof(buf4)));
> + info(" mask: %s",
> + inet_ntop(AF_INET, &mask, buf4, sizeof(buf4)));
> + info(" router: %s",
> + inet_ntop(AF_INET, &c->ip4.guest_gw,
> + buf4, sizeof(buf4)));
> + break;
> + }
> }
>
> for (i = 0; !IN4_IS_ADDR_UNSPECIFIED(&c->ip4.dns[i]); i++) {
> @@ -1230,30 +1238,34 @@ static void conf_print(const struct ctx *c)
> }
>
> if (c->ifi6) {
> + bool do_slaac = !c->no_ndp || !c->no_dhcpv6;
> +
> if (!IN6_IS_ADDR_UNSPECIFIED(&c->ip6.map_host_loopback))
> info(" NAT to host ::1: %s",
> inet_ntop(AF_INET6, &c->ip6.map_host_loopback,
> buf6, sizeof(buf6)));
>
> - if (!c->no_ndp && !c->no_dhcpv6)
> - info("NDP/DHCPv6:");
> - else if (!c->no_dhcpv6)
> - info("DHCPv6:");
> - else if (!c->no_ndp)
> - info("NDP:");
> - else
> - goto dns6;
> -
> - info(" assign: %s",
> - inet_ntop(AF_INET6, &c->ip6.addrs[0].addr.a6,
> - buf6, sizeof(buf6)));
> - info(" router: %s",
> - inet_ntop(AF_INET6, &c->ip6.guest_gw, buf6, sizeof(buf6)));
> - info(" our link-local: %s",
> - inet_ntop(AF_INET6, &c->ip6.our_tap_ll,
> - buf6, sizeof(buf6)));
> -
> -dns6:
> + if (do_slaac) {
> + if (!c->no_ndp && !c->no_dhcpv6)
> + info("NDP/DHCPv6:");
> + else if (!c->no_dhcpv6)
> + info("DHCPv6:");
> + else
> + info("NDP:");
> +
> + for (i = 0; i < c->ip6.addr_count; i++) {
> + info(" assign: %s",
> + inet_ntop(AF_INET6, &c->ip6.addrs[i].addr.a6,
> + buf6, sizeof(buf6)));
There's an inany_ntop()... if you're going to use inany_ntop() for
IPv6 only addresses you might at least use the helper functions
already implemented for it.
> + }
> + info(" router: %s",
> + inet_ntop(AF_INET6, &c->ip6.guest_gw,
> + buf6, sizeof(buf6)));
> + info(" our link-local: %s",
> + inet_ntop(AF_INET6, &c->ip6.our_tap_ll,
> + buf6, sizeof(buf6)));
> + }
> +
> for (i = 0; !IN6_IS_ADDR_UNSPECIFIED(&c->ip6.dns[i]); i++) {
> if (!i)
> info("DNS:");
> --
> 2.52.0
>
--
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 --]
next prev parent reply other threads:[~2026-01-19 8:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 22:16 [PATCH v2 0/9] Introduce multiple addresses Jon Maloy
2026-01-18 22:16 ` [PATCH v2 1/9] conf: Support CIDR notation for -a/--address option Jon Maloy
2026-01-19 5:02 ` David Gibson
2026-01-21 8:15 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 2/9] ip: Introduce unified multi-address data structures Jon Maloy
2026-01-19 7:22 ` David Gibson
2026-01-21 13:02 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 3/9] conf: Refactor conf_print() for multi-address support Jon Maloy
2026-01-19 7:25 ` David Gibson [this message]
2026-01-21 13:02 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 4/9] fwd: Check all configured addresses in guest accessibility functions Jon Maloy
2026-01-19 7:29 ` David Gibson
2026-01-18 22:16 ` [PATCH v2 5/9] arp: Check all configured addresses in ARP filtering Jon Maloy
2026-01-19 8:28 ` David Gibson
2026-01-18 22:16 ` [PATCH v2 6/9] conf: Allow multiple -a/--address options per address family Jon Maloy
2026-01-19 8:41 ` David Gibson
2026-01-18 22:16 ` [PATCH v2 7/9] pasta: Unify address configuration paths using address array Jon Maloy
2026-01-18 22:16 ` [PATCH v2 8/9] ip: Track observed guest IPv4 addresses in unified " Jon Maloy
2026-01-18 22:16 ` [PATCH v2 9/9] ip: Track observed guest IPv6 " 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=aW3ch-zkZTQHVgqk@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).