Netduma Alex

I have sent the fix to your router. You are now safe to upgrade to DumaOS.

Just as a test, could you disable QoS by opening the anti-bufferbloat side menu? That will help me to narrow down the problem to QoS.

Might be due to lag compensation. If your ping is low, I don't see why this would be happening under normal circumstances. Could be down to jitter I guess?

If you let us know what problems you're having, we'll be happy to help. Big updates on the way!

Thanks, i'll add that in the next update.

Hello DumaArmy, We have recently improved our internal tools for managing the Geo-Filter Cloud. Now, it will be much quicker for us to adjust the position of game servers on the map when they are incorrect. We have published a cloud update containing all of the mislocated servers that have been reported thus far, but we need more! If you connect to a server that you believe has been misplaced on the map, let us know by filling in the form below. The reports will be checked frequently and uploaded to the cloud database after we've verified that they are correct. We have also added a space on the form for you to add your forum name, if you want. This will enable us to quickly respond to reports from users with a good track record of accurate reporting. With our improved tools, and the help of the community, we'll be able to make new titles compatible much faster than ever before. Loading…

C'est totalement facultatif, mais DumaOS est le système sur lequel nous travaillons actuellement. Le micrologiciel d'origine (avant DumaOS) n'est plus à jour et aucune mise à jour ne sera publiée pour celui-ci. La seule exception à cette règle concerne les mises à jour du géofiltre dans le cloud, qui sont toujours fournies automatiquement pour le micrologiciel d'origine en même temps que pour DumaOS. Vous pouvez continuer à utiliser le firmware d'origine aussi longtemps que vous le souhaitez. Il ne cessera pas de fonctionner, mais aucune nouvelle fonctionnalité ne sera ajoutée. DumaOS sera mis à niveau cette année vers DumaOS 3.0 qui aura une suite de fonctionnalités largement étendue, en particulier par rapport au firmware d'origine. Si vous choisissez de mettre à niveau, vous pouvez également rétrograder à nouveau si vous décidez que vous préférez le firmware d'origine. -- Well, it's completely optional, but DumaOS is the system we are currently working on. The original firmware (before DumaOS) is no longer up to date and no update will be published for it. The only exception to this rule is for geofilter updates in the cloud, which are always provided automatically for the original firmware at the same time as for DumaOS. You can continue to use the original firmware for as long as you like. It will not stop working, but no new functionality will be added. DumaOS will be upgraded this year to DumaOS 3.0 which will have a wide range of features, especially compared to the original firmware. If you choose to upgrade, you can also downgrade again if you decide you prefer the original firmware.

I'm glad it's fixed. I believe the issue is caused by a bug in the process which attempts to automatically identify devices. The developers will be able to fix this now that we know the source of the problem. Thanks for your patience.

Regarding the r-app not loaded issue, some people have been able to fix this by doing the following: Go to device manager Find any Nintendo Switches that are or have been connected to the router Change their device type to Xbox This, weirdly enough, should fix it.

After typing @name you have to click on one of the people that appears in the drop down. This might be tricky on mobile.

For clarification, the auto-update option is in Netgear's section of the firmware. It will update whenever Netgear releases a new firmware. The cloud update system is something built into DumaOS (seperate part of the firmware) which covers minor updates to device definitions, geo-filter map and so on.

I'll try and explain as best I can without revealing secrets about DumaOS 3.0. It was a problem on our cloud server, a developer pushed an update to our cloud which caused the interface not to load. The cloud update was bugged for a few hours. We had to get one of our developers to come in at midnight to get it sorted out ASAP. It's worth noting that none of the backend functionality of the router was affected, it was just the user's ability to access the interface. Some people have expressed concerns that if the servers were ever to go down, that their routers would stop working. This isn't the case, all that would happen in that situation is that you would receive no more cloud updates. The cloud update system is what we use to expand the amount of games supported by the router. This was a case of human error, and it's taught us never to do any testing using the live server!

Sorry about this issue, It sounds like we might need to fix this problem using TFTP. I will post a link to instructions below, but if you need assistance I can connect to you via teamviewer and do it for you. https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client

IP Modem means Internet Provider Modem, so the kit your ISP gave you when you signed up. EDIT: Oops I was late to the party on that one.

Welcome to the forum! I just attempted to send you the fix, and I think it might have worked, although instead of a confirmation I just got disconnected. Is your router working?

Here's what you should try: Download an old firmware version from here: https://kb.netgear.com/000060660/XR700-Firmware-Version-1-0-1-10 Unplug your XR700 from the modem, so that only your PC is connected Upload the firmware you downloaded, ignoring any warnings about it being old Once the downgrade is complete, perform a factory reset After the setup process, go to Settings and disable automatic updates Connect the WAN cable back to the router.

You can disable automatic updates from the Settings menu... Oh I see, but you're saying that it updates by itself when resetting? Maybe unplug the WAN cable from the router, reset it, set it up, disable automatic updates, then plug it back in.

I assume you did the factory reset from the interface before? You might need to try doing a factory reset using the button on the back, take a look at these instructions: https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Okay I have sent you the fix. You're ready to upgrade!

Yes you can. Have you followed the instructions here to get port 7777 open? http://support.netduma.com/support/solutions/articles/16000085789-how-to-upgrade-your-r1-from-version-1-03-5m-or-lower

Yeah actually I did do a cloud update on Thursday. My current plan is to try and do at least one cloud update every week. Thanks for the post DMC... I haven't read the whole thing yet but i'll do it in a bit! I'll finish the rest of my forum posts first.

We haven't announced a release date yet. We do have a target internally so we're not slacking off. We're making good progress on DumaOS 3.0. But we don't want to promise a release date and then have to delay it.

Yes that's still the latest version. The next version will be DumaOS 3.0.

I'm making progress on the Modern Warfare update. I think i've figured out what's causing the problems. Essentially, it's mislocated servers.

So you can select the server but the ping never appears? Thanks for the report, i'll look into it.