Jump to content

Netduma Fraser

Administrators
  • Posts

    86944
  • Joined

  • Days Won

    1895

Everything posted by Netduma Fraser

  1. Added https://forum.netduma.com/forum/151-netduma-r3-early-access/
  2. As a test shut your console down fully when you stop using it and see if it gets boosted still after 24 hours please
  3. So just the boosting aspect stops working? What games/applications are you expecting to be boosted? Presumably you're seeing them being boosted when you're playing the game/using the application within that first 24 hours and then it shows nothing correct? What devices are you using that the boost would be applying to? Are you leaving that device in an instant on/standby mode rather than shutting it down fully?
  4. How did you set your ISP router for the R3? DMZ, modem/bridge mode? Were ALL devices connected to the R3? Are speeds set the same as those you receive? What settings were changed from the defaults? The Geo-Filter only shows connections that are being made, if only a few didn't appear then it's likely the game wasn't attempting a connection to them. The latest update is here: https://kb.netgear.com/000068422
  5. If you're getting those ping spikes directly connected to the ONU when there is no possibility of local devices interfering then that's something you'll need to rectify with the ISP first as the router won't be able to help with inherent instability. Set the MAC address of the R3 to the MAC of the ONU instead and see if that helps. Where are you measuring the packet loss? It's very bizarre with only a few devices and only being used one at a time that you're getting packet loss. I really would suggest you explore the ping spikes with the ISP first as its likely the loss is related as well, even if you didn't see it in that testing session.
  6. Could you explain what the issue is that you're facing exactly?
  7. You are: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/
  8. I'll ask them to update that too! That's really great to hear, thanks for the update!
  9. Their IPs change and so can become out of date, I'll get the team to update the 14 not displaying, thanks for the report!
  10. It is and yes as far as I am aware - at least for the moment the latest security updates are present - you can upgrade to the public version which does have this version of DumaOS in.
  11. Good to hear, thanks for the update!
  12. Okay so you don't need it. Correct, you have a very good ping so the game doesn't need to do anything to compensate
  13. The ping itself doesn't matter, it's the stability that Steady Ping helps with. If it's a stable 8ms ping to the game server and doesn't fluctuate then you don't need it. If it does fluctuate then I would suggest trying it.
  14. Good to hear, thanks for the update so far!
  15. Do this: Quit the application/game/client completely - including the game client from the System Tray - important! Remove device from the Geo-Filter If you're on PC then give it the PlayStation Device Type in the Device Manager 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 To force servers you need to do the following: It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or platform (e.g. Xbox, PlayStation) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place.
  16. It would be best if you made a new topic for this, include the answers to these questions there: What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3? What are the speeds you pay for/receive? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What game are you playing? What platform are you playing on and how is it connected, via ethernet or WiFi? How have you setup the Geo-Filter?
  17. The beta is no longer required as it is part of the latest public version now
  18. Great to hear that, thanks for the update!
  19. .1147 is the latest one we released on Friday so I'd suggest that
  20. I've added you to Early Access so you can upgrade to the firmware there, that should get rid of the errors on the interface, it may fix the PS issue also but if other devices have internet it may not be the router, I've provided the link to the PS guide for it anyway. If it continues after updating disable the Geo-Filter, does it work then? https://forum.netduma.com/forum/151-netduma-r3-early-access/ https://www.playstation.com/en-gb/support/error-codes/ps5/ce-118527-4/
  21. How did you do a reset exactly? From the interface or physically? By a reset do you mean a factory reset or a reboot?
  22. Thank you I'll pass it onto the team to correct
  23. We don't have any servers that would appear on the Geo-Filter/block you from playing, it's an authentication server for the game, you've done the right thing to allow you to play and we'll take the ID and add it to our whitelist. They change/update their servers frequently so sometimes this happens.
  24. Okay keep us posted! Make sure to do the reboot as well, if it is the lease for some reason then that should prevent it happening for at least a week
  25. On the actual devices themselves, they're device specific settings so for example on the Windows PC that's connected to the WiFi, in the WiFi list when connected to the R3, click the 'i' top right of the connection and it will take you to the page you can disable Random Hardware Addresses. Same principle applies to the way you do it on a phone. The log may be reporting the ports reversed so could be port 1 = 4 and port 3 = 2, are those your PCs? Have any settings or anything with the physical setup been changed prior to the issue occurring?
×
×
  • Create New...