Netduma Fraser

Thanks for the post/suggestions, to cover your points: The most popular questions at the moment are related to issues that need to be fixed really so they won't be a FAQ for long. We learnt from the R1 that giving estimated dates for updates was a very very bad idea. Not to mention it's so fast paced that estimations can change daily. We generally have done that in the past so will probably do that in the future. That was a necessity but now you can update the firmware on the router itself it may not be as needed, it will also provide you the change log. I can't move them to the bottom of the forum but I could close them, the thing is though some people will have fixed their issue and the next day they're back again so it does help to have that post open so I know what has been tried/tested before. I'm not sure we'd make videos for issues but there will be more feature based videos coming It would be super helpful if people did that when making a topic, it doesn't slow any devs down, generally it's just me responding, it would help me for sure. However, in my experience, if someone is having an issue they just want to get a topic up and start getting some responses as fast as possible, this does change person to person though.

That's great to hear, thanks for the update!

That sounds potentially like a power surge/lost power. Make your settings changes, reboot from the interface then if that happens again it should all be preserved

I'm not 100% sure on what the plan is but I suspect it'll primarily be bug fixes with no new features

If you click refresh data in the top right does that work?

A device that connects via different methods will have different MAC addresses so it is possible it's one of your existing devices already. Reboot the router, delete all offline devices and see if it comes back

It shouldn't matter, as long as the IP is correct it will be applying to the Xbox, likely just couldn't detect the MAC properly, rebooting the modem/console may get it back

Still expected yes

For WiFi: Split the bands, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

The Ireland server is an authentication server as well. Get me the ID of the server there that's being allowed and I can check it

Thanks for that, looks like port 4 is where you're losing connection, if you plug the device into one of the other ports do you see the same issue?

As above that'll be the cause. However, you will still have an Open NAT, the Geo-Filter won't prevent that, it's likely just blocking the server responsible for checking the NAT status

It's likely SmartBOOST/IPv6, disabling those seems to prevent it, the team are looking into it. I don't know how it will come out at the moment but I suspect it might be a situation where I'm giving it out manually, we'll see

Where are you testing the ping exactly? Update is expected this week

That's a weird one, glad you were able to resolve it. Are you seeing packet loss directly to the ISP modem/router?

The team actually do seem to like providing firmware on Fridays haha

We are aware of the internet being a bit slow to connect which we're looking into but once connected there shouldn't be any issues. When you go on the game and get that message, is the device added to the Geo-Filter? If so if you disable it does it still happen?

Okay so it was fine for almost 4 days, compared to the previous days/nights was there anything different in your network activity at all?

Ah I see, well give it a try just as a test to see if you can get internet on the R2 through it then switch back. If you can then likely some setting there preventing it

Give it a static/reserved IP on the router, reboot the console then check again please

If you click on a server it'll show something like http://192.168.77.1/dumaweb/#geofilter/server_E48B05

I don't know if the team will want to do that right away - if there is a major issue then it could feasibly affect the entire customer base which would not be good

Delete the device from the Geo-Filter, reboot, close the tab, wait 4 minutes, access, change the home location by clicking on the map and see if that works

You shouldn't have to but does the speedport have a modem/bridge mode you could try?

If you access using 192.168.1.1 instead does that work better?