Jump to content

Netduma Fraser

Administrators
  • Content Count

    25,331
  • Joined

  • Last visited

  • Days Won

    323

Netduma Fraser last won the day on October 15

Netduma Fraser had the most liked content!

About Netduma Fraser

Basic Info

  • Gender
    Male
  • DumaOS Routers Owned
    Netduma R1
    XR500

Recent Profile Visitors

31,082 profile views
  1. Unfortunately we can't give you the answer that you're looking for, when we provide any news/updates that's as soon as we can do that and cannot provide any information beforehand. We've recently posted about what we are working on, hopefully that will give you some hope on what will be coming in the future:
  2. Here's what I suggest: Flush the cloud (if you get the 'too long' message wait a minute after it appears and then refresh the page). Do this while the console is completely off then try again. If that doesn't work then delete all your entries in Allow and Deny. I realise that is frustrating but if they're not working anyway then there is no reason to keep them. Then block as and when you come across those players you want to block. Once blocked, ensure that the connection to that player is completely severed. The easiest way to do that is once you leave the game wait 2 minutes or until the map is completely clear just to be sure. The reason I suggested #2, as much of a pain as it is, is because there was an instance where old denied entries carried over from an old version (not necessarily a firmware version) didn't work on the new version and caused other rules not to work. So by starting fresh it may make the feature work again.
  3. Do you have steam completely shut down before you apply the Geo-Filter/boot up the game? If not do that and then boot up steam/Destiny from the start after applying the Geo-Filter and see if it works then please. Could you make a new topic regarding your issues please? Its hard to properly support you in two other peoples topics.
  4. Do you have steam completely shut down before you apply the Geo-Filter/boot up the game? If not do that and then boot up steam/Destiny from the start after applying the Geo-Filter and see if it works then please.
  5. It could be that you were blocking the US party chat server so you couldn't hear those connected to it. Did you see anything blocked on the map when this happened? If so whitelist that and it should work. Definitely whitelist them as you should only have to do it once (unless their IP changes) and then shouldn't have to worry about it again.
  6. Glad to hear that, thanks for posting back and let us know if it happens again.
  7. No unfortunately not but just keep an eye out for any information/announcements. We do appreciate everyones patience.
  8. It should only be used when you boot up the game but if they're regularly communicating with that server during the game then that could explain why it's better for you. Do you notice if the server gets big and then gets smaller a few times throughout the game?
  9. Hello, welcome to the forum! So that occurs when using the PC as a console device type and if you use it as a PC with the Destiny service? Have you flushed the cloud at all?
  10. If the R1 isn't doing PPPoE itself then it should be okay but let us know after a reboot if it continues to be an issue.
  11. That's fine it's a known bug. When you see that message wait 1 minute and then refresh the page. It will have successfully flushed the cloud.
  12. Yes the update was pushed this week so you can flush the cloud. When you flush the cloud you will likely get a 'took too long to respond' message, don't worry about it, when you see it just wait a minute and then refresh the page and it will have flushed successfully.
  13. Could you provide a screenshot of the Geo-Filter page please showing when this happens?
  14. Okay, if there is something to do with DumaOS then setting the router into AP mode should then bypass that. Could you set it to AP mode please and see if you get the same issue. If you do then we can narrow it down to probably a Netgear settings or hardware issue.
×
×
  • Create New...