× Introducing the Orbi 970 Series Mesh System with WiFi 7 technology. For more information visit the NETGEAR Press Room.
Orbi WiFi 7 RBE973
Reply

BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

Retired_Member
Not applicable

BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

Qos Stopped detecting CSGO while i was playing a few days ago

 

What ive tried

- rebooting router

- removing and adding source/csgo to qos

- enabling All Devices DumaOS Classified Games.

- resetting router to factory settings

- downgrading router to 2.3.2.66 from 2.3.2.104

- resetting router to factory settings again

- cmd ipconfig to confirm ip, changing device name in router, adding csgo to qos

- formatting pc

- manually adding csgo ports, cant overlapping streams, maybe im doing it wrong

Steam Support Article

other games show High Priority Traffic Detected like PUBG

other source games show High Priority Traffic Detected like TF2

Model: XR500|Nighthawk Pro Gaming Router
Message 1 of 6

Accepted Solutions
Retired_Member
Not applicable

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

I appreciate the days of replys, I finally got it working, here is the steps to get it fixed.

 

Reset Router to Factory Settings:

Settings - Administration - Backup Settings - Erase

 

Manually Update Firmware - download

Settings - Administration - Firmware Update - Browse

 

     tested on firmware - XR500-V2.3.2.56.img

          updated to - XR500-V2.3.2.66 - added QOS still works

 

Add Advanced QOS

Source Port

Start 1, End 65535

Destination Port

Start 27000, End 27100

Protocol, TCP & UDP

View solution in original post

Message 5 of 6

All Replies
Netduma-Fraser
NetDuma Partner

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

Likely that we need to update the service, how did you specifically add the ports manually? What are the rules you made?
Message 2 of 6
Retired_Member
Not applicable

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

when manually adding ports i tried

 

Source Port

Start 1, End 65535

Destination Port

Start 27000, End 27100

Protocol, UDP

 

Source Port

Start 27000, End 27100

Destination Port

Start 27000, End 27100

Protocol, UDP

 

Source Port

Start 27020, End 27039

Destination Port

Start 27000, End 27100

Protocol, UDP

 

Source Port

Start 27015, End 27015

Destination Port

Start 27020, End 27039

Protocol, UDP

 

with many variation of these numbers and protocol

 

based on the Steam Client ports shown

  • UDP remote port 27000--27100: Game traffic
  • UDP local port 27015 (default): gameplay traffic

 this netduma article to help-classify-games-for-traffic-prioritization

 but it shows source as IPv4 Address so i dont fully understand this tutorial yet

Message 3 of 6
Netduma-Fraser
NetDuma Partner

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

You had the right idea with the first rule but change it to TCP/UDP as you're missing those and they are needed. Also add one rule along the same lines as the first so source the same but destination 4380 UDP. Then remove the other rules and see if it works.
Message 4 of 6
Retired_Member
Not applicable

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

I appreciate the days of replys, I finally got it working, here is the steps to get it fixed.

 

Reset Router to Factory Settings:

Settings - Administration - Backup Settings - Erase

 

Manually Update Firmware - download

Settings - Administration - Firmware Update - Browse

 

     tested on firmware - XR500-V2.3.2.56.img

          updated to - XR500-V2.3.2.66 - added QOS still works

 

Add Advanced QOS

Source Port

Start 1, End 65535

Destination Port

Start 27000, End 27100

Protocol, TCP & UDP

Message 5 of 6
Netduma-Fraser
NetDuma Partner

Re: BUG: Qos stopped detecting CSGO - XR500 V2.3.2.66

Glad you got it working and thanks for the update with the solution.
Message 6 of 6
Discussion stats
  • 5 replies
  • 3003 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7