Consider a UDP port on IPv6

[vanrein]

Consider a UDP port on IPv6

[vanrein]

This is perhaps the simplest approach to mix 6bed4 with NAT64. Use an option like -n <ip6addr> for the NAT64-translated format. Internally, 6bed4router has a UDP socket and so the internal structure does not change, other than this overridden address binding. The value in -l is used to construct an LLADDR, so it must be given in either case.

[vanrein]

It is also a though to allow destination address renaming before applying NAT64, in a firewall rule. This gives rise to a slightly more general concept of -x <ip4addr|ip6addr> of a translated (xlated) address. This would be the address for UDP port binding, in spite of the -l <v4addr> binding that sets the externally observed address for the 6bed4 service.

See also http://internetwide.org/blog/2020/05/31/net-1-ipv4-backward-compat.html for a general idea, and/or the
network design for the hosting stack of the InternetWide Architecture.

[vanrein]

The IPv6 binding was dropped, as it added nothing much. Instead, we phish 6bed4 traffic out of a flow passing by, and redirect to 127.0.0.1:<port> and specify this assumption as -x <port>. This changes what UDP address/port combination the 6bed4router binds to.

Resolved in 25cfeb5 in branch master.