All Activity

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

yeah but im asking should i use the speed test info for the app instead of using the speeds the app gives me

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.

These are the steps I just took to make PPPoE automatically reconnect. Uploaded the firmware v4.0.41. Performed a factory reset through the GUI. I was unable to reconnect to the router through LAN or Wi-Fi. Performed multiple factory resets through the pinhole in the back of the router until I was able to connect, trying different ideas such as removing the residual power. Removing all cables before factory resetting was what seemed to allow me to connect afterwards. Since I was next to the router at the time, I skipped the setup wizard through the mobile app via Wi-Fi, and everything went smoothly. Uploaded the latest firmware via LAN. Configured PPPoE. Afterwards, I disabled and re-enabled the LAN1 port from the modem connected to the WAN port of the R3, and the R3 automatically detected the Internet Port status.

IS there any reason why all of sudden, I'd be getting really bad packet loss with the netduma, up to 30% and take it out there's 0%.

ok thanks!

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

The ID is: 1FD984N Las Vegas. Ok i was wrong but its 27ms now. Not sure if still need ID. Its weird, when i connect to atlanta server it saids las vegas for a split second then after game start its Atlanta Server. So not sure if this is an issue or not. If need anything else let me know or more info. Thank you for your time.

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

I get this in speed test. But my question is should i be using the speed from speedtest or netduma?

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.

Las Vegas is 4ms. i live in Georgia not to far from Atlanta. I have a 12ms ping. my question is, why is las Vegas 4 ms when Atlanta is 10 or 11ms.

@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?

Hello, I’m currently experiencing significantly lower speeds than expected when testing through my Netduma router. My internet service is 1 Gigabit fiber, so I should be seeing speeds much closer to that. However, when running the speed test through the Netduma app, I’m consistently getting around 200 Mbps download and 200 Mbps upload. To rule out configuration issues, I have already performed a full factory reset on the Netduma router using default settings, but the speeds remain the same after the reset. Because this is fiber, there shouldn’t be any limitation from the ISP side that would explain speeds dropping this low. The results seem far below what should be expected for a gigabit connection.

I tried the workaround you suggested, but unfortunately I am still unable to proceed with the setup. Here is exactly what I tested. After downgrading the router to firmware 4.0.41 and performing a factory reset, the router launches the initial setup wizard. The wizard requires a successful PPPoE connection before allowing me to continue. However, my ISP requires VLAN ID 2 for PPPoE to work. The setup wizard in this firmware does not provide any option to configure VLAN before attempting the PPPoE connection, so the connection cannot succeed. I also tried the command you suggested in the browser console: await duma.RPCHandler.PostRPC({rapp: "com.netdumasoftware.config", method: "get_time_zone", params: []}) The router returned a successful response (errorCode: 0), but the wizard did not skip and remained stuck on the same step. I then attempted several additional troubleshooting steps: Clearing browser storage and forcing redirection to the dashboard via the developer console Trying to directly access internal pages such as /#/dashboard and /#/settings/internet Disconnecting the WAN cable and attempting to skip the internet setup step Connecting a temporary DHCP internet source to allow the wizard to complete Unfortunately, none of these methods allowed me to bypass the setup wizard or reach the main DumaOS interface. So at the moment I am blocked on the setup screen and cannot configure: PPPoE VLAN ID 2 which are required for my fiber connection. For reference, my setup is: Fiber connection ONT: Nokia G-240G-E PPPoE authentication Required VLAN ID: 2 Could you please advise on how to bypass the setup wizard or access the full configuration interface directly, so that I can manually configure PPPoE and VLAN? We are getting close to solving this puzzle, so I am confident we will get there 🙂 Thank you for your help. 192.168.77.1-1773378052314.log

Olá equipe de suporte, Estou enfrentando um problema recorrente com meu roteador Netduma R3. O LED deixou de acender há algum tempo. Já realizei o reset de fábrica e reconfigurei o dispositivo, certificando-me de deixar todas as opções relacionadas ao LED ativadas, mas mesmo assim ele não liga. Notei também um comportamento estranho: em algumas ocasiões, ao desconectar e reconectar o aparelho na tomada, o LED chega a acender por um curto período, mas logo depois desliga sozinho e não volta a funcionar. Gostaria de saber se esse problema pode estar relacionado a algum defeito de hardware ou se existe algum procedimento adicional que eu possa realizar para corrigir. Agradeço desde já pela atenção e aguardo orientações.

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: []})

I encountered a new issue while trying the workaround that was suggested (downgrading to firmware 4.0.41). After installing firmware 4.0.41 and performing a factory reset, the router starts the initial setup wizard. The problem is that the wizard requires a successful PPPoE connection before allowing me to continue to the next step. However, my ISP connection requires VLAN ID 2 in order for PPPoE to work. The setup wizard in firmware 4.0.41 does not provide any option to configure a VLAN before attempting the PPPoE connection. As a result, the PPPoE connection cannot succeed during the setup process. There is an option to skip the internet setup step, but in my case this option appears to be bugged and does not allow me to proceed to the next screen. The wizard remains stuck and I cannot reach the main DumaOS administration interface to manually configure VLAN 2 and PPPoE. Because of this, I am currently unable to complete the setup process on firmware 4.0.41. Is there a way to bypass the setup wizard and access the full administration interface directly so that I can manually configure VLAN 2 and PPPoE? At this point it feels like every step reveals a new puzzle, but I’m sure we’ll get there eventually 🙂.

Would this have been your first factory reset on a firmware after v4.0.41? I believe factory resetting after downgrading is the most important part.

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.

Thank you for the explanation. I understand that firmware development priorities and larger feature updates can delay fixes for specific issues, and I appreciate the transparency about that. To clarify the timeline: the issue started after I upgraded to firmware 4.0.645 and performed a full factory reset. Before that, I did not notice this behaviour. I then decided to downgrade back to firmware 4.0.540 and performed another factory reset, hoping that returning to the previous firmware would resolve the issue. However, the problem remained. Since then, the PPPoE reconnection issue occurs consistently every 24 hours on both firmware versions (4.0.540 and 4.0.645). As soon as possible I will try the workaround that was suggested (downgrading to firmware 4.0.41 first, setting everything up, and then upgrading again) and I will let you know the results.

@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?

Thank you for the clarification and for confirming that the issue is known. From my testing the behaviour is very consistent: exactly 24 hours after a reboot the connection stops. If I disconnect the Ethernet cable between the ONT (Nokia G-240G-E) and the R3 and reconnect it, the internet immediately comes back without rebooting the router. This strongly indicates that the PPPoE session expires and the router does not automatically renegotiate it until the WAN link is reset. My setup is: Fibre connection ONT: Nokia G-240G-E VLAN ID: 2 PPPoE authentication on the R3 Firmware: 4.0.540 What is surprising to me is that, according to the forum discussion, this PPPoE reconnection issue has been known and reproducible since June 2024. Considering that PPPoE is a very common connection type for fibre users, it is quite unexpected that a fix has not yet been released. Regarding the suggestion to extend the PPP session timeout with my ISP, this is unfortunately not possible. The 24-hour session timeout is imposed by the provider and cannot be modified. Could you please clarify if there is an estimated timeline for a firmware fix? In the meantime I will try the workarounds you suggested (v4.0.41 procedure and possibly the Early Access firmware).