From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH 1/3] conf: Consistency check between configured IPv4 netmask and gateway
Date: Thu, 3 Nov 2022 14:17:57 +1100 [thread overview]
Message-ID: <Y2My5SiIcNnNbD6t@yekko> (raw)
In-Reply-To: <20221102230443.377446-2-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]
On Thu, Nov 03, 2022 at 12:04:41AM +0100, Stefano Brivio wrote:
> Seen in a Google Compute Engine environment with a machine configured
> via cloud-init-dhcp, while testing Podman integration for pasta: the
> assigned address has a /32 netmask, and there's a default route,
> which can be added on the host because there's another route, also
> /32, pointing to the default gateway.
I'm afraid I'm having trouble getting a good picture of the situation
from this description. I think an actual example with addresses would
make it much clearer.
> This is not a valid configuration as far as I can tell: if the
> address is configured as /32, it shouldn't be used to reach a gateway
> outside its derived netmask. However, Linux allows that, and
> everything works.
>
> The problem comes when pasta --config-net sources address and default
> route from the host, and it can't configure the route in the target
> namespace because the gateway is invalid.
>
> Sourcing more routes than just the default is doable, but probably
> undesirable: pasta users want to provide connectivity to a container,
> not reflect exactly whatever trickery is configured on the host.
>
> Add a consistency check: if the configured default gateway is not
> reachable, shrink the given netmask until we can reach it.
Hmm... this isn't merely a check, it's changing an otherwise
configured value.
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> conf.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/conf.c b/conf.c
> index 90214f5..5b88547 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -562,6 +562,10 @@ static unsigned int conf_ip4(unsigned int ifi,
> ip4->mask = 0xffffffff;
> }
>
> + /* Mask consistency check: ensure we can reach the default gateway */
Since this is to handle a very weird situation, we absolutely need a
more detailed comment here.
> + while ((ip4->addr & ip4->mask) != (ip4->gw & ip4->mask))
> + ip4->mask = htonl(ntohl(ip4->mask) << 1);
> +
> memcpy(&ip4->addr_seen, &ip4->addr, sizeof(ip4->addr_seen));
>
> if (MAC_IS_ZERO(mac))
--
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:[~2022-11-03 3:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 23:04 [PATCH 0/3] Fixes and workarounds for pasta with Podman in Google Cloud Stefano Brivio
2022-11-02 23:04 ` [PATCH 1/3] conf: Consistency check between configured IPv4 netmask and gateway Stefano Brivio
2022-11-03 3:17 ` David Gibson [this message]
2022-11-03 6:39 ` Stefano Brivio
2022-11-02 23:04 ` [PATCH 2/3] conf: Split the notions of read DNS addresses and offered ones Stefano Brivio
2022-11-03 3:37 ` David Gibson
2022-11-03 6:42 ` Stefano Brivio
2022-11-02 23:04 ` [PATCH 3/3] udp: Check for answers to forwarded DNS queries before handling local redirects Stefano Brivio
2022-11-03 3:42 ` David Gibson
2022-11-03 6:42 ` Stefano Brivio
2022-11-05 1:19 ` David Gibson
2022-11-06 22:22 ` Stefano Brivio
2022-11-07 1:08 ` David Gibson
2022-11-07 9:51 ` Stefano Brivio
2022-11-08 5:51 ` David Gibson
2022-11-08 6:22 ` Stefano Brivio
2022-11-10 4:30 ` David Gibson
2022-11-03 3:13 ` [PATCH 0/3] Fixes and workarounds for pasta with Podman in Google Cloud David Gibson
2022-11-03 6:36 ` 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=Y2My5SiIcNnNbD6t@yekko \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
--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).