@HeroesEcho the firmware is pushed out from the CMTS to the modems. That will happen when Rogers releases firmware updates. Either the roll-out is pushed out from the CMTS over a specified timeframe across the network, or it occurs whenever the firmware update is available and the modem is restarted for any reason. At that restart, the modem would load the latest available production firmware.
Not trying to disagree, but thats no longer the case for modems that are already up and runing. Don't know who runs the firmware roll-out, but, the last rollout or two wasn't done by pushing the firmware out across the network on a fixed schedule. So, it looks like this will be decided on a case by case basis. It could be a fixed schedule roll-out, or it could be slowly rolled out as modems across the network are rebooted/restarted for any reason. That takes a lot less effort and monitoring.
To determine what firmware version you have, log into the modem and look at the Software (firmware) version that is loaded. You can compare that to the list shown here:
If you were on the trials list, you would know it, and if that was the case then the modem would be updated to the latest trial firmware when it became available. That firmware is pushed out to the trial modems.
As @gp-se indicated "unless you have LOTS of devices connected and using the network at the same time, then QOS prioritization of your gaming computer *could* make a difference. "
So, depending on your current router, you could see a difference. That would result from a couple of changes:
1. The method by which the total data que or buffer is handled;
2. The QOS classification of the gaming traffic, where that classification sits in relation to everything else and the allowed data rate limits for each classification.
In the first case, have a look for Fair Queuing Controlled Delay, FQ-Codel. That is a different method to control the processing of the data que which appears to be a better overall solution to que control and data buffering. There are numerous places around the web that discuss FQ-Codel. In the case of Asus routers, specifically Merlin's firmware, , that was implemented in Asuswrt-Merlin 380.67
https://www.snbforums.com/threads/release-asuswrt-merlin-380-67-is-now-available.40191/#post-335866
The current Merlin firmware is 380.68.
https://www.snbforums.com/threads/release-asuswrt-merlin-380-68-is-available.40761/
In the second case, the priority of the various data streams and the min and max data rates can make a considerable difference in the data rate that you see for any one class of data. Here's a rather interesting thread in the SNB Merlin sub-forum that discusses implementation of a script to change the priorities and data rates for the data classes.
Just to bring this up, the question that needs to be answered is whether or not there is any que control in effect when the modem is in Bridge mode, or, does it become a true first in, first out modem where the router has all of the responsibility of que management and QOS duties. When the modem is in Gateway mode, everyone is reliant on the modem for QOS and que management, in Bridge mode, that's a rather interesting question? I'm not assuming anything in this case, and, the only person who can determine that would be @RogersDave. You can do a lot to improve the que management and QOS in a router, but, if the modem is still doing it own thing, that short circuits any efforts one can make to the router's performance. Fwiw, the changes to the CODA firmare V2.0.10.27 shown in Dave'e Realtime Response Under Load - Best Effort (RRUL-be) test show a close resemblance to other plots that I've seen with FQ-Codel running. The plot shown in the link below were done in Gateway mode, and Dave speculated whether or not the results would be the same in Bridge mode, so, this is an interesting question at this point.
@gfadda I'm assuming that you have a white CODA-4582 modem. Please let me know if this is not correct. On the assumption that you do have a CODA-4582, log into the modem and navigate to the BASIC .... GATEWAY FUNCTION tab. Set the Router Mode to IPv4 and save the changes. The modem will revert to IPV4 mode only in about two to three minutes. I usually just reboot the modem, ADMIN .... DEVICE RESET .... Reboot.
Reboot the console as well so that it only has an IPV4 address available.
Restart the game and see if this has resolved the issue.
From what I remember of earlier posts in this thread, server based games are fine with IPV6, Peer to Peer games with IPV6 are not. Microsoft is apparently looking into the problem. So, in the mean time, depending on your choice of games, you may have to switch to IPV4 only.
Would you be interested in becoming a Community Testing Lab member?
-
41160 views
-
83 Likes
-
-
