Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. What is the reason you're having to reboot the R3 exactly? Are you having any issues with IPv6?
  3. To solve the reboot > setup loop after you've done the setup reboot the router from the interface, wait 4 minutes then access again, this will act as a hard save and then if you reboot again (presumably you're doing so via the physical button or pulling power) then it shouldn't go back to the setup. Try the upgrade immediately after a reboot/factory reset i.e. reboot/reset and try to access as soon as you're able to to initiate the upgrade.
  4. Added
  5. Yesterday
  6. Can you also add me? I also have an R2 and R3 router and would love to be a part of the beta test!
  7. Eu tenho ipv6 nativo do meu provedor ips, essa versão beta 4.0.1147 funciona bem com ipv6? Minha conexão é uma ONU em bridge e preciso de usuário e senha para conectar, alguém aqui sabe se gunciona bem e eu tenho um ipv4 fixo (público) ou seria melhor eu trocar para um ONT e colocar o mtz do duma na ONT alguém sabe a melhor opção pois mesmo com a versão beta as vezes preciso reiniciar o R3 alguém sabe sobre 9 que eu falei, alguma sugestão?
  8. Hi guys, it's been a long time since i posted on here so hope this finds you all ok. I bought a used Netduma R2 the otherday and i'm having real problems just running thru set up because whenever it reboots i'm back to the set up 1st page again. So i thought it maybe needed a firmware update so i got the latest one (DumaOS-R2-3.3.280.sig), i started the upgrade and then it just sits there saying "Upgrade in progress" and it just stays there constantly doing nothing i had it sat there for a few hours and nothing. I have factory reset it quite a few times now but get the same outcome where in the end after a restart i am right back at the set up 1st page again. If i had hair half would be gone now, i really hope i have not been sold a dud by the person i got it off. Any help appreciated and if you need any details just ask. Thanks Note: Firmware on the R2 when i bought is 3.0.205 if that is any help.
  9. There can be issues with PPPoE sometimes so if possible I'd suggest having the other router handle it, put the R3 then in the main router DMZ to ensure you don't have any NAT issues then connect ALL devices to the R3 and see if Congestion Control works better then. Ping Optimizer can be inaccurate so I wouldn't trust the values all the time, also by design it disconnects devices to ensure they don't interfere with the test, when finished they would reconnect. There are logs in Settings > Advanced > Troubleshooting. I've given you Early Access so you can try the firmware there: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/
  10. Ahh that's good to hear, glad there was a solution, thanks for the update!
  11. Follow this guide and that should resolve it for you: https://support.netduma.com/frequently-asked-questions/legacyfaqs/wifi-password-incorrect/
  12. Added. Once you've upgraded fully I'd suggest factory resetting then you can re-enable those settings
  13. Hello Fraser / NetDuma Team, I would like to report a possible R3 firmware/DumaOS issue. I have spent a long time testing different configurations, and I believe this may not be a normal setup problem. Network setup: Router: NetDuma R3 ISP: Zen Internet FTTP Connection type: PPPoE Speed: 900 Mbps download / 100 Mbps upload Firmware: DumaOS 4.0.540 Main issue: The Congestion Control function appears to have little or no effect. I manually changed the percentages (10%, 20%, 50%, etc.), but the Bufferbloat results do not change. It feels like QoS is not actually applying the limits. I have already tested: IPv6 disabled SmartBOOST ON and OFF Speed Test Bypass ON and OFF Congestion Control mode set to Always Different Congestion Control percentages Different Ethernet cables R3 as main router R3 as secondary router behind Zen router The result is basically the same. Another problem: When running Ping Optimizer, sometimes the R3 loses Internet connection completely. After several reboots it recovers. After recovery, the built-in R3 Speed Test sometimes becomes abnormal: Normally around 900 Mbps download After the issue sometimes only around 500 Mbps download Strange behaviour: Sometimes without changing any settings: Bufferbloat suddenly becomes Grade A Speed Test returns to normal Everything works correctly Then later, without any changes, the problem returns again. Additional observation: When R3 is used as a secondary router, the Speed Test ping was previously around 5–6 ms. After the recent instability, the same setup now shows around 7–8 ms consistently. I mainly use the R3 for competitive gaming (eFootball), so consistent latency and stable QoS performance are very important. Could you please advise: Is this a known PPPoE/QoS issue? Could Congestion Control be failing internally? Is there any Diagnostic Log I can provide? Is there an Early Access/Beta firmware available that I could test? I am happy to test firmware versions and provide feedback if it helps identify the issue. Thank you very much.
  14. Thanks for the response, sorry for the late reply. After days of attempted troubleshooting I found out that it was actually that my ISP pushed a bad firmware update to a specific line of modems causing these dropouts.
  15. Last week
  16. So I just bought my first netduma r2 and the wifi password on the back keeps saying its not the right password when i try to connect
  17. Can I get access to the beta 4.0? When installing do I turn Qos and other settings that I shut off due to disconnects back on before I install or after?
  18. thank you!
  19. You don't need to be incredibly accurate, speeds are always going to fluctuate so you can't be anyway really. I would just input the average speed you're getting with SmartBOOST on and leave it at that, then focus on adjusting Congestion Control and SmartBOOST to optimize your connection as much as possible.
  20. Nothing more specific than what you would usually do and you can just use the CoD showing on Heatmap as it will almost certainly use the same servers
  21. Added
  22. Hello @Wintercabin. I recommend you enable UPnP, or you could port -forward UDP 3074 and 9308 as long as you have an open NAT it shouldn't really matter. BO1 and BO2 run on P2P (meaning another player in the lobby is the host). Hit reg really depends on how far the hosting player is from you and the quality of their connection so ensure you use the geo filter to get a host close to you.
  23. I did testing as I was able to grab the family laptop, here’s my results. What numbers would you suggest inputting based on my results? BTW I’m impressed that the R3 was able to push my full line considering how cpu heavy pppoe is. Smart boost off 1)) 916 down, 110 up 2)) 921 down, 110 up 3)) 903 down, 109 up Smart boost on, CC sliders set to 100 up and down (to get line speed with qos on) 1)) 837 down, 106 up 2)) 863 down, 106 up
  24. hey Fraser...are you guys still allowing for the beta for the R3? I havent really been on here much but if you are I wouldnt mind messing around with it. Thanks.
  25. Sorry - this is for the XR500
  26. With the ports of Black Ops to PS5, what settings can we use to get lobbies with really good hit detection? Also, which servers can we ping on the heatmap for these games?
  27. Thanks, I’ve currently input 910/105 into speed yesterday. I did do a speed test with cc set to 100 up and down. I got Speedtest.net outputting 808-834 down and about 105-106 up. But based on previously ones, I would say my speed is about 765-834ish most of time. I’ll do more test. (If I did it with r3 in DMZ it would be 794-888) do you advise testing at quiet time, how many times shall I test per season twice or 3 times? and shall I turn off smart boost/cc off or just turn it up to 100 percent for true speed? note: I’m doing pppoe with r3 connected directly Ont. Speed isn’t important, more stability/low lag
  28. What are the allowedIPs you're trying/wanting to use exactly and I'll see if I can get the team to make a working config for you
  1. Load more activity
×
×
  • Create New...