Home internet service IPv6 traffic is all filtered even when using a Netgear LTE router. No port forwarding. Plz fix!

After going through all these issues and trying to figure out why T-Mobile work this way (frequent IP changes, no bridge mode - read carrier UE lock, random latency discrepancies between native ipv6 and ipv4), and I have to say this thread explains a lot. 

Also, there is no such thing as "IPv6 ONLY network" for companies providing DIA. Sure, parts of them can be IPv6 only but you still need to route IPv4 from NAT64 gateways for resources only available on IPv4, it won't go away anytime soon. There are also customers business customers you need to take care of… So, you still maintain two separate networks, the difference is that the IPv4 scope becomes more narrow and easier to maintain.  

Time will say if T-Mobile is a winner going with 464XLAT but it for sure affects their service offerings today, functionality and compatibility wise. 

We talked about shortages of IPs etc. but it looks like Verizon Wireless handled it just fine, with 5G Home Internet getting routable IPv4 addresses, CPEs with bridge mode for both, mmWave and C-Band. Cell phones using true dual stack (CGNAT/IPv6), which seems appropriate.