Jump to content

All Activity

This stream auto-updates

  1. Today
  2. There won't be no. It'll just be security fixes then, it's unlikely it's based on 3.3, I think it probably reached end of service before they did it.
  3. After flashing the latest official firmware, this is what I see in the router menu: System Info: Uptime: 19:17:29 up 1:37, load average: 1.09, 0.72, 0.56 Router Time: Sat Jan 17 19:17:29 UTC 2026 Board Model: XR700 Firmware Version: V1.0.2.62 DumaOS Name: A7Legit There is no DumaOS version shown starting with 3.3 anywhere in the UI. is there any more information available about the XR700 firmware v1.0.2.62 (A7Legit)? I can’t find any user feedback, changelogs, or discussions about this update anywhere online, only the brief “security fixes” note from Netgear. Has anyone tested it in detail or knows what was actually changed?
  4. @Netduma Fraser The latest early access on the old Netduma R3 isn't perfect. I prefer the official one before your big update. It's been a year since the last official firmware.
  5. it's not that hard prerequisites: - PS5/XBOX only - Crossplay:: ON (CONSOLE ONLY) - Standard Moshpit ONLY - Be patient and be prepared for long waiting times. what to do: - Use your Geofilter to target a server approx. 4,500 km (2,800 miles) away. This will give you around 100 ms ping. - Strict mode: on - Fast search: off - Steady ping: off
  6. Good to hear, don't forget the Early Access firmware as well
  7. @Netduma Fraser Hi Fraser Netduma R3 arrived Friday and installed the official firmware 4.0.540
  8. Yesterday
  9. Thanks for the report, I'll pass it on to the team to update it
  10. That's normal, follow this guide to see if you have a CG-NAT https://support.netduma.com/docs/dumaos-3/open-nat/#cg-nat
  11. Hy guys , When i try to search the Arc Raider's server the Ping doesn't work This situation is for only this game ,other game works. Thank you
  12. Hi So I double checked. Wan IP > 192.xx.xx.xx is the same as the static ip that is set on ee hub - the one I used since day one. public ip > is the same one that call of duty, whatismyipaddress dot com and ip info see. I don’t know if this is a sign of double Nat or just the way things work in DMZ. But I noticed in trace routes that after dumaos.lan I hit ee router default gateway. I’ll show a screenshot,
  13. You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ. In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it: Get a static public IP from the ISP (usually a charged extra) Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge) Change ISP to one that doesn't use CG-NAT
  14. Can you add me to the beta access list as well please?
  15. Hi Fraser I hope you and your team had a good Christmas and 2026 is treating you all well so far. I was wondering if i could ask your advice. Due to my setup (Using EE hub with the R3 inside its DMZ). I have double Nat. My ps5 doesn’t seem to care, but my Xbox is not happy about it. So if I were to plug my R3 into my EE’s FTTP ONT, would I need to setup R3 again or can I just go to wan settings on Duma os app and put sign in details? Also, if this approach doesn’t go well and go back to ee DMZ. Should I screenshot my current wan settings or will the router automatically revert to previous settings once reconnect to EE hub? Just to reinform you of my current setup. EE Hub WiFi is off, UPnP is off on ee hub and R3 is assigned a static ip and in the EE DMZ. R3 has UPnp on.
  16. Good to hear, thanks for the update!
  17. Last week
  18. Just updated and it seems like the issue disappeared, did not need to reset factory settings either. Interface loads way faster too. Thanks for the access.
  19. Results definitely won't be the same with the same settings due to having another router connected but you will be able to achieve the same results you'd just need to fine tune the settings. I'd be interested to see your results from all your tests
  20. Bufferbloat!
  21. What does better results actually mean though, in what sense?
  22. Sorry to hear that! We don't give out any ETAs but hopefully not much longer for one
  23. @Netduma Fraser Hi Fraser, the 4 LAN ports on the Netduma R3 burned out due to lightning, and I bought another one that's supposed to arrive Monday. When's the next official firmware? Not even a new Early Access one or the one you haven't released yet.
  24. Já testei, eu tenho resultados muito melhores conectado à ONU do que conectado à ONT, (matéria de controle de congestionamento) fica melhor conectado à ONU certeza!
  25. Added - let us know if you get the same issue on that firmware
  26. Good to hear, thanks for the update!
  27. Hi, I would like to be added too. Have been getting issues with using the DumaOS interface for a while now, just says it can't load and gives me recovery options. When I hard reboot the router via power the interface works for a couple of times then it goes back to this issue after a week or so.
  1. Load more activity
×
×
  • Create New...