Bert

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

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.

To be honest I never felt like that did anything. I use no QoS and full bandwidth, just traffic prioritization. There is a way around this though. Get the cheapest manageable switch you can find that allows you to set port rates and use that between your Xbox and the router. For example Netgear GS305E, about $25 on Amazon, 5 port switch, managable and has port rate limiting.

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.

Yeah you are right but he said he doesn't use wifi, it was specific to his use case Same for me, my connection is split into 2 VLAN's from my ISP, one for home use and one for gaming. I use wifi only on the first one, the gaming one has it turned off so the R1 is sufficient there. The only issue is CPU power if you want to run QoS, you're kind of limited to 300mbit on a R1. For a home router for a family the R1 is long outdated. Even before the XR series came out it wasn't sufficient, I was using it with a 5Ghz AP.

You don't even need the XR500 in your case tbh. I have exactly the same setup, 1 PC and 1 PS4 and wifi turned off. R1 runs this fine altough if you want QoS the bandwidth will become a issue and PPPoE support is an issue. I'm running the R1 now instead of the XR500 and really it performs practically no different in game. The only thing is I need to use my ISP router as well, while I generally run PPPoE on the XR500.

If I turn off crossplay in WZ you can sometimes find a match but usually the lobby is only half full and it takes ages. There is another factor to it, the other console players that have crossplay turned on will connect to the crossplay lobbies and not you. The game pushes crossplay really hard, like when you search it gives you about 3 seconds and then it pops a notification that you should turn on crossplay.

That is your issue probably. Most WZ players in the area is on PC. I turn crossplay on for WZ but off for MP.