Bert

Even if you live in the same city you would not get that low of a ping most of the times since traffic has to cross over from your ISP to the datacenter. Similarly, if I do a speedtest on the local server from my ISP which is in the same city, I get 1ms ping. If I use the server of one of the other ISP's here I get 10-15ms ping. For people like him that make a living off streaming the expenses for a enterprise line are tax deductable so he would be crazy if he was playing on a regular ISP connection. These lines are not ultra expensive anyway.

Enterprise 1:1 lease line with direct peering to the datacenter he is connecting to. Expensive but for these guys they can simply deduct it from taxes as business expense.

If you played a few rounds and did well SBMM is most likely also going to get the best of you. If you're on console, playing with crossplay on vs PC players can be quite a handfull. I play MW and CW on PC now and there is quite a difference in performance.

At 1Gbit up and down you should switch off QoS entirely unless you use a huge amount of bandwidth. QoS is the thing that is probably least understood by gamers but it does for sure sell routers. If you are not reaching the maximum of your connection then there is no packets stuck in the queue and QoS will not do anything for you. Also say you have 500mbit. You go testing bufferbloat, adjust it to 400mbit. Great but if you are using the net by yourself and your average traffic use while gaming is 1mbit instead of downloading stuff, here QoS will again do nothing for you. QoS actually slows down your traffic in terms of latency. Generally this little bit of latency is accepted by getting constant performance in return. A household with kids going off a 100/10 connection or so needs QoS but not at 1000/1000. And yes for 1Gbit SQM you need a lot of CPU power. As far as I know only x86-64 routers are capable of doing this at this present time.

If we are talking milliseconds I doubt you are going to see much of a difference. Consoles are not optimized for very low latency networking. There is lots of people here tinkering with QoS / router settings thinking that it will make a difference while in reality this is all per hop basis. They forget that their own switches add latency and your packets travel to the server over 10 hops which don't care about your QoS, and have a variable load depending on the time of day. Plus processing power of DSL and Cable modems generally poses a bigger bottleneck over the current gen dual core and quad core routers. On my PS4's I typically can't tell much of a difference between the XR routers. Also with gaming consoles you are limited in other area's such as a lower screen refresh rate and input lag from your controllers. That makes all this a moot point. As for the last bit. People just want a "turn-key" solution. And generally the market this caters for is on a limited butget, you can see that on sales figures for the previous flagship, the XR700. Super advanced but the $500 price put people off. If power and speed is required it's much simpler to build your own router on a x86-64 box than to use a consumer grade system. The more tech savy crowd could easily manage geo blocking themselves with the right tools, just a matter of scanning the IPs / domains the games connect to and blocking those in the firewall. What makes it time consuming is fishing out the server IP's etc, so if you buy a DumaOS device this is all taken care of. Well that is the quick version, in some games it will break your matchmaking so geofiltering does not always work well. I would say 98% of the DumaOS users are CoD players, where it actually works ok.

It has more to do with use cases than actual speed IMHO. Between my R1, XR500 and XR700 I don't feel that the OS scales well with CPU's and RAM, ie the XR700 does not respond that much faster over the others. As for WAN speed at 400mbit none of these are breaking a sweat. It's like a windows PC, if you have a 10 year old i7 and put it next to a current gen i7 you barely feel the difference if you're just surfing the web. XR500 is probably the best all round router. Simply because the code/firmware has recieved the most updates. It's actually a R7800 with different software. R2 has most features but seems to be lacking a bit in it's wifi strength. Currently not offering WAN side VLAN tagging which can be a nuissance for fiber users that want to do away with their ISP hub. If you need AX wifi then the XR1000 fits the bill. Personally would not upgrade from AC Wave 2 over it unless you specifically have clients that can use this. Otherwise Wifi 6E seems to be more interesting. XR700 provides the lowest amount of latency possible provided you have the other equipment, PC's with 10Gbit networking cards and a SFP+ connection to the router. That's on paper though since in games you won't notice this. The CPU used is one that is normally found in lower end NAS systems. That's also the key feature to this router, it's extra features are more suited to media streaming than gaming. You can connect a dual port NAS to the link aggregation ports and feed your wired + wifi clients or use it as a NAS by feeding it with USB drives and connecting over SFP+. If you just use this as a standalone router it has no advantages over the XR500 since it has the same wifi specs, outside of AD wifi which no clients use, and the more stable and extra features in XR500 3.0 make it more attractive. Misunderstood product, people think you can run 10Gbit WAN but the CPU is too weak to route this (even with professional equipment with X86-64 CPU's routing + firewall 10Gbit is a challenge never mind running advanced QoS) Key point however is that these are all routers meant to be used as a 'all in one device' in a home setting with a mix of maybe 10-20 wired and wifi clients. And in that area they all have their niche. What always confuses me is the different feature sets. Like my XR700 has VPN but no adblocker, I believe my XR500 does have both. Some better consistency in this would help a lot tbh. Saying that, on my 600/600 fiber connection I was still using the R1 + DumaOS 3 because I don't use wifi on that particular connection and QoS is also not needed. It leaves a nice little footprint and can be put under your desk or tucked away in other places. Just it doesn't work well with PPPoE so you always need a ISP router in front of it, something that wasn't necessary with the XR500.

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.

What I usually do on a overprovisioned line is simply put in what you usually get. Then set your ABB sliders below your contract speed. That way you can benefit off it when you're not gaming and run QoS when you are gaming.

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

Plug your WAN cable on the R2 in one of the LAN ports instead. You won't have internet, but the interface will auto negotiate. If it shows 100 mbit on that LAN port in the R2, it's an autonegotiation issue between your other router and the R2, or a cable issue. If the cable is ok there is very little you can do, unless you can set the ports on the Huawai router to 1000mbit. The only thing to try then is placing a switch between your Huawai router and R2, if you have one around. Edit: See that you already did that in one of your first reply's. That indicates a hardware issue with the WAN port, possibly having no signal on one of the pins. 1000 mbit requires all 4 pairs to work, when one strand is faulty then it will default to 100 mbit as that only needs 2 pairs. Change out the R2 under warranty.

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