Jump to content

Netduma Liam

Members
  • Posts

    7651
  • Joined

  • Last visited

  • Days Won

    131

Everything posted by Netduma Liam

  1. Are you running the VPN client on your PC? If so it's then going to be impossible for Geo-filter to detect 'Call of Duty' traffic and filter server. Disable the VPN and try again if that's the case.
  2. Are there any icons appearing on the map when you're joining a game on MW2? Can you provide a screenshot of what you're seeing in Geo-filter when you connect to a game?
  3. It means it took longer than it was expecting, it's likely that it was still successful though.
  4. Make sure you've always got filtering mode enabled for you device, I notice in your earlier screenshots you had it disable. That's why you were getting connected to SA servers initially. I would expect you have a really high ping to European servers, so it may be that the game client is reluctant to connect to them as your experience in game will be pretty poor.
  5. Welcome to the forum! Have you got Congestion Control set to 'Always' when testing with Connection Benchmark? Do you know if you require PPPoE, VLAN or DHCP identifiers in order to get a connection to the internet? What ping does Geo-filter show you getting to the server and how does this compare to what you're seeing in game?
  6. You can do, just add both devices to Traffic Prio and select 'Games Console' as the service. Then disable all other rules. The only issue then may be that because both devices are going through the priority queue, they are technically competing with each other. Gaming requires such little bandwidth that hopefully this won't be a problem for you.
  7. Apologies, this is an issue with Blizzard/Activision changing their server information frequently. They tend to do this upon the release of a new game. We're working on getting it updated again, you should be able to resync cloud later on today and see the servers again.
  8. How exactly did you recover the R2 the first time? Unfortunately the logs appear to be captures shortly after it booted, so there isn't any record in there of any problems.
  9. OK, for QoS to work properly you need to have all devices on the network connected to the R2, so it has full control over the network. You could try lowering the Download slider in Congestion control down to about 70%, drop upload to 95%/ Then, disable all rules in Traffic Prio except the 'Games Console' rule.
  10. Yes, please disable these for now and add the rule I mentioned.
  11. Use this URL specifically: http://192.168.1.1
  12. Accédez au panneau Geo-filter et désactivez le mode de filtrage pour votre appareil.
  13. OK, it sounds like the initial reset you've done didn't work properly. My advice would be to hold the reset pin again for 30 seconds, leave the R2 for 5 minutes, then try accessing the setup wizard again.
  14. Yes, that's because these devices are strictly limited to their allocation and cannot borrow from other devices. That's the only way to specifically hard limit a device though.
  15. Il est conseillé de réinitialiser les paramètres d'usine après une mise à niveau pour s'assurer qu'aucun problème n'est reporté du micrologiciel précédent. Assurez-vous d'être connecté directement au routeur DumaOS lorsque vous essayez d'accéder au tableau de bord. Pourriez-vous s'il vous plaît préciser exactement quel routeur vous utilisez, est-ce le R1 ?
  16. OK, can you remove the power cable from the R2 for 10 minutes, then reconnect it again and see if the setup wizard is able to load properly after that?
  17. Yep, you got it. If you DMZ the Asus router in the R2, you may indeed find problems in game and using the internet in general.
  18. Pourriez-vous s'il vous plaît ouvrir votre propre sujet et décrire autant que possible votre problème ? De cette façon, nous pouvons nous concentrer spécifiquement sur votre problème dans votre propre sujet.
  19. You can use bandwidth allocation, with Share Excess disabled from the submenu in Bandwidth Allocation. You can then limit the bandwidth to specific devices.
  20. That's already been added, I don't know whether it'll be in the next release or the one immediately after, but it won't be long!
  21. Welcome to the forum! Are all devices connected directly to the R2? Can you send over a screenshot of how you've currently got QoS configured?
  22. Are you only seeing this on your PC? If you access the interface from a different device, do you still get the same error?
  23. You've already got that profile added to Geo-filter, so it won't add it because the same profile already exists.
  24. Move the sliders back up to about 70%, then go down to Traffic Prio and disable all rules. Add a new rules, select your gaming device and select 'Games Console' as the service. Test that and see how it feels.
  25. Can you connect directly to the R2 via ethernet and see if you're able to access the DumaOS interface by going to 192.168.77.1 in your web browser?
×
×
  • Create New...