Bert

Can you add me to the list too? Can test both R1 and XR500 if needed.

Actually no need to reset the console, just close and restart the game.

33-6 on shoothouse TDM today, one death due to a clumsy RPG suicide LOL. A bit campy when I was getting my helicopter and my enemies weren't he best obviously.

There can be many reasons for this, especially if it's peer hosted. One is that when DumaOS pings the server you usually don't get a reply from the server, as these don't respond to ICMP ping. So it's reporting the hub just before that. Two is that same as one, the peer that you ping might not respond to ICMP requests and especially on crappy DSL / Cable connections it takes ping of a ISP hub and real latency to the host is much higher. Third is that not only you will have higer latency on wifi, but the host might also be playing on wifi and thus further increasing latency. Forth is that DumaOS measures actual ICMP ping where the game calculates latency via UDP traffic. So these don't necessarily return the same value due to congestion issues etc.

I can only say that I haven't noticed this. My uptime at the moment 4 days 8 hours. Upload prioritized 1.30M Upload background 10.44M Download prioritized 1.27M Download background 20.58M The prioritized counters run up a bit when CoD sits idling in the menu but they seem to be equal going in and out. Only rule I am using is SRC 3074:3074 DST 30.000-45.000. See what happens when I leave it for a good while.

You can leave MTU on auto in your PS4. MTU works by auto discovery, if one link between you or the server is below 1500 then this will get corrected automaticly. I would make a IP reservation for your PS4 if you need a fixed IP for something, like port forwarding etc. I did that anyway even though I don't use port forwarding at the moment.

You will always see a difference in data rate coming from the server, in a game like CoD for example you are only sending your own player data but you are receiving data from 11 other players and yourself. So the packets coming from the host are bigger. That said. I do remember something that the option DumaOS Classified games only prioritizes packets below a certain amount of bytes. (Not sure of this, devs would have to confim) So maybe it's a programming issue where it just doesn't tag traffic like you said. On the other hand, if you divide the 2 figures it would mean you have a 6% packetloss. Not an implausible figure. One other thing is also that CoD sends data to the backend servers alongside game data. Things like stats are uploaded realtime. In my case this stream is also coming off port 3074 together with game traffic from 3074. This is also why QoS stays active when you sit idle in the menu. Since you have 57344 as source port this might not be the case for you. When I change my setup to where I go through my PC, the source port changes but for some reason backend communication stays at 3074. And the other thing is your game needs to have symmetrical tickrates. WW2, BO4 and MW have 60Hz servers so 60 packets per seconds up and down. But games prior to that didn't necessarily follow that scheme. IW for example had a 100Hz client tickrate but a 20Hz host tickrate. So you would be sending 5 times as much packets as downloading. And last thing, you have 2 rules in your QoS setting. I find that if you set for example SRC 3074:3074 to 30000-45000 it works in both directions. So there is no need for the inverse rule. You might actually be tagging other traffic for QoS that's not game related. Not saying you are not on to something by the way, but there is other possibilities as to why it seems this way.

There is one thing with this though, you cannot really duplicate packets you didn't receive in the first place.

Doesn't need to be, it can be in the middle as well. Like the issue I always have with the Japan serverfarm. During peak hours I get huge fluctuations and a lot of in game jitter, while netduma shows a rock solid ping graph. It's because my UDP traffic is being buffered & dropped somewhere along the route. The closer you are to the server the less likely you will have these issues though.

It's a bit different for everybody. I can't really tell the difference between manual port ranges, a single port like the tool does or simply adding the console setting. Even if I do away with QoS altogether it still works fine for me. I plan to do a heap of tests in a week or so when I am back in Europe. My connection there has lower ping but is far more demanding on QoS due to the low upload. Then I can also see what it is that makes the tool not work in MW for me. Because I think it connects to a different backend server in Europe and USA. Agree though it would be awesome if it was a R-App. Or even if we had a R-App that just shows you which ports are used, or even integrate this in the Autoping screen next to all the other host data.

This SQM is incredibly CPU intensive as far as I know. On edgerouters, the X model tops out between 100-200mbit and your basicly need the Edgerouter 4 or 6 model to achieve anything close to 500Mbit. That's probably why your speeds are so low.

You can try. But really if you connect through internet sharing your Netduma should not recognize your console. To the netduma it appears that the traffic is coming from your PC. That's why you need to set your PC as gaming console in DumaOS.

