Re: [44net] IPv6, for authentication with IPSEC

Yes there are two ways I can think of to do this, as long as you're allocated a /64 from your IPv6 provider it is simple to map as follows: *Most basic (1:1 mapping IPv4 to IPv6)* *Provider:* 2001:19f0:5c01:10f4::/64 *Mapping:* 44.50.1.1 -> 2001:19f0:5c01:10f4:44:50:1:1/128 That wastes quite a lot of IPv6 space, but it's easy to do. *More advanced (Mapping IPv4 to IPv6 subnet)* Another way is directly converting the hex of the IPv4 address: *Provider:* 2001:19f0:5c01:10f4::/64 *Mapping:* 44.50.1.1 -> 2001:19f0:5c01:10f4:2C32:0101::/96 Definitions: 2C = 44 32 = 50 01 = 01 01 = 01 Doing this gives you a /96 per IPv4 address, so up to 4,294,967,296 IPv6 hosts per IPv4 address. All of this requires native IPv6 connectivity, either through something like Tunnelbroker or from your hosting provider. I'm doing this mapping on my Vultr VM where I am BGP announcing my AMPR /24 to begin with. The ranges are not "portable" but I'm not sure I see the requirement to take an IPv6 range with me when I move from one ISP to another since everything in IPv6 space should be done with DNS and not hard coded IPs. Hope that helps, Shawn (KC0AKY) Shawn Garringer (sgarringer(a)gmail.com) On Sat, Jul 28, 2018 at 11:37 AM, Robert Keyes <robertwkeyes(a)gmail.com> wrote: > I've read the FAQ, and see there is no equivalent IPv6 for our lovely 44/8. > My question is, can we utilize IPv6 with our IPv4 address embedded in it? > The reason > I want to be able to easily utilize message authentication with IPSEC AH. > > 73, > N1YRK >