Jump to content

Recommended Posts

Posted
On 1/26/2023 at 2:33 PM, Netduma Liam said:

Apologies I was not clear enough:

  1. Disconnect the Xbox ethernet cable
  2. Go to device manager and delete the xbox device
  3. Reconnect the xbox

If that doesn't work, re-enable IPv6 from LAN and see if it can get a connection again.

Did 123 didn’t work . So enabled IPv6 on lan then rebooted r2 and console . Connection comes back but Nat is strict double Nat 

Posted
Just now, Netduma Fraser said:

You will have to use your IPv4 public address not the IPv6 public address

Fair enough . How do I do that just disable IPv6 . The whole time it’s been set up on Xbox it’s always said ipv4 only any way . And before turning IPv6 on netduma I was getting the same issue double Nat 

  • Administrators
Posted

So disable IPv6 in LAN & WAN Settings on the R2, yes disable it on the BT Hub as well if possible. In theory with IPv6 there shouldn't be an issue with NAT so there is definitely something going on so if we can figure it out with IPv4 it will be easier. Once you've done all that google your IP address, it should be shorter so 150.160.170.190 for example, then follow the CG-NAT guide.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...