@@TallPaulTech As a basic example, it is what you would use as an ipv6-only ISP wanting to support ipv6-only customers, while still providing access to ipv4-only resources. Not necessarily useful in your case, but in the case of mobile carriers, many are already ipv6-only. Consequently, there is solid support for 464xlat on iOS, Android, and MacOS. That said, I have no idea where Windows and Linux stand w/ support. Biggest benefit IMO is that it lets you use apps which only support ipv4 in your ipv6 network, without a huge amount of hackery. ipv4-limited apps still believe they are on an ipv4 network.
That's what I mean... let me rephrase that. Why would I in particular want to play around with that when I have everything I need? I think somebody else can do that video :)
now do 464xlat, don't disappoint me mate.
jk, quick and simple tutorials, all the people need to get on the ipv6 train
Why 464xlat?
@@TallPaulTech As a basic example, it is what you would use as an ipv6-only ISP wanting to support ipv6-only customers, while still providing access to ipv4-only resources. Not necessarily useful in your case, but in the case of mobile carriers, many are already ipv6-only. Consequently, there is solid support for 464xlat on iOS, Android, and MacOS. That said, I have no idea where Windows and Linux stand w/ support.
Biggest benefit IMO is that it lets you use apps which only support ipv4 in your ipv6 network, without a huge amount of hackery. ipv4-limited apps still believe they are on an ipv4 network.
That's what I mean... let me rephrase that. Why would I in particular want to play around with that when I have everything I need?
I think somebody else can do that video :)
You get a /48 from your ISP and used the first /96 from the top /64 as your NAT64 prefix?
Ew gross 🤮 IPv6. I prefer to be able to read my IPs. Lol jp, I enjoy your content ❤.
Get your husband to read them to you then