NEW R2 FIRMWARE: 3.0.394

[deuce98lau]

I just upgrading to .394 and US was listed as an option.

 

My wifi did not boot up after I did the factory reset. I don't need it, so I disabled it and left it at that. The lights are still on. I read someone say that lights only turn off after a power cycle. I'm not bothering. I know before your wifi was terrible. Has anyone tested the wifi, is it reliable now? 

[Netduma Fraser]

6 minutes ago, deuce98lau said:

I just upgrading to .394 and US was listed as an option.

My wifi did not boot up after I did the factory reset. I don't need it, so I disabled it and left it at that. The lights are still on. I read someone say that lights only turn off after a power cycle. I'm not bothering. I know before your wifi was terrible. Has anyone tested the wifi, is it reliable now? 

It may be after the second reset the option is lost, we'll investigate.

If it's disabled entirely the lights shouldn't be appearing at all, if it's not broadcasting and the lights aren't bothering you then that's fine, if they are, enable wifi, apply, reboot, wait 2 minutes then disable WiFi, apply, wait 2 minutes then see if the lights stop.

[slugg]

8 hours ago, Zippy said:

Your not losing your mind.. I can confirm this as well. There is no United States in the region selection when first setting up your R2. @Netduma Fraser please take a note of this please to have this corrected.  

Thanks!

Zippy.

Thanks for sanity check! lol

[djiby]

Bonjour, pour mettre à jour il faut d'abord installé la nouvelle mis à jour puis ensuite faire une réinitialisation d'usine?

(je pensais que c'était l'inverse😅)

[Netduma Fraser]

17 minutes ago, djiby said:

Bonjour, pour mettre à jour il faut d'abord installé la nouvelle mis à jour puis ensuite faire une réinitialisation d'usine?

(je pensais que c'était l'inverse😅)

Oui c'est vrai, mettez à jour, attendez que tout se passe et que vous ayez à nouveau accès à l'interface, puis réinitialisation d'usine.

[fatal0Efx]

Always glad for an update.  I love the multi tonal background now.. Much easier to look at.

Disappointed the geofilter scroll/zoom issue isn't fixed yet where zoom overrides scroll.  I really hate having it zoom when I'm simply trying to scroll the page.

Also still waiting for the anti-ping assist filter to exclude people with crap pings within my geo fence.

[Netduma Liam]

8 hours ago, fatal0Efx said:

Always glad for an update.  I love the multi tonal background now.. Much easier to look at.

Disappointed the geofilter scroll/zoom issue isn't fixed yet where zoom overrides scroll.  I really hate having it zoom when I'm simply trying to scroll the page.

Also still waiting for the anti-ping assist filter to exclude people with crap pings within my geo fence.

Thanks for feeding back!

The issue of the Geo-filter map will be resolved soon, we're making some front-end changes currently. It's not really possible in most games to block players with high ping, most games use server based matchmaking so you can only control the server you connect to.

[fatal0Efx]

1 hour ago, Netduma Liam said:

Thanks for feeding back!

The issue of the Geo-filter map will be resolved soon, we're making some front-end changes currently. It's not really possible in most games to block players with high ping, most games use server based matchmaking so you can only control the server you connect to.

Thanks for the response. Yes I'm aware that I can't control whoever else a given p2p-host/dedi-server allows to connect to it.  

It is my understanding, though, that ping assist allows low ping players (outside my geofence) to connect to me (if I am host)  or allows me to connect to them or low ping servers that are outside my fence.

If that is accurate, why couldn't you do the opposite; preventing me from connecting to high ping player hosts/servers that reside within the fence? 

[Netduma Liam]

39 minutes ago, fatal0Efx said:

Thanks for the response. Yes I'm aware that I can't control whoever else a given p2p-host/dedi-server allows to connect to it.  

It is my understanding, though, that ping assist allows low ping players (outside my geofence) to connect to me (if I am host)  or allows me to connect to them or low ping servers that are outside my fence.

If that is accurate, why couldn't you do the opposite; preventing me from connecting to high ping player hosts/servers that reside within the fence? 

Sort of yeah, setting a ping assist value means that servers OR peers outside of your radius will not be blocked if they're below a certain ping value.

The reason we haven't implemented the reverse of this is that it's much more rare to find a peer/server within your radius that has a high ping. This can only occur if it's been mislocated, in which case you can just manually deny it. 

[Simon]

Why the hell am I having even more issues with this update now? My internet keeps disconnecting more often. It happens about twice a day, and my speeds are way lower then what I should be getting. My internet connection isnt consistant anymore..

[johnnytran]

Anyone having issues with the connection benchmark? getting abysmal speeds but other speedtests max out my connection

 

[fatal0Efx]

14 hours ago, Netduma Liam said:

Sort of yeah, setting a ping assist value means that servers OR peers outside of your radius will not be blocked if they're below a certain ping value.

The reason we haven't implemented the reverse of this is that it's much more rare to find a peer/server within your radius that has a high ping. This can only occur if it's been mislocated, in which case you can just manually deny it. 

Maybe I have a misunderstanding still.

