Losing my mind!

[wmartin89]

I posted previously about my Xbox, this has never been fully resolved.

I’ve now plugged my Netduma R3 straight into my internet port to use as the main router rather than through my Hyperoptic Nokia Router.  My Xbox is hard wired to the R3.  It is constantly coming up NAT unavailable when I load up my Xbox.  I sometimes get lucky and get it to open after a tonne of messing around.

I’ve tried:

1. UPNP on by itself.

2. UPNP on with Xbox in DMZ.

3. UPNP off with port forwarding all of these ports (ignore on or off at the minute, this is during testing)

4. Port forwarding with DMZ also.

When I test the NAT, I get “can’t get a teredo IP address” error on the Xbox.

Xbox is manually setup with the assigned IP on the photos.  The last photo is using UPNP, this port shows active then inactive, it is never fully on, it goes between both during the NAT test.

I am using Google DNS (8.8.8.8 & 8.8.4.4)

Have turned off QoS tagging, have disabled IPv6 in the LAN section, nothing is working 🤬

[TrayDay]

Apologies for not adding anything. But, I am curious, who is your Internet Service Provider?

[wmartin89]

2 minutes ago, TrayDay said:

Apologies for not adding anything. But, I am curious, who is your Internet Service Provider?

It’s Hyperoptic, I only seem to have this issue since using the R3 whether it’s used as a secondary router or, as of the other day, the main router, and it hardwired.

Wireless to the Nokia router supplied by Hyperoptic had no issues with NAT, the reason I went wired and with R3 was for better connection and geo filtering, but this is so much hassle trying to resolve!

[Netduma Jack B]

Hi @wmartin89

Just as a test, is it possible for you to disable IP6 on the WAN interface, enable UPNP and then reboot? 

Would just like to see if that fixes the NAT issue.

 

[wmartin89]

10 hours ago, Netduma Jack B said:

Hi @wmartin89

Just as a test, is it possible for you to disable IP6 on the WAN interface, enable UPNP and then reboot? 

Would just like to see if that fixes the NAT issue.

 

Would this not disable me being able to access the router settings on my phone after testing?  Would it not be the LAN interface since this deals with the wired connections?

I unplugged the Ethernet cable and everything works swimmingly, however the download speed being 184mbps when I’m paying for 1Gig and am only 2mtrs away from the router is the exact reason I wanted to go wired.

[bbursley]

Hey there.

It sounds like the NAT issues are a result of you trying to trying to double NAT (because of the two routers). What I would personally do here is set your Nokia device either in bridged mode, OR, adding assign a static IP to the netduma router in the Nokia, then add it to the DMZ. This should allow your netduma to become wide open to the internet, and allow you to apply firewall related security using the netduma instead. 

If you can, maybe see if your ISP offers an ONT only, without needing the router, that would surely make life a lot easier overall in my opinion. ISPs don't always offer that though, but its worth considering!

[wmartin89]

9 hours ago, bbursley said:

Hey there.

It sounds like the NAT issues are a result of you trying to trying to double NAT (because of the two routers). What I would personally do here is set your Nokia device either in bridged mode, OR, adding assign a static IP to the netduma router in the Nokia, then add it to the DMZ. This should allow your netduma to become wide open to the internet, and allow you to apply firewall related security using the netduma instead. 

If you can, maybe see if your ISP offers an ONT only, without needing the router, that would surely make life a lot easier overall in my opinion. ISPs don't always offer that though, but its worth considering!

I’ve just taken the time to remove all smart home devices from the Nokia, put absolutely everything on the R3, removed the Nokia completely (unwired, unplugged), used the R3 as the main router, still nothing is working (either wired or wireless).  I had it set to Open on the wifi for a while last night, now back to “unavailable” and when testing - “can’t get a teredo IP address”.

On my screenshot above with UPNP, it shows teredo IP matching the Xbox IP, the port just constantly goes between active and inactive, should it not be staying active?

[Netduma Fraser]

12 hours ago, wmartin89 said:

Would this not disable me being able to access the router settings on my phone after testing?  Would it not be the LAN interface since this deals with the wired connections?

I unplugged the Ethernet cable and everything works swimmingly, however the download speed being 184mbps when I’m paying for 1Gig and am only 2mtrs away from the router is the exact reason I wanted to go wired.

You'd still be able to access. LAN IPv6 is for local IPv6 addresses which wouldn't be applicable in this scenario. Interesting okay so check the IP on the console when you're connected via WiFi and then again via ethernet, then match these with the IPs on the Device Manager. For the WiFi version of the console what settings have you set up for this? Then again for the wired one, what settings have you done? Make the ethernet device changes the same as the WiFi (remove every change if needed), then check, does it work properly?

[wmartin89]

2 minutes ago, Netduma Fraser said:

You'd still be able to access. LAN IPv6 is for local IPv6 addresses which wouldn't be applicable in this scenario. Interesting okay so check the IP on the console when you're connected via WiFi and then again via ethernet, then match these with the IPs on the Device Manager. For the WiFi version of the console what settings have you set up for this? Then again for the wired one, what settings have you done? Make the ethernet device changes the same as the WiFi (remove every change if needed), then check, does it work properly?

With the update above in reply to someone else, the wifi also started showing unavailable NAT and the like after shutting down last night and loading up this afternoon.

Wired IP ended in 196 and wireless 193, both matched the Device Management settings when doing either.

I changed my LAN IP from 192.168.77.1 to .0.1 at the end, this opened up the NAT (for now) on Wireless, I’ve not messed around with Wired yet to see but I have a feeling once I power down Xbox later and load back up another time, I’ll have the exact same issue.

[Netduma Fraser]

That's bizarre, changing the LAN IP shouldn't have made any difference whatsoever. Was the IP to access the Nokia router 192.168.0.1 by any chance?

[wmartin89]

4 minutes ago, Netduma Fraser said:

That's bizarre, changing the LAN IP shouldn't have made any difference whatsoever. Was the IP to access the Nokia router 192.168.0.1 by any chance?

That’s why I have a feeling that once I shut down and load up another time, it’ll go back to unavailable.

The Nokia router was 192.168.1.1, but I done this change when the Nokia router had been removed and I using the R3 as the only router hooked up to my wall.

[Netduma Fraser]

I'd remove the manual DNS, that might not be helping you, if you want to use one then use 1.1.1.1 and 1.0.0.1

[wmartin89]

4 minutes ago, Netduma Fraser said:

I'd remove the manual DNS, that might not be helping you, if you want to use one then use 1.1.1.1 and 1.0.0.1

Have tried with no manual DNS and only the upstream DNS checked, have tried with google DNS with both upstream checked and unchecked.  Will give the above one a try if more issues crop up.