Before CGNAT was applied I could setup ipv6 in my router, I believe it was named 6to4. After CGNAT was applied that was no longer possible, so now I don't have public ipv4 and no ipv6 access from my isp anymore.

41:34 Europe: well, we put it in the group, that's the really clean option

I've been using T-Mobile's 5G home gateway, and for most of what I do, it works well. I've used it for many Zoom calls. AFAIK, they have all been IPv4, so the 464 XLAT has done its job. That said, I wonder if T-Mobile didn't make a big show of creating an IPv6 only last mile in a communications system that doesn't even look at the level 3 address just to get a corner on the network engineer market.

Thank you so much. This was really detailed and informative.

Thank you

This was very TITillating.

Really good! Thanks a lot for uploading!

IPv6 is a dog ugly protocol that is breaking internet functionality and is helping cloud nonsense to take away control from end users. It sucks and I hate it!

Good presentation with some really useful information in coming up with a ipv6 implementation design.

Nice information .. I was looking for CGN

I really enjoy the info!

Awesome video!

Thanks for the upload, lots of good info!

What are the names of the first guy and the lady that follows?

The best

oh.. got a new machine... net.ipv6.conf.all.disable_ipv6 = 1 done.

This was a very comprehensive review that any carrier (as well as enterprises) should review before the go V6. Well done.

Chris sounds like a Turkey.

bravo!

Nice Job

Excellent

Unfortunately Apple's IPv6-only 3GPP support in iOS requires the mobile operator to have a separate tethering APN (as T-Mobile does). There is no other way to get IPv4 connectivity to IPv4-only tethered devices. Since there is no 464XLAT interface in iOS it is not possible to provide IPv4 connectivity on a tethering LAN via an IPv6-only APN connection. There are two operational issues with this for providers. 1) Separate APN providers like T-Mobile have the problem of not being able to provide IPv6 on their tethering LAN without also making their tethering APN dual-stack which is counter to the objective of IPv6-only APNs. 2) Operators with a combined handset and tethering APN cannot provide IPv4 tethering with an IPv6-only APN due to the missing 464XLAT function.

Great to see you up there Stephan! Go V6!

Fantastic overview of those organizations with a controlling interest in IoT protocol selection. Very well presented by an engaging and articulate speaker.

I am preparing for the 200-120 CCNA exam and even though I know that this is out of scope for the CCNA exam, I was very curious and I needed to know what the Solicited-Node address was exactly.Anyway, I spent half the day looking for something or someone to show me the answer with no luck at all... until I came across this video that is... thanks a lot!!!! :O)

The name is spelt wrong, it is Joe Klein.