Jump to content

Netduma Fraser

Administrators
  • Posts

    83971
  • Joined

  • Days Won

    1730

Everything posted by Netduma Fraser

  1. Okay so it was a faulty power adapter, we don't sell the adapter directly but it should have all the information on the plug itself.
  2. Do you have another power adapter with similar voltage that you are able to try with the router?
  3. It's certainly something we can look into, thanks for the idea, I'll add it to the list!
  4. Without access to the interface we're unable to remote in and really there isn't anything else that can be done except us flashing the router again in house but I'm not sure if we have that functionality anymore as we haven't sold the router for quite a few years. You can email [email protected] and they may have some more suggestions but likely to be the same as I have said.
  5. Only needs to be held for 30 seconds, then you can release it
  6. Unplug the router from power for 10 minutes, plug in, wait 2 minutes then try accessing and see if it loads
  7. You'll need to sign up here for Early Access: https://forum.netduma.com/topic/39415-introducing-early-access/ then once approved you can try out the firmware
  8. You'll have to keep trying resets, unplug the router from power for 10 minutes, plug in, wait 2 minutes then reset the same way as above
  9. Do you know what firmware version you were on? It indicates it may not be resetting correctly. The beeps on startup is normal.
  10. Je détecte IPv4 maintenant, donc tout va bien, nous ne pouvons malheureusement pas accéder en utilisant IPv6, nous essaierons donc d'accéder lundi en utilisant l'IP que nous pouvons voir maintenant, sinon nous publierons un retour car cela peut changer d'ici là.
  11. This is something we're aware of, it's something we've managed to fix on the R2 according to a user having the same problem so possible it'll be fixed in the XR500 build. I'll add your name to the list so you can try it when we expand the group.
  12. Great to hear it's all working now, thanks for the update!
  13. Sounds like a misreading on the console side then, glad to hear you're having a good experience, thanks for the update!
  14. We'll make a note of your username for when we start adding more people!
  15. Je viens de remarquer que vous avez IPv6, pourriez-vous également le désactiver dans les paramètres LAN et WAN sur le R2, s'il vous plaît ? Merci et toi!
  16. It's definitely worth shopping around for servers, not all of them will be under heavy load and like I mentioned, some with a higher ping on the Geo-Filter that you wouldn't think would play well might be better if the in game ping isn't that much higher. Playing outside peak times will be better as well although I appreciate it's not always possible. You're very welcome!
  17. To quote myself on this: Geo-Filter: Shows your ping direct to the server, anything on your side of the server essentially, including the server location, ISP routing, modem, router, QoS settings etc can affect this. In Game: Shows your ping direct to the server + processing delay - All games have processing delay but not all choose to include it in their ping calculation, CoD does. I would expect the in game ping to be 20-30ms higher than the Geo-Filter ping maximum. If the in game ping is 30+ ms higher than the Geo-Filter then it indicates the server is under heavy load (too many players online on the server bank), when this happens it's a good idea to try and force a different server. Even if the ping on (1) is higher, if (2) is lower overall than the previous server then you will have more stability and a better experience. Hopefully that clears it up for you!
  18. Hey, welcome to the forum! Default credentials are lowercase admin / password if not you hold the reset button for just 30 seconds, wait 2 minutes then attempt access again. There is no other way to access it where it won't ask you for the credentials and you can't use the USB port to upload firmware.
  19. For this message a reboot fixes it, give the router a reboot, wait 2 minutes then access and see if it works
  20. Nous pouvons essayer de forcer une mise à jour pour vous à distance lundi, pourriez-vous vous assurer que le R2 est dans la DMZ du modem/routeur de votre fournisseur d'accès Internet et activer l'assistance à distance dans les paramètres WAN sur le R2, s'il vous plaît
  21. Non ce n'est pas normal, je n'ai jamais vu ce comportement auparavant. Pourriez-vous redémarrer puis essayer immédiatement d'accéder et d'essayer la mise à niveau dès que possible, si cela ne fonctionne pas, essayez la même chose, mais avec une réinitialisation d'usine, veuillez voir si vous pouvez le faire prendre le firmware de cette façon
  22. Setup the cascade option and select the option for passthrough as well on that page, that should then allow you to get an Open NAT through the R2
  23. Débranchez le routeur de l'alimentation pendant 10 minutes, branchez-le, attendez 2 minutes, puis maintenez enfoncé le bouton de réinitialisation à l'arrière du routeur pendant 30 secondes, relâchez, attendez 2 minutes, puis essayez d'accéder.
  24. It depends if that IP is part of known VPN IPs, if not then it may work but there is no guarantee
  25. Great to hear that! I've approved you for Early Access, you can find it here: https://forum.netduma.com/forum/144-netduma-r2-early-access/
×
×
  • Create New...