yeah... v6 passthrough "works" with my Asus.
Native/delegation appeared to work at first, but irt crapped out when I tried to run a v6 compliance test like 30 seconds later.
I say passthrough "works" more so because of client side issues then network issues.
DNS can be sluggish (at least in Windoze), causing your browsers to fall back to v4 lookups. But if you are avoiding that screwy slow DNS fall back scenario (like on your phone), it works.
Just frustrating. They should have known better. Sometimes it feels like the DOCSIS beta days. You can see there should be a better way to do things... but it just is not happening.
yeah... v6 passthrough "works" with my Asus.
Native/delegation appeared to work at first, but irt crapped out when I tried to run a v6 compliance test like 30 seconds later.
I say passthrough "works" more so because of client side issues then network issues.
DNS can be sluggish (at least in Windoze), causing your browsers to fall back to v4 lookups. But if you are avoiding that screwy slow DNS fall back scenario (like on your phone), it works.
Just frustrating. They should have known better. Sometimes it feels like the DOCSIS beta days. You can see there should be a better way to do things... but it just is not happening.
Phones on T-Mobile use DNS64. So, you will always get an IPv6 response and address from DNS on a phone. This is not the case with TMHI. You will only get an IPv6 address if there is a AAAA registration for the host. For me, DNS is working properly with TMHI. My clients use IPv6 for sites and services that support IPv6. If I completely turn off IPv4 on a client, I still have connectivity to those sites and services. I even tested using DNS64 servers and turned off IPv4 and I had no issues with apps or service except for the T-Mobile digits app.
Oh I could run a v6 DNS query from the command line fine and all.
It was just too slow.
My phone got along with it just fine. It was the Winblows and $ony platforms that didn't behave well.
By default, some browsers will fall back to a v4 query if the v6 takes too long. I just didn't feel like farting around with them to figure out how to override or otherwise tweak the timeout limit for the query (not to mention Microsoft's screwy stuff). Most everything I do is still reliant on v4 addressing and all, so wasn't up for the headache.
That is another part of the problem... way too many applications are not geared to use V6 properly yet.
I just want to use IPv6 passthrough (bridge mode) so I can connect my external router. I don’t need port forwarding or inbound access. I called before ordering the service and they told me this was possible — but I guess they lied.
It sounds to me like you want IPv6 delegation, not passthrough. In pass through your router behind theirs actually acts as a bridge. In delegation their router accepts dhcpv6 requests and then delegates subnets to your router. TMHI supports passthrough just fine, unfortunately they do not support delegation. They want to bundle prefixes to simplify their network and that complicates delegation, though there are plenty of both standard and nonstandard solutions that work to fix that and aren’t even mutually incompatible. Ie they could implement both RFC 6603, prefix shortening and multi /64 prefix delegation all on the same device. All would solve the issue and none would interfere with each other.
I solved my specific problem, but it’s not a generic solution for all. For those that are interested, here’s how I solved the double-NAT issue and got VOIP to work.
I got the TMHI trashcan gateway to use as a secondary WAN connection (my primary is Cox cable). I’m using a Peplink Balance 20 router, which allows dual WAN connections.
Peplink also offers a service called SpeedFusion Cloud, which is basically a VPN. However, it also offers advantages like WAN smoothing and the ability to selectively route your traffic over both WANs simultaneously. This means you can pull the plug on one WAN and someone on a VOIP call won’t even notice a problem (I verified this by actually doing it).
Since SpeedFusion is an outgoing connection that is initiated by the router, it doesn’t care if it has a public IP. It works fine with the private IP address assigned by the T-Mobile gateway.
This solution is a variation on using a VPN that others have mentioned. The cost of the SpeedFusion cloud service is as low as $20 for six months of service. Right now I’m only routing my VOIP traffic through it, since our VOIP service is critical and it is the only service that appears to be affected by double-NAT issues. Also, it doesn’t make sense to pay for the extra bandwidth just to stream Netflix over a redundant connection. However, it might make sense to route business-critical Zoom calls this way.
For anyone using a Peplink router, this might be a good solution. Now that I can split my traffic across two providers, I’m considering cutting the speed on my Cox service. The cost savings by doing this will just about pay for the TMHI service and the small extra cost of the Speedfusion Cloud service. This means I will have fully-redundant internet service for about the same cost as my original cable service.
This post I found seems related and comments have been disabled. (link below) I have had my gateway for three days now and just attempting the gateway settings and noticed port forwarding is missing. It looks like this has been an issue for some time and there are no plans to address it. So we were sold home internet, but got a wifi hotspot. I am sad that my only option now is to return the unit to T-Mobile and pay triple what T-Mobile was offering to get the same speeds with Cox. :-(
I am using a generic LTE modem here connected to T-Mobile as a PFSense backup connection.
This is a SOHO Wireless with Firewall AP with an RJ11 (phone jack), 4 network ports and WLAN.
LTE only.
Testing right now via WLAN direct to LTE modem and VPN works fine here. IE:
1 - OpenVPN to another PFSense server
2 - IPSec VPN to same server
3 - Wireguard VPN via PIA from my laptop via LTE modem and only see an IPv4 address
I cannot bridge the WAN to the LAN port so PFSense connecting to LAN port.
If I do a “what is my IP” I see both an IP v4 and v6 address.
ISP: T-Mobile USA
City: Chicago
Region: Illinois
Country: United States
I am OK with it as it is even though I cannot bridge the WAN to the LAN.
PFSense T-Mobile connections specs are only OK on PFSense:
RTT: 58.9ms for T-Mobile and 8.5ms for XFinity
RTTsd: 62.2ms for T-Mobile and 1.5ms for XFinity
No loss on either T-Mobile or XFinity.
Testing the modem with a battery last week connected to a second PFSense box it worked for more than 2 hours with no PS plugged in.
