goofygooberr7 Posted January 29, 2023 Author Share Posted January 29, 2023 On 1/26/2023 at 2:33 PM, Netduma Liam said: Apologies I was not clear enough: Disconnect the Xbox ethernet cable Go to device manager and delete the xbox device 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 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 29, 2023 Administrators Share Posted January 29, 2023 Could you do the CG-NAT test again please but with IPv6 completely disabled in LAN/WAN? Link to comment Share on other sites More sharing options...
goofygooberr7 Posted January 29, 2023 Author Share Posted January 29, 2023 23 minutes ago, Netduma Fraser said: Could you do the CG-NAT test again please but with IPv6 completely disabled in LAN/WAN? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 29, 2023 Administrators Share Posted January 29, 2023 You will have to use your IPv4 public address not the IPv6 public address Link to comment Share on other sites More sharing options...
goofygooberr7 Posted January 29, 2023 Author Share Posted January 29, 2023 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 Link to comment Share on other sites More sharing options...
goofygooberr7 Posted January 29, 2023 Author Share Posted January 29, 2023 Should I turn IPv6 off on by hub if there is an option ? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 29, 2023 Administrators Share Posted January 29, 2023 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. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now