Double NAT issue (Non 4G smarthub)

[Bimbles04]

I've been having issues connecting to the R6 Siege servers under Ubisoft on PC for the past month, It's been frustrating bouncing between forums, customer service agents, online chat bots etc for the past month in my spare time.

I finally got a definitive identification of the issue, and it's that there are 2 private IPs within my home network which is causing the issue, one of which, is not for hardware within my home.

According to the Technician I spoke to from Ubisoft, that is the cause, as it can often lead to issues with Double NAT and cause issues with port forwarding.

The technician suggested I either ask for a dedicated public IP for my router, or I speak to EE about possible configurations.

Can I get some advice about what to do, and what might work if anyone has had something similar?

[XRaySpeX]

Sorry, which router do you have? Do you mean by "Non 4G smarthub" the EE Smart Hub provided for fixed Home BB? Cuz there isn't such a thing as a 4G smarthub! What product do you have from EE?

[Johncox80]

I'm having the same issue with 2 Ubisoft games, Rainbow Six vegas 2 and Splinter Cell Blacklist.  Neither can connect to the Ubisoft Servers and Ubisoft Support claim it's because I'm connecting through a double NAT. Only have the BT Smart Hub 2 through EE and no other router. REALLY need help

[Christopher_G]

Hi @Johncox80 

Do you have other games that work OK using the router for online gaming?

Chris

[Johncox80]

ALL other games work perfectly apart from the 2 Ubisoft games. Vegas 2 and splinter cell blacklist

Get Outlook for Android

[mikeliuk]

Hi @Johncox80 ,

I recommend to carry out a traceroute (tracert under Windows 10) to a public end point such as 8.8.8.8 to see how bad the situation is.

Below I show an example. Most people using NAT within their own homes will use private IPv4 addressing in the 192.168.0.0/16 range so you are likely to be double-NATed within your own home if you see two subnets 192.168.x.0/24 and 192.168.y.0/24. As you only have one router, this will be unlikely.

The second thing to look out for is the two other most common private IPv4 subnets 10.0.0.0/8 and 172.16.0.0/12 which you are unlikely to see using home broadband. Below you see that EE has used IPs in 10.0.0.0/8 as they don't feel that network engineers who are customer might be using that in their home labs.

Multiple levels of NAT typically doesn't have much impact on outbound connections.

If all the IPs on the traceroute are publicly routable IPs except for your LAN, then you are unlikely to be double-NATed.

[x@x ~]$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  example.com (192.168.x.1)  0.631 ms  0.567 ms  0.527 ms
 2  192.168.x.1 (192.168.x.1)  1.754 ms  1.720 ms  1.684 ms
 3  * * *
 4  * * *
 5  10.248.x.y (10.248.x.y)  40.913 ms  40.696 ms  42.118 ms
 6  10.247.87.167 (10.247.87.167)  51.151 ms  49.973 ms  49.923 ms
 7  * * *
 8  10.247.87.113 (10.247.87.113)  48.063 ms  21.278 ms  23.069 ms
 9  10.247.87.142 (10.247.87.142)  25.617 ms  27.983 ms  27.968 ms
10  87.237.20.146 (87.237.20.146)  27.735 ms  43.603 ms  20.750 ms
11  87.237.20.67 (87.237.20.67)  20.657 ms  19.486 ms  17.631 ms
12  72.14.242.70 (72.14.242.70)  25.249 ms  23.255 ms  25.369 ms
13  74.125.242.97 (74.125.242.97)  25.551 ms 74.125.242.65 (74.125.242.65)  20.859 ms  23.003 ms
14  108.170.234.231 (108.170.234.231)  23.020 ms 142.251.52.143 (142.251.52.143)  20.002 ms 142.251.52.151 (142.251.52.151)  24.652 ms
15  dns.google (8.8.8.8)  23.454 ms  19.176 ms  22.976 ms