Netduma Fraser

Thanks for all that, I believe the dev will be next week so we'll finally be able to connect in and get you sorted

Le sugiero que primero pruebe el nuevo firmware, espere 5 minutos y luego siga con un restablecimiento de fábrica, luego vea si tiene el mismo comportamiento.

Bem-vindo ao fórum! Reproduzimos o problema e o transmiti à equipe para dar uma olhada, espero que seja um problema de nuvem que possamos corrigir rapidamente sem uma atualização de firmware.

Did you do a factory reset after the upgrade? If not please do so and see whether that resolves the disconnects. We have reproduced the location issue and I've passed it onto the team to have a look at.

Gaming requires very little bandwidth, you don't need to assign much to it - I would assign more to streaming, don't forget about Congestion Control as well - that will prevent your game lagging while streaming

No worries, thanks for trying, we'll have to wait until the dev is back, sorry for the delay!

Congestion Control you can experiment with, we always suggest starting at 70%. Based on this: https://stream.twitch.tv/encoding/ you need 3000-6000Kbps (3-6Mbps) upload to stream between 720p - 1080p quality. So for example if you have 10Mbps upload you would assign 30 - 60% to the streaming device.

@BulCongestion Control applies to the entire network to prevent local congestion so I would recommend still having that enabled but you could disable Traffic Prioritization and that will stop the game being prioritized. You could also assign bandwidth to the streaming device via Bandwidth Allocation - have a look at what Twitch recommend for upload depending on what quality you're going to stream and then assign the necessary bandwidth.

You can skip right past the registration part at the end of the wizard, if you do that can you access the interface without issue? What web browser/device are you using to access? Did you upgrade manually or do it in the interface via the firmware check?

I think we'll have to get the team to try and access and see what is happening on Monday. Could you enable remote support in WAN Settings please

That is peculiar, could you factory reset from the interface, then access it as quickly as possible, speed through the wizard and try the upgrade immediately, I'm hoping the speed of doing it will allow it to go through

Alright keep us posted and hopefully that will do it! That is awesome to hear, really glad you like what we are doing!

I'm not sure what link you used to download .207 but this is the correct one: https://www.dropbox.com/s/8z4kcynmo3glplp/DumaOS-R1-3.0.207.sig?dl=0 if you did use this link then it is possible the Chromebook has altered it somehow, in which case using a Windows PC and then upgrading from there should work just fine. When you factory reset how do you do it, via the interface or by using the hardware button?

That would be very cool! With designs like that you are relying on the internal antennae and not being able to move them could result in poorer WiFi performance. Maybe in the future! Awesome but the copyright lawsuits that follow it would not be 😂

Welcome to the forum! Did you factory reset after installing .134? If not please do so and see if that resolves the issue.

My 2cents on that would be that generally routers are kept in corners or out of sight so spending more money on the design of something makes less sense than putting that money into the internals or software.

Here you are: https://forum.netduma.com/topic/39415-introducing-early-access/

It'll be something we'll have to look into then, for the moment you'll have to manually reconnect it.

Just to confirm, are you saying the same thing happens when you just do a normal reboot from the interface?

How do you restart it, by the interface, button or unplugging the router? Setup the VPN so it is connected, reboot from the interface, wait 2 minutes and then see if it is still connected. If it is, see if it is connected when you next turn it on.

I mean how long do you leave it off, did you leave it off for 6 hours before the issue and then 8 hours and the issue started for example

Has the amount of time that you have had the router off increased by any chance?

I can see you've applied for early access so once that has been approved you'll be able to try it out!

Was that on a previous firmware? There aren't any settings that can be enabled/disabled to make it reconnect after a reboot

Je vérifie avec le développeur maintenant et je reviendrai vers vous quand j'aurai sa réponse