Just because a host is close, it does not mean it is a good host.  Many folk have issues with their networks or ISPs.  Some oversaturate their lines (hence why QoS feature was designed though most people don't have Netdumas).  Further there's often issues between two hosts that are uncontrollable.

I understand the Geo fence setting being added was based on the assumption:  closer = better.  Correct?  But then sometimes that pool of hosts may be too thin, so ping assist was added to include any host with a good ping.  Correct?

If both of those are correct, couldn't this all be done better and more simple by scrapping geo and ping assist entirely and simply give us a single option to prevent hosts over X ping (aka anti-ping assist as is today)?  I fear I may be over simplifying what those options do today, so forgive me.

[Netduma Liam]

15 hours ago, Simon said:

Why the hell am I having even more issues with this update now? My internet keeps disconnecting more often. It happens about twice a day, and my speeds are way lower then what I should be getting. My internet connection isnt consistant anymore..

Did you factory reset after upgrading? If not, please do.

If the disconnections continue after this, could you please see if you're able to access the interface when this occurs?

9 hours ago, johnnytran said:

Anyone having issues with the connection benchmark? getting abysmal speeds but other speedtests max out my connection

The next firmware will fix a lot of issue pertaining to how Connection Benchmark reports speeds.

8 hours ago, fatal0Efx said:

Maybe I have a misunderstanding still.

Just because a host is close, it does not mean it is a good host.  Many folk have issues with their networks or ISPs.  Some oversaturate their lines (hence why QoS feature was designed though most people don't have Netdumas).  Further there's often issues between two hosts that are uncontrollable.

I understand the Geo fence setting being added was based on the assumption:  closer = better.  Correct?  But then sometimes that pool of hosts may be too thin, so ping assist was added to include any host with a good ping.  Correct?

If both of those are correct, couldn't this all be done better and more simple by scrapping geo and ping assist entirely and simply give us a single option to prevent hosts over X ping (aka anti-ping assist as is today)?  I fear I may be over simplifying what those options do today, so forgive me.

Sure, I see what you mean. However very few, if any, games currently use peer-to-peer matchmaking. Especially in the competitive setting. So the assumption that the closer servers will have lower ping and therefore provide a better experience is more accurate now.

I like your idea of blocking servers/peers by ping and I'll add it to our list of community suggestions for the devs to consider, but I do think it's use-case is more rare now.

[fatal0Efx]

4 hours ago, Netduma Liam said:

Sure, I see what you mean. However very few, if any, games currently use peer-to-peer matchmaking. Especially in the competitive setting. So the assumption that the closer servers will have lower ping and therefore provide a better experience is more accurate now.

I like your idea of blocking servers/peers by ping and I'll add it to our list of community suggestions for the devs to consider, but I do think it's use-case is more rare now.

Fair. Appreciate the dialog. Thanks! 

[Danno1016]

I upgraded to the newest firmware and no I am lagging when I play games. Can you help me out here or in a private message?

[UK_Wildcats_Fans]

On 11/19/2021 at 4:16 AM, Netduma Liam said:

We totally get that it’s been a while since the last firmware and we’ll be posting an update explaining why, as well as why it’s not going to happen again. There's a LOT more to come, including features, over the next few months so keep an eye out...

I have not see any posts about this.  Did I miss it?

[Netduma Fraser]

10 hours ago, Danno1016 said:

I upgraded to the newest firmware and no I am lagging when I play games. Can you help me out here or in a private message?

Did you factory reset after upgrading? I'd recommend retesting your QoS settings, we did a lot of stability improvements so what worked for you on the previous firmware may not on this one.

37 minutes ago, UK_Wildcats_Fans said:

I have not see any posts about this.  Did I miss it?

You can see it here: https://forum.netduma.com/topic/38088-where-is-the-next-dumaos-firmware-for-nighthawk-pro-gaming-routers/

 

It's not specifically about the R2 but it does also apply.

[brother_x]

 

I have this error with the latest firmware on my R2 (3.0.394)

[Netduma Fraser]

20 minutes ago, brother_x said:

 

I have this error with the latest firmware on my R2 (3.0.394)

Did you factory reset after upgrading the firmware? If not please do so and that should resolve the issue.

[brother_x]

12 minutes ago, Netduma Fraser said:

Did you factory reset after upgrading the firmware? If not please do so and that should resolve the issue.

Hi Fraser, I did do a factory reset before and after the update.

[Netduma Fraser]

1 hour ago, brother_x said:

Hi Fraser, I did do a factory reset before and after the update.

Do you get the error just on the QoS page or every page? Did it occur when loading the page for the first time? If you do a reboot, wait 2 minutes then access is the error still there?

[brother_x]

2 hours ago, Netduma Fraser said:

Do you get the error just on the QoS page or every page? Did it occur when loading the page for the first time? If you do a reboot, wait 2 minutes then access is the error still there?

It happens in Dashboard, QoS, Device Manager, I will try again to update the software and then a factory reset.

[brother_x]

8 hours ago, brother_x said:

It happens in Dashboard, QoS, Device Manager, I will try again to update the software and then a factory reset.

The problem is not resolved, I had to go back to version 3.0.205

[Netduma Fraser]

1 hour ago, brother_x said:

The problem is not resolved, I had to go back to version 3.0.205

Interesting, not seen this error message before, and it doesn't occur on .205? When you factory reset after the upgrade how did you do it exactly?

[brother_x]

1 hour ago, Netduma Fraser said:

Interesting, not seen this error message before, and it doesn't occur on .205? When you factory reset after the upgrade how did you do it exactly?

In version .205 I hadn't had that error, I downloaded the file, did a factory reset, 
did the initial setup and then ran the .394 update, 
and after the update was done I did another factory reset.