Phantomblu

It also happens to me with a 100 megabit line.

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?