Xbox one NAT moderate

@Greggy73

In your case the problem is the Home Hub 5.

It has extremely poor UPnP support and is not fit for purpose. In fact if you have call of duty on the xbox one then you might find you have a moderate NAT in the game even if you have an open NAT on the dashboard. This is because of the broken UPnP support.

I used to use one but the UPnP is so broken I ended up buying a new router and am now on permanently open NATs on all consoles.

 

Aha, you see, I am way ahead of you - whatever this is worth - as I have turned instant on off long ago, and have tried connecting directly into the gateway, bypassing the router, just to end up with the same problem, which means is not a double NAT issue.

The sheer amount of variations and attempts I have tried, combined with the fact that everything, including the 360 works fine, but the X1 does not, leads me to the conclusion it is console related, I may be wrong, but at this point, I seriously doubt it.

Once again thank you all, and please fell free to keep on brainstorming.

 

Have you tried factory resetting the console?

If you firmly believe there is a problem with your console that may be worth doing.

Obviously only do this if your console can connect to Live because your saves are stored in the cloud and if you couldn't access the cloud you would lose your saves.

Alternatively have you tried factory resetting the router?

 

[quote user="SpartanOfTheArk"]tried connecting directly into the gateway, bypassing the router, just to end up with the same problem, which means is not a double NAT issue.[/quote]So would that be a yes, or a no, regarding my question if your gateway is
operating in bridge mode?

Access your GP5607's web-utility interface, and It should be quite easily for you to determine if this device are using DHCP, NAT, and UPnP.

 

My Xbox has been behaving this way since I first powered it on, but yes, I have tried resetting both.

I have not tried to bridge, however, as I said, I have tried connecting it directly to the gateway, bypassing the router, which has the same effect, taking double NAT issues out of the equation.

That said, I go back to the original question, why does my battle scarred 2005 360 works like a charm, and the next gen do-it-all super machine does not? To make matters worse, it seems I am not alone in this problem.

 

According to this documentation:
www.pace.com/.../GP5607.pdf it's a gatway.

Do you know if your connected through an LTE service (mobile), or a carrier-grade service, or if your ISP has implemented IPv6, as native, or as a translation between IPv4 to IPv6?

 

As I said, I have tried connecting directly into the gateway (Pace), bypassing the router (Netgear).

My ISP is fibre optic, not LTE or CGN, and unfortunately, It is not IPv6, nor transition.

Sorry to keep insisting, but the bottom line is, whatever net set up I have, the 360 works and the X1 does not, and it just feels like cheap engineering.

 

Technically, the Xbox 360 doesn't use the same method to discover and diagnose NAT behavior, as the Xbox One. The Xbox 360 are using custome STUN (Session Traversal Utilities for NAT), where the Xbox One are using a simplified version to the STUN protocol,
which is one of many features implemented by the Teredo protocol. Since Teredo resides behind an end user NAT device, it encapsulate IPv6 packets inside IPv4 UDP packets, which also make it more sensetive to firewalling, and filtering behavior.

There are certain gateway's that do not function well with Teredo, and therefore, you should aim at your Pace GP5607 and confirm that this device has nothing to do with address translation, or portmapping. It should funtion as triple-play, to QOS your services,
like Internet, VOIP, IPTV.

 

Ah see, I knew they were cutting corners somewhere.

I will try to look further into it.