Netduma Fraser

Thanks @Dialatech I've added that to the form. Could you do that if you find any more as it's time consuming for us to go through pictures to get IDs.

Quel a été le pourcentage qui a le plus réduit le ping lorsque votre connexion a atteint son maximum? Je suis surpris que ce soit exactement 70%. TOUS les appareils sont-ils connectés au routeur? Ce serveur est une adresse IP américaine, ce qui explique pourquoi le ping est élevé, est-ce le serveur auquel vous vous connectez? Quel ping obtenez-vous au jeu montré par le Geo-Filter? Cela fait beaucoup de règles, je voudrais simplement les supprimer, désactiver les jeux classés DumaOS et ajouter le PC avec le service de console de jeu. - What did you find was the percentage that lowered the ping the most when your connection was maxed out? I'm surprised that it was exactly 70%. Are ALL devices connected to the router? That server is a US IP so that explains why the ping is high, is that the server you're connecting to? What ping are you getting to the game shown by the Geo-Filter? That is a lot of rules, I would just remove them, disable DumaOS Classified Games and add the PC with the game console service.

Just checked the ID, it shows as Valve Corporation so that is a server, we have it misclassified.

Commencez d'abord par le guide de qualité de service optimal et si ce n'est pas mieux, nous pouvons vous aider à le peaufiner. - First start with the optimal QoS guide and if it isn't any better then we can help you fine tune it. http://support.netduma.com/en/support/solutions/articles/16000077073-dumaos-optimal-settings-guide-qos

En mode Spectateur, il n'aurait pas été filtré du tout, mais en supposant que vous ayez conservé le serveur comme vous l'avez sélectionné dans le jeu, il n'y a pas de différence. Si vous avez de bons jeux en mode Spectation et que vous ne l'avez pas fait, cela ressemble plus à un problème de congestion local. - Spectating Mode it wouldn't have been filtering at all but assuming you kept the server the same that you selected on the game then there is no difference there. If you got good games in Spectating Mode and then you didn't then it sounds more like there is a local congestion issue.

Vous ne pouvez pas conserver exactement le même hôte à la fin du jeu / serveur et vous ne pouvez pas continuer à partir de ce jeu. La sélection du même emplacement de serveur est la meilleure que vous puissiez faire à cet égard. En théorie, vous pouvez littéralement bloquer chaque serveur, même les autres à cet emplacement, mais ce serait une tâche impossible. - You cannot keep the exact same host as the game/server ends and you're not able to do a continuation from that game. Selecting the same server location is the best you can do in this regard. In theory you could literally block every single server even the other ones in this location but it would be an impossible task.

I have just chased this with the team as I think this is something we can fix remotely for everyone without a firmware update. Just waiting to hear back from them to confirm that.

There will be something being blocked on the Geo-Filter when that occurs, look at the Geo-Filter Map quickly and allow the icon that appears blocked and that should resolve it. Please also then let us know the ID so we can whitelist it in the cloud.

If it's fine with QoS completely disabled then it may be a QoS issue, if it isn't then it isn't a QoS issue. If you're doing it from the top right of the interface then you probably already have it and can ignore it, check in System Information to see if you're on the latest version.

I would recommend you leave Bandwidth Allocation default with share excess enabled, consoles don't require much bandwidth at all. With share excess every device will get what it needs and share the excess that devices don't use with the ones that do. As long as you use Anti-Bufferbloat that will prevent local congestion.

It will apply automatically but you can go in to misc settings and click the update/apply button for the cloud twice and that should do it.

That's fine, just wait a minute after that pops up and then refresh the page, it will have applied.

Could you add it to the form here please and if you see any more of them which you likely will as they cluster could you add them also and we'll get out another cloud asap.

It will download automatically within about 4 hours but what Slingshot suggested will allow you to get it sooner.

We won't have touched the whitelist servers recently that I'm aware of, the next we're doing is incorrect server locations. Do you have the ID/IP for that server? It may be a new one that we need to add as we won't have changed that one.

Don't start changing MTU because if you get it wrong then it will cause issues like that as you've seen and 'optimising' MTU will not make a difference when gaming. Find out what the optimum or default for your connection is - probably between 1452 - 1492 and leave it at that. If you're still having issues after that then I would highly suggest you first start experimenting with Anti-Bufferbloat and the Geo-Filter before you go into custom port ranges, no QoS etc as the issues you're having could be related to local congestion or simply picking a bad server that could be avoided by forcing a better one.

What do you mean by an explosion of packets? What is the actual ping you're getting to the game? Are you actually experiencing lag or just wanting it to be super smooth every game as that is not really realistic as there are many variables with the server/game that cannot be controlled.

Judging from the first post as you've mentioned source ports don't overlap at any point unless I've missed it. Perhaps some others can give you advice on what specific ports to use but I personally just use DumaOS Classified Games and find that works for me.

As the other rules you've done have source ports within the 1-65535 range that you're trying to add now they're overlapping. You're essentially doing more than the basic console service or DumaOS Classified Games would, it's a lot more than is needed.

What are the other rules you're trying to add? If you're getting that message then the port has already been covered in one of the ranges that you've added previously.

These features may not be available for awhile although profile saving would probably be the first to be seen. For ping I would suggest you pin auto ping to the dashboard and open the dashboard in a new window and with the help of this old guide you should be able to have it overlay on your stream using OBS https://web.archive.org/web/20170710051950/http://wiki.netduma.com/doku.php?id=embed_ping_to_videos_and_streams

That's definitely a mislocated server, if you could put the details in the form in this topic that would be helpful. Possibly the above but if you've got that mislocated server showing in the US then the game still thinks you're in Europe so will block you from the US games so try forcing where that server isn't and you may find a game faster. Also would suggest you try forcing the East Coast.

I'm almost certain they are but I can ask the team to be sure. Some aspects are saved within cookies as they're more user preference rather than critical to the features e.g. switching between miles/kilometres on the Geo-Filter and so that means less strain on the router - obviously that example wouldn't strain the router but I think you get what I mean. As we add more features it's about squeezing the most out of the router as possible. No, you don't always have a connection to the cloud, periodically the router will connect to the cloud to check it has the latest Geo-Filter database for example, if it has the latest version then the connection is terminated until next time. If it doesn't then it will download this and then terminate the connection. When you use the flush cloud button you make a manual connection to the server and re-download the database regardless.

Thanks for the feedback, we will take it on board and sorry for the inconvinience it caused you. By affect I meant it didn't affect the internet which is what most people would be concerned with immediately.

You should just be able to do a reboot and then if it's still not working properly clearing the cache/cookies should work. The cloud system is there for parts of the router that would need updating frequently, instead of releasing minor firmware releases every week. The parts of the router this affects shouldn't ever cause issues with the routers functionality itself. As mentioned we've ensured this won't happen again.