Netduma Fraser

I didn't do the testing myself but from what I've been told there were servers that needed to be whitelisted in order for it to work again properly, is it working for you now? (You may still need to add your friends to the allow list)

Okay no worries, we'll see where the team are at with this.

Interesting okay we'll look into it, thanks for letting us know!

Most people buy the router for its intended purpose, that's you're opinion and that's totally valid. I don't believe spending money and resources to market what a product isn't designed to do is a necessary step - if people research the router then they will see we don't specify circumventing SBMM as a feature. We have plans to incorporate more VPNs in the future, it's possible we could implement that sort of VPN but the purpose would be to help those in countries where their routing to game servers isn't optimized where the VPN can specifically help reduce their latency.

I've add you to the beta, upgrade to that and see if you're able to reach higher speeds: https://forum.netduma.com/forum/145-nighthawk-pro-gaming-beta/

The US we definitely weren't able to filter before the update but we were able to after. The US works as it's not too far away, it may not be possible for servers that severely increase your ping but we'll have a look - again, it's not the purpose of the router, if the game has changed something that prevents this we won't be able to do anything.

We can certainly try and take a look at it, I'll pass it onto the team

When you disable QoS how do you do it exactly? Also doesn't look like you've entered the speeds you expect in Bandwidth settings

This can sometimes still occur as DHCP is still active, it will continue to renew the lease, even though device IPs won't be refreshed it can still cause a disconnect for some reason. NG are aware and looking into it, in the meantime disable DHCP completely and that should resolve it. Keep in mind any new devices you want to connect to the router will need a static/reserved IP set to connect.

We have pushed out an update and from our testing it is better at filtering now

The translations belong to Netgear so we can't simply copy it to our routers unfortunately

It's not been fully released yet has it, is it still in alpha? Does it have its own server browser?

Do you see anything blocked on the map when that message appears at all?

We're testing it currently it seems a lot harder to force games much further away from your location, we're looking into it

Is that with the update we did yesterday and having added friends to the allow list?

Yeah I think that is a bit of a typo, if the Geo-Filter is indeed causing a misreading of the NAT status you can just leave it enabled and ignore the NAT reading from then on, we'll change it thanks!

My mistake, someone else asked this exact thing yesterday! No it won't be limiting you to the speeds reported there so you're all good, glad to hear you're having a good experience!

I believe I spoke to you yesterday about this but it's due to the servers we use and what server it may choose for you, if you get good speeds on speedtest.net then you can ignore it

Deberíamos haber enviado una actualización hoy, pero si no, será mañana. Vuelva a sincronizar la nube en el Geo-Filtro y vea si funciona

A more focused game update will happen this week, just requires a bit more testing.

We've put out a ping heatmap update today as well as an update for the XBL chat servers, more updates will come for the game but it requires a bit more testing to get it all sorted.

We did do some updates today, I'm unsure if efootball was included, try a resync, if not I'll see if they can do it tomorrow

Depending on the time of day/server load some servers may not be always available, this seems to happen specifically with Italy and Spain in Europe.

I'll talk to the team again about this as it's definitely an interesting one - I don't think we could do it on the NG routers but perhaps our own!

That's very kind of you thank you, we do appreciate it! I think for the moment, we're so deep in the next iteration of DumaOS that it would be better to try that once available and see what may have been improved upon/rectified and then what may still need improving and then we'll be in a better spot to implement those changes. That makes sense, Safari forces HTTPS by default and I'm not sure if there is a way to disable it. Regarding PWA we were looking at doing something like this, I'm not sure if it's still planned though.