Jump to content

Netduma Fraser

Administrators
  • Posts

    86949
  • Joined

  • Days Won

    1895

Everything posted by Netduma Fraser

  1. We get loads of PMs that's why we focus on support on the forum, I only have one PM from you saying you've sent some previously but I don't have those and I can't see any emails on the Netduma account if you used the email associated with your forum account? If you need anything in the future please make a topic and we can help out and reply much faster than PMs. Thanks for submitting IDs to the cloud form, we don't reply to anyone that has submitted IDs to the form or update them on when it is done, people submit them and when we're able to we put them in the cloud.
  2. Well if you notice the Geo-Filter ping becoming higher or more unstable, Connection Benchmark results becoming worse despite no changes and then changing QoS to counteract it could be helpful
  3. Not much we can do to troubleshoot/diagnose that unfortunately but if you find any stats that appear different that would be really helpful for us
  4. Thank you for the feedback, that's an interesting observation, is the delay felt or is it seen in the Geo-Filter ping for example? What surface is the router on?
  5. I meant the error could have happened due to deleting a device but reset is the go to fix for this currently
  6. That could've been deleting the device itself and why a normal reset fixed it
  7. It is quite possible restoring the config could cause that, especially if the IP address or name of the device changed which could also be contributing to it without restoring, we should be able to resolve that but it shouldn't appear to happen too often
  8. So basically the error occurs when a device has been added to the Geo-Filter but that device then gets removed completely from the router for example so if you deleted it from the Device Manager but didn't remove it from the Geo-Filter is one cause. So yes likely the config is bringing back the device to the Geo-Filter but its not connected to the router. So a clean factory reset will fix it.
  9. We're not utilizing the notification system just yet so you'll have to check the beta forum to see if we've posted a new version
  10. No need to flush the cloud, the cloud update would already have been uploaded to the router. It's just how you normally filter, put your location/radius over a server/region you want to connect to, strict mode on in the Geo-Filter Map menu, Ping Assist 0 and then search. If you do notice that you get kicked just before the game have a look on the Geo-Filter and there will be something blocked. Ping this (if needed can turn Auto Ping off in the menu) then name it and click allow on the ping panel and you should be able to get a game after that - it could take a few times allowing these servers. If you do come across servers you need to allow please let us know the IDs and we'll add them to our allow list.
  11. As an in encrypted key that will allow access to the R1 remotely, as we've not accessed an R1 in a long time they're trying to find that so they can access your unit.
  12. That's a local IP so we couldn't join off that, I think your IP has stayed the same though. The dev said they're missing a key they need to access so trying to get that first and then they should be able to access.
  13. Okay great, double check the DMZ on the ISP modem so thats still correct and I'll see what the dev says tomorrow once they're back in
  14. The PC actually has that as its IP address or says that's the gateway address? Without access to the interface, you'll either need to factory reset or reboot - if you're going to reboot unplug it for 10 minutes, then plug in, wait 2 minutes and attempt access
  15. I'm checking with the dev now to see if they made a connection, what IP is your device getting that is connected to the R1?
  16. We have and we're working on it for this next sprint
  17. Adblocker isn't available on any of the XR routers at the moment
  18. Very odd but great to hear that, thanks for letting us know!
  19. Are you asking or saying it is working?
  20. Sounds about average for your connection then unfortunately, maybe they will be able to do something though!
  21. We have reproduced the chat issue, just a case of narrowing down why that's happening so it's definitely something we'll be able to fix. As it's shared, have you checked really late at night/very early in the morning to see if the ping/packet loss is reduced? Packet loss is normal to a certain extent but it's usually less than 1% on a decent line so being shared I can see that probably being about average - I don't know too much about it but that would be my expectation, especially if it does reduce during quiet times
  22. It might be we need more settings available for IPv6 which I have requested before that can work. Though it shouldn't be too much of an issue not receiving pings, won't be related to chat as that's not working on IPv4 either. If it happens direct to the modem then you're definitely barking up the right tree, could even be the modem itself.
  23. You can keep it disabled if you think that might be helping with the disconnects. That's right, I suspect if you enable that then the test will not mention that as a problem
  24. Glad to hear it! Port Scan Protection is enabled by default so is recommended but it's up to you. I'll get the team to update heatmap again. Have you disabled respond to ping by any chance in settings?
  25. You only need one router really as they all run DumaOS. What is the exact issue you're having with FIFA? Did you try that method I linked then?
×
×
  • Create New...