Jump to content

Netduma Alex

Administrators
  • Content Count

    732
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Netduma Alex

  1. There has been a hotfix firmware since last time you checked, but I don't think it's addresses your issue. Might be worth a try anyway:
  2. You just need to close the game and open it again once you've changed settings. The idea is that any existing connections to the game servers will be dropped when you close the game. The Geo-Filter only applies it's rules to new connections, so when you change it mid-game, any existing connections might be breaking your rules. The reason we don't apply the rules to existing connections is so that the router can't be used for cheating.
  3. That's strange. Could you try using a Wifi Analyzer app to see which channels are congested near you? The router should be able to figure that out by itself but perhaps a little manual intervention wouldn't hurt?
  4. So you're actually having the opposite problem? Your SFP+ port is much slower than your WAN port?
  5. You could add Destiny 2's ports to Traffic Prioritization and Port Forwarding. Bungie have a list of the ports here: https://www.bungie.net/en/Help/Troubleshoot?oid=13610#PortForwarding
  6. The Netduma results seem to have fewer spikes. Is Anti-Bufferbloat turned on?
  7. I'm surprised that's happening since Ohio isn't close to Mexico at all. One idea might be to put the Geo-Filter in spectating mode, and when you connect to a server which seems like it might be in Mexico, check the Geo-Filter map to see where it is. You can then position the Geo-Filter radius to exclude that server, and then return to filtering mode.
  8. Well if you've whitelisted everybody you want to play with (in spectating mode), then you could make your Geo-Filter radius really small, maybe put it in the ocean, and disable Strict Mode. Then put it in filtering mode and hopefully that will work.
  9. Make sure that you follow this guide exactly to reset the R1: http://support.netduma.com/en/support/solutions/articles/16000094903-how-to-factory-reset-the-netduma-r1-using-the-reset-button Specifically, keep holding until all of the lights blink on and then off.
  10. That's really interesting, i've never come across that here in the UK but maybe they don't do it here yet? It's like moving your router into the street cabinet so you and your neighbors are all on the same subnet, weird.
  11. Do you have Geo-Filter enabled? This might be blocking the downloads. Turn Geo-Filter to Spectating mode and see if that allows downloads again. When you say you "can't download games", does your PS4 get any connection to your router at all? What IP address does the PS4 say it has in Network Status? If possible, could you upload a picture of the View Network Status page on your PS4? Thanks.
  12. Well we can help you with anything related to using Hybrid-VPN, or bypassing restrictions on your DumaOS router to get your VPN working.
  13. What provider are you using for your VPN, and what software are you using? Or do you mean you're attempting to set up a private VPN?
  14. So it was in a tab, but after logging in, it became it's own window? That's interesting, I don't think it's meant to do that. I'll try and recreate it.
  15. Hi all, just a quick one, I've added a field to User Profiles which will allow you to show which DumaOS hardware you own. It's a multiple choice field, so if you own more than one piece of hardware, you can list it. The information will appear in the sidebar, and is useful for two things: We can see which hardware you're talking about when support is needed Bragging rights To enter this info, click your username in the top right and choose Profile. Now press Edit Profile, scroll to the bottom, and tick the boxes for the routers you own. Now press save. At some point in the future we might make this field mandatory, but right now it's optional. Happy gaming!
  16. Nope we've not parted company with NETGEAR and we have no plans to do so. We're still in daily communication with them. We're trying to improve our communication to customers, but NETGEAR have strict policies in this regard and we have to abide by those policies. Not much more I can say right now except that big updates are still on the way.
  17. So the default IP (to access the interface) is 192.168.88.1, the default username and password are admin and password In order to use the Geo-Filter with Destiny 2, you'll need to disable Strict Mode
  18. Sometimes browser extensions will block necessary elements on the router interface. Using a private/incognito window in your browser will bypass these extensions. The other option would be to add an exception for your router's IP in the extensions. For example, tell AdBlock/uBlock not to block anything on "192.168.88.1" or "routerlogin.net" or whatever address you use to access your router. Any extensions that block scripts should also be disabled.
  19. Well i've never tried anything like this, but I think it could work. Have the ASUS router connected to your modem, apply your QoS settings Connect the LAN port of the ASUS to the WAN port on your R1 Go to System Information on R1, write down WAN IP, put this WAN IP into the DMZ on the ASUS Go to QoS on R1, Anti-Bufferbloat menu, tick Disable QoS Connect gaming device to R1, add to Geo-Filter Use Geo-Filter as you normally would Hopefully, by putting the WAN IP into the DMZ of the ASUS, you'll avoid any double-NAT issues.
  20. Oh right, and then the Geo-Filter restarts? Or you have to refresh the page?
  21. I wasn't able to recreate the one where there's a 6 next to some garbled text, but I did manage to get the bufferbloat flower not to appear. I recreated your Dashboard layout and the flower didn't appear, but when I unpinned the Network Map, it reappeared. There might be a problem trying to render both at once.
  22. Are you using Smart Connect or a separate 2.4GHz channel?
  23. I actually asked Luke for input on this question, and he said pretty much what I said, we don't have an answer. All I can tell you is that we have no immediate plans to end support, it's going to be supported for the foreseeable. As I said, we haven't dropped support for a product yet, and we'll support each product for as long as we can. The only reason I could see for dropping a product would be if it wasn't powerful enough to handle the latest updates, and the XR700 is the most powerful product in our lineup.
  24. Right so you mean the Geo-Filter stops responding to input? How do you bring it back from this state?
×
×
  • Create New...