peanut183

I think folks might want to look at what those numbers mean. A good tutorial on howtogeek can help demystify the results from uptime.

EDIT: Ah, only firmware versions prior to 2.3.2.32 are vulnerable. Are the XR500 routers vulnerable to the recently announced Unauthenticated RCE (Remote Code Execution) bug recently patched on the Netgear R7800? This article seems to suggest that is true. As does the KB article from Netgear.

This. I broke my own vow to not buy another Netgear product when I saw this router come out. I thought, "Hey, someone else doing the software!!! Cool, maybe I can rely upon this 3rd party to keep the system up to date." The jury is in. Nope. Another abandoned Netgear product. Shame on me.

Nice. Get given the run around for months...have some egg on your face too. The XR500 was a last chance for a Netgear product in my world. Sorry to see Netduma get dragged down with them, was really hoping I'd experience something different than the abandoned router syndrome that Netgear is famous for doing. Maybe we can all look forward to XR500v2 which has the exact same hardware just a different firmware roadmap with newer features. This is just insulting that the XR700 gets the HybridVPN us XR500 users have been promised months and months.

Here is some history. - January 23rd, 2018 - Netduma Iain (CTO): "NETGEAR have already agreed to include our VPN feature in future firmware. It is a prioritised (sic) feature as well so should be available in less than a month." Over 4 months later and no VPN. - February 12th, 2018 - Netduma Fraser: "Just a little update, we are currently developing the VPN feature for DumaOS on the XR500, it will be in the next firmware update (after the one that comes out soon)." This was before update 2.2.1.10 came out in March. Next update...no VPN feature. - February 21st, 2018 - Netduma Fraser: "our VPN solution will be included and the update will be out in March." This has been promised to me here publicly and privately with direct emails from the CTO and support. I'm really disappointed that I was told over and over again that it was coming. I was urged not to return the router by the CTO of the company saying it was coming soon. Fool me once...

You have to be joking.... You honestly expect a consumer to reset a device to factory settings and enter their settings manually again after every firmware update? Wow, you are out of touch my friend, that isn't how updating your device is supposed to work. Maybe to someone who plays around with dd-wrt and the likes for fun this is old hat, but Joe Gamer wants to play video games not resetting his router and spending 30 minutes reapplying settings.

Thanks for the verification all.

Just so I'm clear, I've been reading there are some Cisco products out there that aren't passing 1.1.1.1 along so for sure it could be my ISP, I just wanted to be sure it wasn't the XR500 since it looked to be dropping at the XR500.

I don't think that is the issue. If you look at my traceroute to 1.0.0.1 you will see that it hits my DMZ router at 192.168.0.1 while the 1.1.1.1 never makes the next hop. I'm able to access 1.1.1.1 through my VPN connection while trying to trace the route to 1.1.1.1. I'm looking to see if anyone else has had success hitting 1.1.1.1 through the XR500. For example, if I try to trace to 1.1.1.2 Tracing route to 1.1.1.2 over a maximum of 30 hops 1 3 ms 3 ms 2 ms 192.168.1.1 2 3 ms 2 ms 3 ms 192.168.0.1 3 * * * Request timed out. 4 * * * Request timed out. The 1.1.1.1 traceroute never hits my DMZ router. This is what I would expect to see if it was a problem with their service.

Hi, I'm unable to reach Cloudflare's DNS primary 1.1.1.1 through my XR500, but I am able to reach their secondary 1.0.0.1. I have a DMZ setup, my network is as follows: 192.168.1.0/24 Wifi/LAN on XR500 192.168.0.0/24 DMZ with .1 as the router ISP I setup the DNS in the XR500 to use the two Cloudflare servers, but the first one times out after 2 seconds and I cannot reach it via traceroute. Trying to get to 1.1.1.1... λ tracert 1.1.1.1 Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1] over a maximum of 30 hops: 1 2 ms 2 ms 3 ms 192.168.1.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. Trying to get to 1.0.0.1... λ tracert 1.0.0.1 Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1] over a maximum of 30 hops: 1 2 ms 2 ms 3 ms 192.168.1.1 2 3 ms 3 ms 2 ms 192.168.0.1 3 * redacted * 4 * redacted * 5 * redacted * 6 * redacted * 7 * redacted * 8 * redacted * 9 10 ms 9 ms 9 ms 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1] Does the XR500 use 1.1.1.1 internally?

That is a real bummer. I missed my return window based on some of these promises.

Any update on the DumaOS VPN client on the XR500?

Thank you so much for the update and the quick response on this issue.

Any idea if this was ever released by BD? I'm still seeing. "Uncaught TypeError: tree.invalidateData is not a function" - Device Manager "Uncaught ReferenceError: d3 is not defined" - QoS "Uncaught ReferenceError: d3 is not defined" - Geofilter I can't use any of the above features as their UI doesn't load.

Tough combination to pin down. Thanks for the update.