Netduma Liam

So have you now upgraded to the latest firmware? If so, could you please factory reset the R2 either through the three-dot menu in the top right of the interface (if possible) or hold the reset pin on the back of the R2 for thirty seconds.

Immediately after the disconnect, can you download the log file from the three-line menu in the logs panel and send them over to us?

In general, the results look pretty good as far as I can tell. Were these tests run while saturating the connection as Fraser mentioned? I'll link the guide below again for convenience. http://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping

When did you start noticing this? Was it after any network changes or an upgrade? Can you perhaps try a different browser?

Can you take it out of bridge mode if possible, then put the XR500 in it's DMZ and disable the modem's Wi-Fi.

Sorry, I'm referring to the modem that the XR is connected to, do you know the make and model of that? You can then put the XR WAN IP in it's DMZ if possible.

Thanks for that, could you please disable the DumaOS classified games rule, then add a new one. In the new rule, select your games console as the device and 'Games Console' as the service when prompted. After that, set Congestion Control low, down to about 40% maybe. Then set it to always. After doing this, click 'Reset allocation' on Bandwidth allocation just to be safe. Then, play some games and see how it feels. A couple of follow up questions: Do you know if you require PPPoE, VLAN or DHCP identifiers to get a connection to the internet? Are you using Geo-filter? If so could you share your configuration with us?

La solución a corto plazo es configurar VLAN/PPPoE en el enrutador ISP y luego conectar el XR a través de DHCP. A continuación, puede controlar la carga. No tenemos un ETA en el nuevo firmware, pero estamos trabajando activamente en ello con NETGEAR. Publicamos todas las actualizaciones que tenemos aquí: http://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress Intente también agregar la regla personalizada a Traffic Prio como mencioné.

Just to clarify, have you reset since the upgrade to the latest firmware version? If not, could you please do so. Can you also answer a few questions for us: Are ALL devices on the network connected via the R2? Have you got any custom rules configured in Traffic Prioritisation? If so could you please share them? If not, is the DumaOS classified games rule detecting traffic while you're playing? This is indicated by a red light on the rule, and the packet counters increasing. What's the make and model of your modem?

Tenemos algunas correcciones de QoS en el próximo firmware, con suerte deberían resolver este problema. Mientras tanto, hacer que el enrutador ISP maneje la VLAN, luego DMZing el XR solucionará el problema por usted. También sugeriría crear reglas personalizadas en Traffic Prio para el dispositivo en el que está jugando. Para experimentar inicialmente, simplemente seleccione "Consola de juegos" como servicio y vea cómo se siente.

Interesting, what's the make and model of the modem exactly? If it's a router/modem combo, can you put the XR in it's DMZ and reserve an IP address for it?

No tenemos nada que anunciar todavía, mantenemos este artículo actualizado con toda la información más reciente sobre firmwares: http://support.netduma.com/support/solutions/articles/16000132677-dumaos-firmware-progress

Hey @Ameryjr, unfortunately it looks as though we won't be able to do this. Lots has changed since the R1 and accessing the older hardware is now not going to be possible as far as I can tell. You could try downgrading back to an older firmware if you haven't already in case it's the newer firmware your R1 is having an issue with.

Just to clarify, is the problem you're having that DumaOS classified games is appearing to prioritise traffic even though it's disabled? Or are you having a problem with your custom rules not prioritising traffic? Is this having any actual affect on your game? It's more likely just a visual bug.

Thanks for posting all this information! One thing to note: Have you factory reset the R2 since upgrading? If not, please do so when possible as the latest firmware is quite a big upgrade so it's best to start from a clean slate and clear out any low-level code that could be there from a previous version.

Thanks for posting this. It would be good if you could create a new topic with this information so we can look into this further with you. In the new topic, could you please include the below: When the connection drops, are you able to access the DumaOS interface from a device connected via wired? Do you need to reboot the R2 to get the connection back, or will it eventually restore itself? Do you recall if the disconnections occurred after a particular device started generating some traffic? Are you using any wireless extenders, powerline adapter or access points for example?

You can see if it's enabled on the top bar of the interface, marked with a shield icon. We've seen another issue reported from a separate user where Traffic Controller may be causing a similar problem, have you setup any Traffic Controller rules?

@ahmedkI've responded to your new topic, let's continue there.

Are you using NETGEAR's Armor feature? If so could you please try disabling it. Is there any pattern at all to the disconnections? Do they occur during a particular time of the day or when a particular device is online? Are you using QoS and/or Traffic Controller at all?

@CJArthur Could you perhaps let us know the specific Traffic Controller rules you currently have configured? We'd like to replicate them internally to see if we can reproduce the bug.

Excellent, thanks for letting us know. We'll relay this info to the devs and get back to you.

Are you using Adblocker on your R2? If so could you please disable it temporarily and check if things improve.

Did you reboot after? If not, now that it's basically rebooted itself, monitor to see if it occurs again. The addresses should now be properly applied.

Could you please try hitting 'Resync cloud' now in Ping Heatmap and see if that's better?

A few users have reported this with the XR500, we'll get the team to look into it and see why it's not updating.