Re: [PATCH 0/4] Use inany addresses through port forwarding configuration

On Fri, 20 Sep 2024 14:12:40 +1000
David Gibson <david(a)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