# IPv6 NAT T-Mobile Home Internet

**URL:** <https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194>\
**Category:** General\
**Created:** [February 28, 2022, 3:12am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194 "2022-02-28T03:12:17Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChildOTK](https://forum.mikrotik.com/letter_avatar/childotk/32/6_449c533f586939b6e5f246632a46421f.png) [@ChildOTK](https://forum.mikrotik.com/u/ChildOTK)\
**Post date:** [February 28, 2022, 3:12am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/1 "2022-02-28T03:12:17Z")

</div>

I have T-Mobile Home Internet and one of their 5G gateways which I am trying to get working nicely with my RB4011, specifically with IPv6.

I am able to turn on the IPv6 DHCP client which pulls an address, and from there ping Google’s DNS, so there is connectivity.

T-Mobile Home Internet doesn’t support PD so I can’t pull a prefix from the DHCP client and use a pool internally.

What I have tried so far is setting up an internal IPv6 network, and then essentially NAT IPv6 traffic out, which I would expect behaves similarly to IPv4, sharing the same address.

However, although my devices get IPv6 IP addresses, IPv6 doesn’t work and is just dead.

I am wondering if anyone here has T-Mobile Home Internet and is using IPv6. Since T-Mobile Home Internet is really IPv6 based, it’s a necessity to maintain good performance.

With IPv6 latencies are anywhere from 17-22ms on average. Without it, latencies are more like 60-70ms on average, so quite a huge jump.

Would appreciate any help with this.

I upgraded to 7.1.3 today with hopes that I could get this working, I was on the most recent version of 6 earlier this morning but noticed there was no NAT available for IPv6.

---

<div class="post-metadata">

**Author:** ![tdw](https://forum.mikrotik.com/letter_avatar/tdw/32/6_449c533f586939b6e5f246632a46421f.png) [@tdw](https://forum.mikrotik.com/u/tdw)\
**Post date:** [February 28, 2022, 8:01pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/2 "2022-02-28T20:01:36Z")

</div>

Mobile/cellular carriers often only provide a single /64 and use the RFC7278 bodge. This is just about OK for a mobile with tethering, or a MiFi device with a single “LAN”, but useless if it is in (or connected to) a router which requires a /64 per interface. Support for prefix delegation was introduced into the 3GPP specifications, but it can take years for changes to be implemented by carriers.

The huge address space in IPv6 was supposed to do away with NAT, specifically the one-to-many network address and port translation (NAPT) which is ubiquitous in IPv4. There is a case for stateless one-to-one network prefix translation, I believe Mikrotik added this in v7 but can’t find any documentation to see if it would be suitable.

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 17, 2022, 12:23pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/3 "2022-05-17T12:23:01Z")

</div>

I have the same setup and am running 7.2 of ROS. I haven’t found any way to do this without getting a PD from T-Mobile. I also have business accounts with them and they don’t provide PD for their business accounts either. ☹

---

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [May 17, 2022, 2:26pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/4 "2022-05-17T14:26:13Z")

</div>

RouterOS now seems to support NAT “masquerade”, at least in the 7.3beta.  
Maybe you can get it to work using that?

---

<div class="post-metadata">

**Author:** ![aglabs](https://forum.mikrotik.com/letter_avatar/aglabs/32/6_449c533f586939b6e5f246632a46421f.png) [@aglabs](https://forum.mikrotik.com/u/aglabs)\
**Post date:** [May 18, 2022, 4:21am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/5 "2022-05-18T04:21:38Z")

</div>

Have TMobile 5g home internet myself. Only way I’ve found so far is as mentioned use fc00/7 inside my network and setup nat66 (/ipv6/firewall/nat).

My endpoints get a fc00/64 address which nats to public ipv6 address (must configure dhcpv6 on wan interface connected to TMobile router)

Only thing I’ve found so far is fc00/7 is treated as lower priority than ipv4 on windows endpoints so they will prefer ipv4 when it’s available. But ping -4 [Google.com](http://Google.com) and ping -6 [Google.com](http://Google.com) both work. Linux doesn’t seem to care and tries ipv6 first.

---

<div class="post-metadata">

**Author:** ![711brown](https://forum.mikrotik.com/letter_avatar/711brown/32/6_449c533f586939b6e5f246632a46421f.png) [@711brown](https://forum.mikrotik.com/u/711brown)\
**Post date:** [May 21, 2022, 1:55am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/6 "2022-05-21T01:55:09Z")

</div>

Can you expand on how you’ve set up the nat66 (/ipv6/firewall/nat) arrangement? I have the same situation – TMHI, their box grants an address (no PD); set up my own addressing – clients successfully get an IPV6 address, but without any internet access.

I tried setting up the IPV6 NAT rule similar to the ipv4 nat/masquerade settings, but wasn’t able to gain internet access over ipv6.

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 25, 2022, 9:50pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/7 "2022-05-25T21:50:36Z")

</div>

I have the same issue. I’ve setup an IPV6 DHCP server on ROS 7.2.3 with a pool = FD01::/56 I see all the devices getting an IPV6 address but they can’t get to the internet.

---

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [May 26, 2022, 8:33am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/8 "2022-05-26T08:33:06Z")

</div>

So now you all have to wait on each other and maybe one of you will experiment with the NAT features and post a working solution…

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 26, 2022, 12:58pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/9 "2022-05-26T12:58:59Z")

</div>

The IPV6 DHCP server doesn’t seem to do anything. I setup a private pool fc00::/56 and then assigned IP addresses to each VLAN. I also setup NAT rules similar to what we do on IPV4. I see the IPV6 routes created. I can ping the IPV6 gateway but that’s about where it all dies.

If I do prefix delegation from Spectrum I can get IPV6 to work. That’s probably because I’m getting publicly routable IP addresses from Spectrum.

aglabs: If you can post what you have working I can try some more experiments.

---

<div class="post-metadata">

**Author:** ![Zoxc](https://forum.mikrotik.com/letter_avatar/zoxc/32/6_449c533f586939b6e5f246632a46421f.png) [@Zoxc](https://forum.mikrotik.com/u/Zoxc)\
**Post date:** [May 26, 2022, 5:56pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/10 "2022-05-26T17:56:42Z")

</div>

@nsaldanh You’ll want to use fd01::/64 with Advertise enabled as the address on the LAN side. Make sure your client devices gets an address in fd01::/64 by SLAAC. Also make sure you get a IPv6 address on the WAN side and that the router is able to ping IPv6 addresses.

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 27, 2022, 2:20am UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/11 "2022-05-27T02:20:13Z")

</div>

[RB4011-IPV6.rsc](https://forum.mikrotik.com/uploads/short-url/kRtBNj6mZf0q2onkWAKrEN9Spka.rsc) (17.3 KB)  
Here is my configuration. I tried using fd01::/64 for each of the VLANS. All PCs get an IPV6 address from the pool, but they cant ping anything on the internet. I’d be very grateful for any help that someone much more knowledgeable about ROS 7 and IPV6 could provide.

Thanks!

---

<div class="post-metadata">

**Author:** ![Zoxc](https://forum.mikrotik.com/letter_avatar/zoxc/32/6_449c533f586939b6e5f246632a46421f.png) [@Zoxc](https://forum.mikrotik.com/u/Zoxc)\
**Post date:** [May 27, 2022, 2:02pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/12 "2022-05-27T14:02:19Z")

</div>

I’d use managed-address-configuration=no and other-configuration=no for /ipv6 nd as you’re not running a DHCPv6 server. Not sure if that is sufficient to get things working, but I didn’t spot other errors.

---

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [May 27, 2022, 2:15pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/13 "2022-05-27T14:15:15Z")

</div>

Show us the IPv6 routing table (/ipv6 route print) on the router and on the PC (route print) while everything is active.

---

<div class="post-metadata">

**Author:** ![tdw](https://forum.mikrotik.com/letter_avatar/tdw/32/6_449c533f586939b6e5f246632a46421f.png) [@tdw](https://forum.mikrotik.com/u/tdw)\
**Post date:** [May 27, 2022, 3:26pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/14 "2022-05-27T15:26:32Z")

</div>

And don’t use all-zeros for the host part of the address, it is reserved. Use _add address=::1/64 from-pool=private-pool interface=…_ or _add eui-64=yes from-pool=private-pool interface=…_

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 27, 2022, 4:08pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/15 "2022-05-27T16:08:02Z")

</div>

Thank you for all your suggestions. I am also running IPV4 in a dual wan configuration. ether1 goes to Spectrum and ether 2 goes to T-Mobile. Load balancing works under IPV4. I'm trying NAT to see if I can get dual wan loadbalancing to work under IPV6. I don't have the mangle rules for IPV6 as yet. I'll do that once I can actually connect to the internet using IPV6. If I just use prefix delegation from Spectrum, IPV6 will work as long as the Spectrum circuit is up and running.

I've changed what you suggested. Here is the output as requested:

[admin@MikroTik] \> /ipv6 route print  
Flags: D - DYNAMIC; I, A - ACTIVE; c, d, y - COPY; H - HW-OFFLOADED; + - ECMP  
Columns: DST-ADDRESS, GATEWAY, DISTANCE  
DST-ADDRESS GATEWAY DISTANCE  
DAd + ::/0 fe80::26c:bcff:feb8:c819%ether1-WAN1 1  
DAd + ::/0 fe80::26c:bcff:feb8:c819%ether1-WAN1 1  
DIdH ::/0 ::%ether2-WAN2 1  
DAd 2603:XXXX:XXXX:XXXX::/56 1  
DAc 2603:XXXX:ff00:XX::/64 ether1-WAN1 0  
DAc 2607:XXXX:XX:d163::/64 ether2-WAN2 0  
DAc fd01:0:0:4::/64 BR1 0  
DAc fd01:0:0:5::/64 MGMT\_VLAN 0  
DAc fd01:0:0:6::/64 VLAN\_110 0  
DAc fe80::%ether1-WAN1/64 ether1-WAN1 0  
DAc fe80::%ether2-WAN2/64 ether2-WAN2 0  
DAc fe80::%BR1/64 BR1 0  
DAc fe80::%VLAN\_130/64 VLAN\_130 0  
DAc fe80::%MGMT\_VLAN/64 MGMT\_VLAN 0  
DAc fe80::%VLAN\_110/64 VLAN\_110 0  
DAc fe80::%VLAN\_120/64 VLAN\_120 0  
DAc fe80::%cap8/64 cap8 0  
DAc fe80::%cap1/64 cap1 0  
[admin@MikroTik] \>  
  
  
and on the Windows 11 PC:

# IPv6 Route Table

# Active Routes: If Metric Network Destination Gateway 20 291 ::/0 fe80::764d:28ff:fed5:81bc 1 331 ::1/128 On-link 20 291 fd01:0:0:1::/64 On-link 20 291 fd01::1:5ca8:8b97:8561:380/128 On-link 20 291 fd01::1:708c:d761:e9bb:3b9f/128 On-link 20 291 fd01:0:0:5::/64 On-link 20 291 fd01::5:5ca8:8b97:8561:380/128 On-link 20 291 fd01::5:708c:d761:e9bb:3b9f/128 On-link 20 291 fe80::/64 On-link 20 291 fe80::708c:d761:e9bb:3b9f/128 On-link 1 331 ff00::/8 On-link 20 291 ff00::/8 On-link

Persistent Routes:  
None

---

<div class="post-metadata">

**Author:** ![nsaldanh](https://forum.mikrotik.com/letter_avatar/nsaldanh/32/6_449c533f586939b6e5f246632a46421f.png) [@nsaldanh](https://forum.mikrotik.com/u/nsaldanh)\
**Post date:** [May 27, 2022, 4:50pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/16 "2022-05-27T16:50:05Z")

</div>

Update: I can now ping Google’s IPV6 address. I could not in the past. However [whatismyipaddress.com](http://whatismyipaddress.com) does not detect IPV6

also [test-ipv6.com](http://test-ipv6.com) gives me this message: Your browser has a real working IPV6 address but is avoiding using it.

---

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [May 27, 2022, 4:56pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/17 "2022-05-27T16:56:01Z")

</div>

It can be that this is due to earlier failures and it will try using it later (maybe after a restart).  
The routing tables look OK. But as mentioned, it is better to put ::1 in the requested address fields (together with from pool).

---

<div class="post-metadata">

**Author:** ![tdw](https://forum.mikrotik.com/letter_avatar/tdw/32/6_449c533f586939b6e5f246632a46421f.png) [@tdw](https://forum.mikrotik.com/u/tdw)\
**Post date:** [May 27, 2022, 6:21pm UTC](https://forum.mikrotik.com/t/ipv6-nat-t-mobile-home-internet/156194/18 "2022-05-27T18:21:30Z")

</div>

> [@](#):
>
> also [test-ipv6.com](http://test-ipv6.com) gives me this message: Your browser has a real working IPV6 address but is avoiding using it.

If you are using Windows then IPv4 is favoured over IPv6 ULA

```plaintext
C:\>netsh interface ipv6 show prefixpolicies
Querying active state...
Precedence Label Prefix
---------- ----- --------------------------------
        50 0 ::1/128 localhost
        40 1 ::/0 IPv6 (except for better matches)
        35 4 ::ffff:0:0/96 IPv4 mapped
        30 2 2002::/16 6to4 (deprecated)
         5 5 2001::/32 Teredo (deprecated)
         3 13 fc00::/7 ULA
         1 11 fec0::/10 site-local (deprecated)
         1 12 3ffe::/16 6bone (deprecated)
         1 3 ::/96 IPv4 compat

```

You can use netsh to temporarily or permanently change the precedence.
