From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/4] Use inany addresses through port forwarding configuration
Date: Wed, 25 Sep 2024 19:39:15 +0200 [thread overview]
Message-ID: <20240925193915.3defebab@elisabeth> (raw)
In-Reply-To: <20240920041244.593192-1-david@gibson.dropbear.id.au>
On Fri, 20 Sep 2024 14:12:40 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> We use inany addresses, which can represent either an IPv4 or IPv6
> address heavily through the flow table. However, for the
> configuration of port forwarding: both the command line parsing and
> initialization of listening sockets, we use address family+(void *)
> pairs instead.
>
> Using inany through these paths makes them slightly neater now, but
> more importantly will make it easier to add more robust tracking of
> forwarding configuration.
>
> David Gibson (4):
> udp: Don't attempt to get dual-stack sockets in nonsensical cases
> util, pif: Replace sock_l4() with pif_sock_l4()
> tcp, udp: Make {tcp,udp}_sock_init() take an inany address
> inany: Add inany_pton() helper
Applied, sorry for the delay.
--
Stefano
prev parent reply other threads:[~2024-09-25 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 4:12 [PATCH 0/4] Use inany addresses through port forwarding configuration David Gibson
2024-09-20 4:12 ` [PATCH 1/4] udp: Don't attempt to get dual-stack sockets in nonsensical cases David Gibson
2024-09-20 4:12 ` [PATCH 2/4] util, pif: Replace sock_l4() with pif_sock_l4() David Gibson
2024-09-20 4:12 ` [PATCH 3/4] tcp, udp: Make {tcp,udp}_sock_init() take an inany address David Gibson
2024-09-20 4:12 ` [PATCH 4/4] inany: Add inany_pton() helper David Gibson
2024-09-25 17:39 ` Stefano Brivio [this message]
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=20240925193915.3defebab@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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).