Netduma Fraser

Delete offline devices in the Device Manager menu, then if any come up as unnamed check the IP it shows with the IP on the device and re-name it. What makes you think the static IPs aren't working exactly? If you set the static IPs it can help prevent that issue, otherwise make sure you add all devices with static/reserved IPs then you can disable DHCP entirely. You don't need to worry about the logs, they're primarily for devs and show normal background processes. By reset do you mean reboot and are you doing that by unplugging the router? Go to the System Information page and then in the Rapp panel menu ≡ change the retries to 5, reboot from the interface, wait 4 minutes before accessing and see if it prevents it going forward.

Added you both

Added, let us know if it improves: https://forum.netduma.com/forum/151-netduma-r3-early-access/

Could you try using a different browser and see if it works then please? For example I tested with Opera and it worked

You won't be able to ping every server, that is normal, most game servers don't respond to pings and so we can't determine what it is. We're working on a new ping method that should help make this more reliable.

What is the firmware file you're trying to update with exactly?

That's great to hear, thanks for the update!

Are you testing the speeds on the router or speedtest.net? If applicable how have you up your ISP modem/router to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode. Are ALL devices connected to the R3? The 450 and the R3 have completely different hardware and software so settings that work on one won't necessarily work on the other.

Good to hear, thanks for the update!

Is it still showing on the map when that happens? If so that's fine it's still working but I've given you Early Access where it should be more reliable on that firmware: https://forum.netduma.com/forum/151-netduma-r3-early-access/

When you're able to, do downgrade and let us know if the issue continues

Gaming doesn't use much bandwidth so the amount shown for gaming there could be correct. Try this: Quit the application/game/client completely Remove device from the Geo-Filter Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works.

If you have a connection in that setup then that means you do not need to change anything further relating to the network settings

We're aware of the issue and looking into it. In the meantime use the mobile web browser to access the interface for a similar experience.

Check direct to your modem/router, do you get the same issue?

I've given you Early Access which should work better: https://forum.netduma.com/forum/151-netduma-r3-early-access/ If on point 1 you're still seeing servers on the Geo-Filter etc then you can ignore that but it should be resolved on early access firmware. You won't be able to stabilize or even ping every server so that can happen. We're working on a new ping method that may improve this.

I don't think the command was right as it should return a different message, double check you're getting the whole command. What did you see when you tried it on the app exactly? What is the model of the modem/router the R3 is connected to?

Added

Right click the page, then go to Inspect (Element), on the window that appears click on the Console tab. Then paste and enter this command: await duma.RPCHandler.PostRPC({rapp: "com.netdumasoftware.config", method: "get_time_zone", params: []}) see if that allows you to get past the Setup Wizard.

Open it in an incognito window and see if you can continue, if not try another browser, otherwise download the DumaOS app on your phone and try to continue that way

Thanks for letting us know, we can certainly look into it

It's hard to say, I think they would use relay servers regardless but I suppose it is possible - if you play without filtering enabled but so you can still see the servers, do you notice the same thing?

Have you tried the latest Early Access firmware? It should be largely resolved with that one. To disable fully go into SmartBOOST - Menu - Settings > Toggle Enabled off

The only things I can think of that could be causing it are: The devices aren't directly connected, instead they're connected through a switch, extender etc The device name you think it is, is no longer correct - for example if you've changed the connection method it may appear as a different device. Check the IP on the device itself and then check the device you think it is on the Device Manager, do they match? If they do then I think go ahead with the reinstall of the firmware.

Added