Bert

PS4: Sliders 90% QoS SRC 3074 - DST 30000:45000 Geofilter on uPNP on Shared excess all Custom DiffServ QoS on switches Just started playing WZ on PC yesterday and it's spot on without any form of QoS / Geofilter etc. Ping between 19 and 27ms depending on server. (in game dashboard)

Actually wondering why you switched a XR700 for a XR1000. The XR700 wifi is quite solid and in terms of raw power and connectivity is actually ahead of the XR1000. XR1000 is more the follow up to the XR500 rather than the XR700.

The whole point of QoS on inbound traffic is WiFi. Your bandwidth coming from WAN is almost always smaller than bandwidth available to LAN since you have 1Gbit ports. In worst case scenario it’s equal with gigabit internet. So in reality there is never any sort of restriction there unless you have some funny setup with WiFi bridges or a 100mbit switch. And even if you connect to a 100mbit switch traffic is passed to the routers internal switch at a much higher rate. And that has it’s own packet buffer. Plus typically we have limited our WAN bandwidth anyway by the ABB sliders so QoS will literally do nothing there. Wifi is a different ballgame as bandwidth to your device is smaller than WAN. And also we have to deal with variable bandwidth. Ie the Xbox that is in the other end of the house might be only getting 30mbit. So in case where we have 1GBit internet and dodgy WiFi you can create bufferbloat yourself. And that’s not even counting multiple devices etc. You can probably set the identifier Gaming / Voice on LAN but it won’t do much good since you’re not restricted and your devices don’t understand these identifiers anyway. Your switches need to be able to process DSCP tags as well for it to have any effect.

If you look at Amazon and other places you can often buy small cheap barebones PCs with dual network cards. Install something like Untangle or OpenWrt x86-64 and it will basicly blow every residential or gaming router out of the water. Then you can definitly do SQM at gigabit speed.

CoDeL manages latency across the ques. It works really well but also it’s very CPU intensive. There is no routers that I know of for home use that can do this at gigabit speed. This is because it requires the configuration of many traffic classes, and different priority weights. Downside of codel is that it increases absolute latency a little bit over other forms like PFIFO. It also depends on how you measure. Like DSL reports measures latency by sending http GET requests. Not ICMP ping. This sort of traffic is exactly what CoDeL is meant to optimize. Whereas the XR routers use PFIFO and say you have gaming traffic optimized, it won,t do anything to these GET requests. But QoS does work when you’re actually gaming. I have never tried it but possibly if you configure your XR router for that type of traffic you will see a improvement in bufferbloat ratings. It doesn’t necessarily produce real world results though. That said, CoDeL is the better option for all round general use if you have the CPU power to run it.

If you look at your Wireshark captures you will probably find that the outgoing packets have destination and ports reversed. So when you make a rule in DumaOS saying: PS4 source 3074-3074 destination 1-65535 it makes 2 ques: ETH: source 1-65535 any IP destination 3074-3074 PS4 IP WAN1: Source 3074 PS4 IP destination 1-65535 any IP It’s just to simplify the setup. You could say source in DumaOS is equal to local host in Asus.

Different router brands have different notations for this. Some other let you specify both inbound and outbound separately and some always assume source to be the sender. DumaOS combines both directions but in reality inbounds means forwarding incoming WAN traffic to LAN and vice versa. On more professional systems you would add a rule to the WAN interface SRC 3074 DST 30000-45000 and Ethernet interface SRC 30000-45000 DST 3074. The rule is always applied to sending traffic since the interface can not control the receiving side. Ie you can not control what you will receive over the internet. also it’s really simple to check if you’re rule is actually working. Look at the packet counter, for games WW2 and later it should add 60 packets under ‘prioritized’ for every second you play the game, both inbound and outbound. Unless it’s private games they have different tickrates in a lot of cases. TCP is only used for communication to the back end servers, uploading stats etc so doesn’t affect your gameplay.

You wouldn’t be blaming hitdetection for your loss if you were that good at the game These traffic prio rules only function under the condition that your line is congested. Then it works because you get a buildup of packets in the sending que and it can put game traffic in front of the que. If no congestion occurs then each packet is send inmediately and the rule does nothing. Running QoS requires packet inspection and that does add latency, this is the trade-off for running QoS on your system. So therefore in situations with symmetrical connections with very few devices I would always recommend turning off QoS totally as this gives you the cleanest path for traffic. Ie I have 600/40 connection in one house where that connection services the whole home, there I have QoS on because it’s easy to congest a 40mbit upload line. In my other house I have 2x 600/600 WAN and the connection that is used for gaming doesn’t use QoS at all since I never congest it with just 1 PS4 and 1PC. As for DumaOS classified games vs manual rules. You could argue that other UDP traffic will try to get in front of your gaming traffic (DumaOS classified games simply prioritizes UDP 1024-65535) but in reality this is not noticeable unless you are running something special that generates a huge UDP stream. And here again, it would require the line to be congested in the first place. Also you could add the device as game console and then it simply prioritizes UDP traffic to that device. The only reason I use a manual rule is so that my bandwidth is not restricted when the game is running idle in the menu. There is really no magic traffic prioritization rule. You will find many topics about it, people have spend countless hours with wireshark etc but none have the magic answer.