I have auto for these settings, let DHCP on XR500 supply those. But they should not be having any influence on your geofilter.

This would actually be a great addition. For some reason when I go through my PC I get the game data stream on some port around 62.000 instead of 3074. Using your own port would be very beneficial.

I did just play a game of BO4 and it works flawless in that game. Packetcount and everything checks out. It won't actually detect a server until the game starts and the IP in the tool matches the server IP in DumaOS. It's only MW where it isn't working right for me. I think it's purely the fact that we don't have a backend server in Singapore in BO4, In MW it confuses the tool somehow having 2 different datastreams coming off port 3074.

I tried it on a game of infected and the first target was 32030 which is pretty normal, after it jumped 30070 which is normal range for the Singapore backend server. And when I tried a second game it jumped to 30070 again. Also the packet count in QoS is not what you would expect. I'm not getting 60 packets per sec, but just a few every now and then. The domain reported by DumaOS resolves to 13.228.24.173 When I stop the utility it leaves me with 18.139.85.95 Both is AWS Datacenter.

The game communicates with the back end server / matchmaking server while sitting in the lobby and also during the game. And then there is a separate traffic stream going to the actual game server. In normal circumstances both these originate from port 3074 on PS4. I don't know if it makes a difference but in my case the backend server is located in the same Singapore AWS datacenter as the actual game server (there is 2 locations for backend / matchmaking AFAIK, one in Ireland and one in Singapore) When I ran my setup through my PC the external port actually changed to high 6x.xxxx while backend communication remained at 3074. I don't know why this is, but here I was able to separate both communications because of the changed source port. Under the priority rule that everybody was using before, say SRC 3074:3074 to DST 30.000-45.000 it often also includes communication with the backend / matchmaking server, or at least for me, maybe the port numbers are different for others. It probably picks up the backend server first and holds on to that because this connection remains active. I will try a bit more later but maybe you need to be already in the pregame lobby or loaded into the game when you start it on auto?

Actually that was too soon. It picks up communication with the backend server and put's that in hyperlane, but it doesn't prioritize game traffic

The new version works for me

@F1RE-BUG No but then you have a FTTH connection. FTTH/FTTP = Fiber To The Home / Fiber To The Premises. Here you have a fiberoptic cable entering your house and that plugs either in a ONT or ISP supplied router/ONT. The ONT is basicly just a signal conversion however often they can also do other stuff like QoS etc. In this case you can plug your XR500 straight into the ONT. Or like I have, I have my fiber connector straight into the SFP+ module on a switch, connected with s SC module. This connection is often symmetrical ie 100/100, 500/500 etc. It's easily possible because RX and TX on a fiber line have different frequencies. If you have 200/200 that's simply a limit set by your provider but the line can easily handle 1000/1000 and upwards in most cases. FTTC = Fiber To The Cabinet. In this case you have a fiber connection to a central point in your neighborhood and you use a xDSL line to connect to the fiber point. So in this case you do need a modem. Because of limits in the xDSL technology you often have a asymmetrical line because DSL is limited in how much data it can transmit & recieve by the amount of channels it uses. This is also why you often see that xDSL providers have lower speed ratings in their outer service regions, because of signal noise interference they can't guarantee a certain speed.

Then in that case ask your provider if they can set it to bridge mode. You just plug the XR500 in the LAN1 port on the modem/router. You need to ask your ISP but most times in bridge you will need to use PPPoE details in your XR500. If they can't do bridge mode or you want it to handle PPPoE at the modem/router, put it in DMZ.

Depends on. If your modem and ISP router are separate then you should be able to plug your XR500 into the modem like that and take out the ISP router. You then enter your PPPoE details in the XR500 and it should work. A lot of times you also need to add a VLAN tag but this is specific to the ISP (sometimes their modem/ONT handles this, sometimes the router, or some don't use it) When you use the words modem and you have a 100/10 connection I'd venture to say its a FTTC connection where you connect to the fiber cabinet by DSL. These often don't use VLAN tagging so just PPPoE details is enough. You might have to use the MAC adress cloning function. If it's a integrated modem/router you probably have to connect to a LAN port and just use DMZ with your XR500.

@Daniele at which step do you get stuck?

Appreciate the effort you put into it!

It really depends on what sort of connection and modem. Like I use fiber and just plug it into the ONT, enter PPPoE + VLAN details in the XR500 and it works. But if you have a modem that handles PPPoE for you you might be able to just leave it on DHCP. More info is needed.