Jump to content

Netduma Fraser

Administrators
  • Posts

    87510
  • Joined

  • Days Won

    1947

Everything posted by Netduma Fraser

  1. Ah no that usually means for example, the WiFi from one router - for example, if one was connected to your upstream ISP router WiFi and one to the R3 it wouldn't work
  2. Do a factory reset, there will have been a lot of changes made, especially to the Geo-Filter on that firmware
  3. If you split the bands then have one device on 2.4 and one on 5GHz then it should work. Once the next firmware is available that'll be fixed so you can combine the bands again
  4. If they said you don't need to use their modem then yes in theory that should work fine. If you still have issues let us know more details and we can help.
  5. I'm not a dev so I don't know the details like they do, based on what the logs mention I think we have done some work in those areas so it might help
  6. It would be better to have Ping Assist at 0 and cover an area around you - I don't know your region but there should be a few servers there at least, try with a 1000km range to start
  7. We have a firmware in testing currently that resolves the main issues, if that works as expected it should be out soon
  8. You don't have to worry about that due to how you have it setup so that is fine. What was the router/modem you had before - did you get full speeds through that? Whatever it was get its MAC address and in Settings on the R3 make it use that make address, reboot from the interface and see if the speeds are any better please.
  9. Good question above, if you gave it a random static IP rather than the one it had already then you would need to restart the console for it to get the new one
  10. Yes it would, you'd just need to connect the R3 to that router
  11. The server on Heatmap won't necessarily be the exact server you're playing on so the pings may differ sometimes. As in Geo-Filter reports normal ping rather than normal ping + VPN ping?
  12. Don't setup a static IP on either router or console and you shouldn't get the error or set it up in Settings > DHCP on the router and leave it automatic on the console
  13. Thanks for the information, this should be sorted soon!
  14. What do you mean IP address issues? What actually happens?
  15. Great to hear, thanks for the update
  16. That's great thank you, I'll pass it on
  17. I don't want you to do so I was just checking as it could have been a potential reason. If you wait that 30 seconds does it then work?
  18. Did you get that from an auto update?
  19. That's great thanks, we think we've fixed it now so should be sorted for the next firmware!
  20. I think that'll be the max you can get on this firmware then, the next firmware *might* help but not a guarantee
  21. I suspect this is more about DDoSing, lag switching etc as the router is a router, it provides internet, it determines what you can and can't connect to, nothing that could be detected as wrongdoing there
  22. Thank you, where roughly are you located? The server definitely is in LA. I've tried tracing the IP and as expected it's timing out so a theory I have, though we have a couple is that it's not able to ping and so taking the last hop it can get. We'll look into it.
  23. On the Device Manager page click the icon top right and resync the cloud then try again and see if it picks it up please. Also what firmware version are you on currently?
  24. I don't recall anyone specifying an issue with this? If it's the WiFi issue where using two devices on 2.4GHz for example isn't working and one needs to be on 2.4 and the other 5 then this is fixed for the next version
×
×
  • Create New...