Phantomblu

Hi, could I also get early access to the firmware please. Thanks.

On Call of Duty PC to get open NAT via UPNP I switched my connection to private and not public to allow sharing. Then by clicking on the properties of the Duma R3 I shared the ports I needed, in this way I was able to view UPNP working in R3

I got Nat open by disabling UPNP and putting my PC in DMZ, try this way. I'm playing MW3 . Firmware 4.0.21 R3

I got Nat open by disabling UPNP and putting my PC in DMZ, try this way. I'm playing MW3

By doing what you said above you don't get what the filter was created for, the pings are low in the game except for 1 or two which are generally very different (in the order of 100 ms fluctuating, perhaps because they have a connection WI-Fi or a VPN). Furthermore, the feeling that the players are not from the limited area, but external and this is because it is not possible to completely isolate the server on which you want to play, in fact I always have to leave not only my closest server (Milan) but also the external server in Ireland otherwise the Call Of Duty Modern Warfare 3 game will not start. Also last night before going to bed I unchecked IPV6 and today when I tried to play the connection was interrupted, the DHCP seemed dead even after setting the static and restoring IPV6, so I had to reset all the settings to be able to connect again (I'm not sure if removing IPV6 triggered the DHCP problem). All in all, however, I like it, I get much more consistent hits and the pings are quite low. The firmware is 4.0.21 and I would be happy to try another firmware if you have it. Thank you P.S. Consider that to start the game I have to start via battlenet and I assume that it asks for authorization from the server in Ireland which works in complicity with the one in Milan to search for people in the game (and this is probably why it is not possible to limit the geofilter area completely )

The same thing happened to me, now I will try the solution expressed in this argument by Fraser. Thank you

You don't even realize it because you play it every day but that's a cheat given to you by the hardware manufacturer of the console, otherwise you wouldn't do anything.

I’d like to be added aswell

7, 9, 10, 13, 17, 19, 21, 45, 52-53, 66-69, 80, 88-89, 376, 443, 500, 547, 1119, 1120, 1343, 1353, 1801, 3074-3080, 3478, 3544, 4379-4380, 4500, 5060-5061, 5351-5355, 6881, 7077, 7117, 8182-8186, 8443, 22885, 27000-27050, 30000-6553

I believe that the protocols used by the game consoles are partly Torrent protocols, it could be a reason, a sort of vpn established by the consoles through those network protocols, because xbox uses gnutella and I could see from edgerouter x, with dpi inspection ....

Surely playing at the North Pole or in Africa or otherwise uncrowded areas, it's not that great ...

I'm not a console player and I played the Cod beta on PC. Normally I play with 200 fps or a little below, for me it is an energy saver since doing so many tests it works well with a 6 ms return to the monitor, it seems excessive to push further. However it is important that the whole system works well ... It is not just the monitor. Latency must be the lowest for the entire game system otherwise it makes no sense. Just yesterday I discovered that I had a latency problem in my operating system due to a Corsair mouse driver and I was unable to kill in game. So lowering the latencies is something difficult to achieve, to give you an example it could happen that the Firmware of your Pad does not work as it should and the whole game system would draw the consequences ....

Buongiorno. Il mio xr500 è aggiornato al firmware 2.3.2.134 e finalmente sembra funzionare bene. Funziona in cascata dietro un Fritzbox 7590, mentre prima (un anno fa), era dietro un router/modem del mio ISP (ISP che ho cambiato) che molto probabilmente aveva bug tali da dare un sacco di problemi al firmware 2.3.2.130. Fatta questa premessa per capire i problemi che ho riscontrato e ringrazio lo staff di NetDuma, vorrei chiedere un altro aiuto: - Attualmente nella fase iniziale dei miei upload rilevo un ritardo iniziale di 200ms mentre nei test DumaOs XR500 di 50 ms che poi scende rapidamente a 10-12 ms.. Questo ritardo lo rilevo facendo vari test di velocità online come OOKLA, NPERF ecc. E facendo anche il test di velocità sulla XR500, indipendentemente dall'impostazione della velocità QOS. Pubblico un'immagine qui sotto.. Mi chiedo cosa puo' dipendere da quell'iniziale ritardo di congestione? Dal Fritzbox stesso o da altri problemi?

I report an open discussion by the staff of 343 about geofilters and I ask the management of the Duma routers what direction to take in this regard .... or in any case if you expect new solutions ... By now it is a well-known practice in the fields of games and companies, not only for Halo Infinite, have noticed it and are taking steps in this regard .... https://forums.halowaypoint.com/t/halo-infinite-update-on-latency-geofiltering/501149 What is geofiltering? Geofiltering is when players manipulate their system files or router settings in an effort to force the matchmaking system to give them matches hosted on servers located near them. Many do so thinking that they are creating their own “server selection” within the matchmaking system, but that is not what’s happening. Instead, they are simply forcing the game to be played on their chosen datacenter, regardless of where the other players in the game are located. Why is it bad? Normally, when a match is created, the matchmaker hosts the game on a server with the best connection for the highest number of players in the lobby. That means sometimes it will select a server that is in between all the players and other times it will pick a server that’s closer to where the majority of the people from the match are located. However, if one of the players in the lobby is geofiltering, they will then force the game to be played on their datacenter. To be clear, this means a geofiltering player’s actions take effect after all of the players have already been selected for the match. This happens because the matchmaking system pulls the lobby together when it still believes that all our data centers would be available to host the game. Then, in the process of picking the best data center to host this match, the manipulation blocks out any servers that the geofiltering player does not allow. When players do this, it creates a small benefit to them at the cost of making the match worse for everyone else. To provide a real-world example, below is a match between players from Regions A, B, and C – where Region B is located in the middle. For this match, picking a server in Region B would be the fairest to all players, with the lowest overall latency. However, the Region C player geofiltered their ping data and forced the match to occur in their region. Here’s a ping comparison (in milliseconds) between what our matchmaker detected and what the players were forced to play on due to a geofiltering player in Region 😄 PLAYER LOCATION EXPECTED PING TO OPTIMAL SERVER IN REGION B ACTUAL PING AFTER BEING GEOFILTERED TO REGION C Region A 67ms 144ms Region A 86ms 155ms Region A 74ms 147ms Region A 61ms 130ms Region B 26ms 94ms Region B 13ms 82ms Region B 26ms 84ms Region C 97ms 40ms As you can see, geofiltering allowed this player to block the optimal server and negatively impact the experience of the entire lobby in a pretty dramatic way. It also wouldn’t feel great to be a player in Region C and get matched into Region B frequently, and further below we share the actions we’re taking to reduce how often that happens. Given the example above, one geofiltering player can degrade the experience of between 7 (Arena) to 23 (BTB) other people per match, meaning they could impact hundreds of people in one gaming session. Then, take those hundreds of lower-quality experiences and multiply that by the total number of players geofiltering around the world, and you can start to see why this practice is harmful to the game and your fellow Halo players. Not to mention, as players are forced on to these higher ping servers, they begin to either geofilter themselves, play the game less, or stop playing entirely. All of which increases the likelihood that the people playing the game normally are going to run into someone who is geofiltering and have a lesser experience. It became a vicious cycle and, as a result, the quality of online matches began to deteriorate at a rapid pace. If geofiltering was acting as a makeshift “server selection” feature, we may have considered turning a blind eye to it. However, since that isn’t the case, we needed to fix it and ensure that players are getting the best experience possible .