Netduma Fraser

What do you mean by an explosion of packets? What is the actual ping you're getting to the game? Are you actually experiencing lag or just wanting it to be super smooth every game as that is not really realistic as there are many variables with the server/game that cannot be controlled.

Judging from the first post as you've mentioned source ports don't overlap at any point unless I've missed it. Perhaps some others can give you advice on what specific ports to use but I personally just use DumaOS Classified Games and find that works for me.

As the other rules you've done have source ports within the 1-65535 range that you're trying to add now they're overlapping. You're essentially doing more than the basic console service or DumaOS Classified Games would, it's a lot more than is needed.

What are the other rules you're trying to add? If you're getting that message then the port has already been covered in one of the ranges that you've added previously.

These features may not be available for awhile although profile saving would probably be the first to be seen. For ping I would suggest you pin auto ping to the dashboard and open the dashboard in a new window and with the help of this old guide you should be able to have it overlay on your stream using OBS https://web.archive.org/web/20170710051950/http://wiki.netduma.com/doku.php?id=embed_ping_to_videos_and_streams

That's definitely a mislocated server, if you could put the details in the form in this topic that would be helpful. Possibly the above but if you've got that mislocated server showing in the US then the game still thinks you're in Europe so will block you from the US games so try forcing where that server isn't and you may find a game faster. Also would suggest you try forcing the East Coast.

I'm almost certain they are but I can ask the team to be sure. Some aspects are saved within cookies as they're more user preference rather than critical to the features e.g. switching between miles/kilometres on the Geo-Filter and so that means less strain on the router - obviously that example wouldn't strain the router but I think you get what I mean. As we add more features it's about squeezing the most out of the router as possible. No, you don't always have a connection to the cloud, periodically the router will connect to the cloud to check it has the latest Geo-Filter database for example, if it has the latest version then the connection is terminated until next time. If it doesn't then it will download this and then terminate the connection. When you use the flush cloud button you make a manual connection to the server and re-download the database regardless.

Thanks for the feedback, we will take it on board and sorry for the inconvinience it caused you. By affect I meant it didn't affect the internet which is what most people would be concerned with immediately.

You should just be able to do a reboot and then if it's still not working properly clearing the cache/cookies should work. The cloud system is there for parts of the router that would need updating frequently, instead of releasing minor firmware releases every week. The parts of the router this affects shouldn't ever cause issues with the routers functionality itself. As mentioned we've ensured this won't happen again.

I don't really understand how a reboot could have prevented you gaining any access to the interface. I have passed this on to the team to see if they have anything to suggest or want to take a look themselves. Sorry for the inconvienience.

Can you access at all via routerlogin.net or routerlogin.net/adv_index.htm? If not do a factory reset by holding the reset button for 30 seconds and then leave the router for 2 minutes and try to connect. If that doesn't work try and go through the TFTP process again.

In that case can you make the computer use a static IP address with these details: IP: 192.168.1.2 Subnet: 255.255.255.0 Gateway: 192.168.1.1 and then see if you're able to access the interface please.

Ahhh I see what might have happened. Can you clear your browser cache/cookies please and then try to access the interface again. If that doesn't work could you do ipconfig in a command prompt window and show me what the gateway address is please?

It did transfer successfully then, can you access the interface after that normally? Before you even attempted TFTP, did you downgrade to .32 etc and then upgrade back to .56 or reboot or reset at all?

I think it's best if you do a factory reset, this is generally recommended after upgrading to a firmware so may be going from .32 to .56 carried over some legacy issues. What were the steps you tried exactly before you started the TFTP process? Are you able to connect to the interface using an ethernet cable?

Hey, welcome to the forum! Basically we pushed an edit to the default theme of the router which caused the issue and so once we pushed the corrected theme file it fixed the issue. The features are hosted locally but we can push certain things over the internet, themes being one of them.

Great to hear that, thank you very much for letting us know so quickly.

Sorry to hear that, we do apologise for the inconvenience. Have you followed the above instructions to get back on the .56 firmware? If so, is it working correctly?

Please go here for the fix to this issue, let us know if this has resolved it for you:

Hi everyone, We had a temporary problem tonight which caused XR500 users to see a white screen which says 'DumaOS not loaded yet'. This is now fixed. You just need to reboot your router and the problem should be gone. Please post in this thread if this solves your problem as we have developers waiting to make sure this is 100% fixed for all. If you followed our workaround earlier and downgraded to firmware version 2.3.2.32, you can upgrade back to the latest version (.56) and you should be able to access the interface as per usual. The latest firmware is here: https://kb.netgear.com/000061157/XR500-Firmware-Version-2-3-2-56 We apologise for any inconvenience caused and hope you can all now get back to tinkering your DumaOS

*Update* We have identified the issue and we are working on an immediate fix. We will update this post with further information when it is safe to reupgrade back to .56. Thank you for your patience.

This has happened this evening after our office hours have closed so the team will investigate tomorrow when they are back in the office so I couldn't say at this time.

Try downgrading first then as that should work without resetting. Access via your LAN IP instead and add /adv_index.htm at the end, I've added this to my main post to reflect this. No it doesn't, thank you for the reminder, I've updated the main post to reflect this.

Clear your browser/cache cookies, if that doesn't work you may need to do a factory reset to ensure no legacy issues have carried over.

Updated post with the features not active on .32 and removed .40 link also.