You will find that UDP, which is the protocol that is used in a good majority of games will run faster with IPV6 enabled. From there, its up to the pc or console in terms of its own UDP performance. That is part of the puzzle when it comes to gaming performance. On top of that, each game is different in its use of IPV6, or not. That is something that the individual user will have to determine.
If you use OpenDNS for Web Filtering, that is an IPV4 service only. IPV6 DNS use will bypass that filtering. Currently you can't specify the IPV6 Domain Name server in the modem. That will hopefully appear in the next trial version for the 4582. The end result currently, is that the modem will use the Rogers IPV6 DNS, bypassing the OpenDNS web filtering. If and when the IPV6 DNS entry is in place in the modem, that will allow you to set that as desired. Even if you do set that for OpenDNS's IPV6 DNS address at that time, it will still bypass the IPV4 Web Filtering. IPV6 web address filtering has been on their to do list for three to four years now and there hasn't been any indication of any progress to date.
So, leaving IPV6 running is really up to the individual user. You shouldn't have any problems with it. If you use any web address filtering service for DNS purposes, then you might want to disable IPV6 until you know that it provides IPV6 filtering.
Twitch issue seems to be gone, I can watch streams and leave it open for hours, and then come back to my desktop and it's not freezed.
I am also streaming for 5hours using upload to twitch.. and no problem at all.
Seems the issue is fully resolved for me!
Update on my ping situation after switching to the CODA modem:
Ping still gets pretty starting around 4pm until 11pm or so. Tonight was really bad. Ping in game was spiking up to 200ms sometimes, one disconnect, and what seemed like an average of around 20-30ms jitter. I was streaming at 5000kbps bitrate on Twitch.tv, which would make my ping with the jitter hover around 70-100ms. Once I turned it off, I was getting 50-60ms when I should be getting around 30-40ms.
I have a few DOCSIS event log that I could post if someone could help make sense of it.
The DOCSIS event logs is shown here
|1||06/12/2017 18:45:29||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|2||06/12/2017 18:45:40||69010200||notice||SW Download INIT - Via Config file bac10400010xx:xx:xx:xx:xx:xx|
|3||06/12/2017 18:46:26||69011200||notice||SW download Successful - Via Config file|
|4||06/12/2017 18:53:25||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|5||06/12/2017 18:53:27||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|6||06/12/2017 18:57:17||84000500||critical||SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|7||06/12/2017 19:04:51||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|8||06/12/2017 19:09:05||84000500||critical||SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|9||06/12/2017 19:09:11||84020200||warning||Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|10||06/12/2017 19:09:21||84000500||critical||SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|15||06/13/2017 09:12:52||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|16||06/14/2017 23:59:52||84020200||warning||Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|17||06/15/2017 15:05:05||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|20||06/16/2017 00:34:01||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx; CM-QOS=1.1;CM-VER=3.1;|
The problems were really bad on the 15th. Note that my modem time is still default GMT so the times are off compared to where I live (EST).
I'm looking online and it seems the warnings (MIMO event) are from modem resets, which I did do (unplug and replug it in) in an attempt to fix the ping issues. The critical timeouts look bad though.
Edit: next time when I'm getting really bad ping, I'm going to save my DOCSIS WAN overviews to post.
Thanks for editing out my MAC addresses RogersZia. Didn't really know if I should have left them in or not.
@Nadernt can you post the DOCSIS WAN signal levels when you can, just to see how they are at the time of posting. They really shouldn't change during the day unless there is something wrong at the CMTS.
Given what you're indicating, I think you might be running into upstream congestion at the CMTS. To see that, have a look at the following post regarding the use of pingplotter to monitor the modem to CMTS path. Running pingplotter for a 24 hour period allows one to see the change in the response times, from the early morning quiet hours to the evening and night congested times.
When you have that plotted after 24 to 48 hours, you can save the data by exporting it to a file so that you can reload the file and look at it later on. I keep a directory with sub-directories for days that I run Pingplotter for test purposes so that I can look at the results, version to version. There is also an EDIT ..... COPY an IMAGE function that you can use to capture the application image to dump that to MS Paint for example and then save the image. You can post that if you would like to do so, so that we can have a look at the result and see if there is a problem from the modem to the CMTS.
Pingplotter can also be used to look at the complete path, looking for problems downstream, however, if the issue is outside of Rogers network, then it would take someone like @RogersDave or @RogersKevin to initiate the required action to resolve the issue. First and foremost though is ensuring that the modem to CMTS path is running as it should, and that takes some data collection to determine that.
Here is the DOCSIS overview, I'll start running pingplotter now and will post the results tomorrow.
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||38595785||ATDMA - 64QAM||36.750||3||3200000|
|2||30596000||ATDMA - 64QAM||34.000||1||6400000|
|3||23700000||ATDMA - 64QAM||33.500||2||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
Ok so I have pingplotter pro running now. Just to clarify, it should be the 2nd hop that I ping, under the IP I use to access the modem? (192.168.0.1)
@Nadernt, yes thats the correct IP to ping. If you have the modem in Gateway mode without a router, the first IP in the list is the modem, the second IP in the list is the CMTS, and that is the target to enter into the pingplotter address bar. Pingplotter will operate in Pro mode for 14 days. In that mode you can view 7 days (?) of target data. So, if you kept pingplotter going for more than 7 days, the most you can see in a single window is 7 days of data, but you can scroll left or right thru weeks of data. If you decide to keep pingplotter you can by the standard licence for $40 US, or the pro licence for $199, or not buy a licence and just use the freebie mode which limits the amount (timespan) of data that you can see with it. The standard licence allows you to keep pingplotter going for days/weeks, but it limits the max amount of data that you can see to 2 days although, as above, you can scroll left or right thru a larger timespan of data.
I still cannot connect to player to player games on NHL17 & FIFA17. I just went to get the CODA router with the .27 firmware but it still does not find any opponents when I search for games? I port forwarded all required ports to have open nat and the recommended ones by EA sports. Please let me know if you can help.
@Jacob10 are you running the 4582 with IPV6 enabled? If so, log into the modem, navigate to the BASIS .... RESIDENTIAL GATEWAY tab, select IPV4 instead of DUAL (Stack IPV4 and IPV6) and save the data. The modem will revert to IPV4 only in about 1 to 2 minutes. You could reboot the modem at that point if you prefer, although it shouldn't be necessary. (ADMIN .... DEVICE RESET .... Reboot)
If this is the case where you had to revert to IPV4 only, please let us know how this turns out on those games.