Netduma Fraser

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.

Could you provide a screenshot of where it appears and what its ID/IP is possibly? Just curious to see how that's presenting itself.

*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. *Update 2* It is now safe to upgrade back to .56. We have received multiple reports about these issues. I have reported this to our team as this seems to be affecting a few people today. While we investigate please try a factory reset first using the button at the back of the router and holding it down for 30 seconds then allowing 1-2 minutes for boot up before accessing. If that doesn't work please follow these instructions: 1. Go to http://routerlogin.net/adv_index.htm if that doesn't work please try your LAN IP instead with /adv_index.htm added to the end e.g. the default IP is 192.168.1.1 so would be 192.168.1.1/adv_index.htm 2. Administration -> Firmware Update 3. Download this firmware (two versions below .56*) http://www.downloads.netgear.com/files/GDC/XR500/XR500-V2.3.2.32.zip 4. Unpack the .zip file 5. Browse to Image file 6. Upload 7. Go back to Administration -> Firmware Update and disable Auto Upgrade until we can say this has been resolved. If you receive any errors on the .32 firmware then you may need to clear the cache/cookies on your web browser, if that doesn't solve it then do a factory reset, that should ensure no legacy issues have carried over. We are sorry for any inconvenience this may have caused and will investigate this issue ASAP. *This version lacks some security updates but this is unlikely to affect you as well as some features (e.g. Ping Assist, Device Manager Table View, Hybrid VPN & Advanced Ping Stats) from the .56 firmware.

The Geo-Filter shouldn't show local IPs, could you provide a screenshot of this? Do you have the R1 in the DMZ of the Tp.

You can do it like that, it just won't appear correctly in the list but it will work. Just click done and it should add a rule.

I would suggest keeping the source ports at the default 1-65535 and just changing the destination ports as that will definitely work but that's our official stance so you may want to experiment instead like other users are but just thought I'd mention it.

If the light is on then it is working. They're different games with different population sizes so they will play differently. If you've done manual prioritization then they may have different ports you need to use.

No that isn't normal. The rules you've added will be incorrect, you'll have to double check the rules mentioned by the guys in the topic to get it working correctly. Alternatively post a picture of your rules and they can let you know what to change.

I mean it's possible, I couldn't think of why they would do that at all. Have you done any port forwarding rules? If you've not port forwarded correctly that could explain it. Switch to UPnP and see if you see the same behaviour.

Was it port 49566 by any chance? Do you have multiple Xboxes or consoles in your home at all? If it was 49566 and you do have another console thats used then it may switch to this port when 3074 is being used by another console.