I have used them both (manual rules and duma classified games) and know for fact there is no difference.

The point was that both traffic prioritization and DMZ have totally different functions and have nothing to do with eachother. If a user wants to use QoS they need to set this up separately from DMZ.

They have nothing to do with eachother. DMZ places the device outside your firewall so it’s something you should never do with a PC. Traffic prioritization lets packets jump the que so to say. But if you select all ports there is no point since all traffic goes through the priority que. For 99.99% messing with these port ranges is not necessary and simply turning on DumaOS classified games is sufficient. Or simply select your device and select the games console setting.

You need to specify its UDP. I have source 3074-3076 destination 30.000-45.000 but the above will also work. my rule only comes on when you’re in the lobby so there is game traffic, it will turn off when you’re idle in the menu. Also 3076 is only because I have multiple ps4s, with only on console you can also set 3074-3074.

Actually youu don't. For CoD, 3704 for local / source port and the destination port in the range where it connects to the server, ie I have 30.000-45.000. And it needs to be set for UDP only. The inverse rule is automatically applied by DumaOS so you don't need to add a second rule. This was confirmed long time ago by wireshark. But you are right I see the most fantastic port configurations in this topic Also people that think that adding QoS rules will make their game better when they are having 2 devices connected while using a 1Gbit internet connection LOL.

1. Traffic priority on or off. (This used to be visible in the traffic overview widget, not anymore currently) 2. Bandwidth sliders 3. Bandwidth in use 4. Ping to host 5. Geofilter on/off

Mine is: Community name: BertAnsink Email: [email protected]

LOL this. I signed up on day 1 for the XR500 beta. Nothing. But apperantly everybody who signed up last week and now asks gets bumped.

The one that is active is the only one you need

To be fairly honest, I expect that the no QOS 890mbit simply has to do with the connection efficiency. It's just confusing that it gets mentioned like that. There is no hardware limiting it in that case, it's just limited by LAN performance. Like if you use a 1Gbit network adapter it's rare that you ever get above 940ish mbit. This is also most likely the reason they sell that package as 940mbit, it's what their ISP supplied router can manage and they won't advertise it as 1000 because it would have people complaining that they are not able to see those speeds in a speedtest. Also, generally when you set up any sort of QoS you typically loose out on a bit of available bandwidth. Like in DumaOS you set the ABB sliders but with a automated QoS system like CAKE or fq_codel you generally enter speeds 5-15% lower of what your actual speeds are. So if it can do 821mbit with QoS running that's perfectly fine. Last, unless you are really heavy on bandwidth usage, you won't need QoS that much with gigabit speeds.

There was output numbers mentioned in a topic in the CoD section. Basicly 890 mbit QoS off and 860 mbit QoS on.

Not really actually, unless you have a ton of devices running. Because they are also restricted from the sender. For example if you watch YT or Netflix. They will send you data in bursts so you can buffer it. But if you have a 1000/1000 connection these data bursts will not choke up 1000 mbit, because they limit their sending rates. TCP/IP will try to max out your connection in theory yes, but in real world scenario's this practically never happens at those speeds. That is why QoS is more important on low bandwidth connections vs very high bandwidth connections. So if you own a high bandwidth connection, it's simply a matter of looking at your usage. Do you need QoS yes or no. And if yes, what hardware do you need to run your connection with QoS enabled. This varies as different types of QoS can be more CPU intensive over others.

If you push that kind of bandwidth you're not likely to need QoS much. Unless you have a lot of devices etc but then a more powerful solution would be preferred anyhow.

To be fairly honest, I think it's also because there is less of a market for the XR700. It's a niche product compared to the XR500. The biggest failure of the XR700 is supplying only 1 SFP port. Because of this, you either have the option of running a 2.5-5-10G internet connection, but you have no way to transmit this to your network, outside of wifi. Or, you run a 1000/1000 internet connection and use the 10G port to link up to a 10G capable switch or a NAS. This is really the best use case scenario. Where this comes in handy is if you are doing a lot of streaming from local sources. Since you could run a NAS or something else at 10G instead of gigabit. That eliminates any sort of congestion. Or use link aggregation to the NAS and hook up a 10G switch. Your devices can make full use of the NAS without congesting the link between router and switch. If it had 2 SFP ports you could run 10G LAN and link up to a 10G switch. This would have been a much better scenario altough by the time 10G LAN will become mainstream, the wifi is outdated anyhow.

As for the shipping price. You get a discount on the pre-order so if you wait until later when there is cheaper options you're still paying more.

I don't really understand this as I am able to get a good 300+ mbit out of the R1 with QoS enabled. The newer DumaOS versions are a bit more CPU intensive, on original FW I could get 400+ mbit. Unless you're running PPPoE mode or something.

Do you know this from actual testing? That would be a serious letdown if it can't handle a gigabit connection since that is rapidly becoming the standard in most places.