Netduma Fraser

We don't give out any ETAs but if we were to release .645 publicly it would be using the exact same version of the firmware you're on now. If we made any changes to it we'd release it with a new firmware number.

You can put that router MAC address into the R3 if needed, if that's the only thing they check for then it should work. Most likely but I couldn't say for certain or tell you who it could be

What do you mean you turn the router off a few times using the power button? To get the LEDs to work or for some other purpose? Are you waiting at least 4 minutes before turning off again?

It's likely a mislocated server then, can you provide a screenshot of the Geo-Filter page showing what you see when it happens and also provide the ID of that server please?

You don't need PPPoE to connect the router to their ONT, you can just connect them and it should work unless they've specifically put measures in place to ensure you use their router connected to the ONT. You can just connect the R3 to their router otherwise.

Yes it would hinder performance because you'd be limiting yourself unnecessarily and then SmartBOOST/Congestion Control would go off those speeds and potentially limit you further

Good to hear you were able to get out of it, fingers crossed it's stable for you now

Correct, it does not have HybridVPN to use a VPN provider like Nord with

Make sure you have Geo-Latency disabled

Keep the speeds you pay for input into the router, then anytime you want to do a speedtest do speedtest.net

There is no specific inherent reason why it would just suddenly happen, we'd need to delve deeper into exactly what is happening on the network at the time, your settings etc. Are you playing over WiFi etc, all the usual questions, as much detail as you can provide will help.

That ID is actually a Las Vegas server so not sure what happened there but all good!

Much better and closer to expected! You can use speedtest.net that's fine, it will be more accurate

It'll be a mislocated server on the map and very likely in Georgia or Atlanta. If you could provide the ID we can get it corrected.

@JOSHR3ll try this command as one command please instead: await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_web_setup_done",params:[true]}); await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_setup_done",params:[true]});

The test on the router itself can test lower due to the server provider we use but it doesn't necessarily mean it is limiting you. What speeds do you get on speedtest.net?

It's unlikely to be a hardware fault, more likely that it's gotten itself into a weird state. What firmware version are you on currently? If you downgrade/upgrade does it work after that?

I generally wouldn't advise going back to versions this old for reasons like this as those early versions are going to be where more issues are but if you open the browser developer tools by right clicking the interface, inspect element or pressing F12 usually then go to console on that window that appears and paste this command in exactly then press enter it should allow you to skip the wizard. Also .219 might be a good one to try as we did specifically improve PPPoE compatibility in that one. await duma.RPCHandler.PostRPC({rapp: "com.netdumasoftware.config", method: "get_time_zone", params: []})

Okay interesting, if you do have success on that .41 version it may be worth then re-upgrading to .540 to see if you can stay on a more up to date firmware while keeping connectivity.

@JOSHR3ll We have been made aware of it by users with PPPoE, not every person experiences it (unless they're simply not reporting it) and most aren't using PPPoE as far as can be determined by the forum. The big features we're working on have caused delays in getting firmware out and going backwards to fix issues like that would take more time than continuing on this path to get out a firmware with those features and hopefully a fix with that initial version. We don't give out any ETAs and I couldn't give you one for when any specific issue may be resolved. I do share and understand your frustration. It looks like you've had the router since towards the end of last year or maybe longer, have you had the issue the entire time or have you just upgraded to a connection that uses PPPoE?

As above it is something we're aware of and will be fixing. You could try the firmware above, I don't have any evidence to say either way whether that one will resolve it for you. I've not seen it as much on the latest Early Access but people just may not be reporting as they wait for it to be resolved. The only things I can suggest at the moment are try the above version, the early access version, asking the ISP to extend the timeout if possible, if you have a static IP then setting this on the R3 may help, otherwise putting a router in between the two to handle PPPoE for the moment would be the only other thing you could do while we get it sorted.

Not specifically no. You may be able to do some of these things by setting up Internet Rules for a specific guest device for example to block file sharing, printers etc

I will reply there shortly

Added

Haha don't worry, there will be a new firmware in your lifetime! Progress is going well as far as I can see. In the meantime though there is a newer firmware you haven't yet tried which I've just given you access to: https://forum.netduma.com/forum/151-netduma-r3-early-access/