Hello @bob99991,
Welcome to the Community and thank you for your post!
Lagging can definitely ruin a gaming experience :(. It's strange that this only occurs when the WiFi is turned on. How long have you been noticing this issue? Has it been constant or did it start happening recently? Can you describe where the modem is placed, does it have anything around the unit that could prevent it from ventilating properly?
I have not heard of this specific issue but I will tag in some of our resident experts who may be able to provide some insight @Datalink, @Gdkitty, @gp-se.
We look forward to your response!
RogersZia
@bob99991 I think that the answer might be fairly simple, and it might depend on what’s connected via wifi. What devices are connecting via wifi and is there any chance that one of those devices are running large downloads or uploads?
Assuming that there isn’t anything wrong with the modem, and as you indicated, the problem clears up when the wifi is disabled, that points to an internal modem firmware issue. It would be rather odd for the firmware to reserve a specific amount of bandwidth simply because the wifi is enabled, but, hey, anything is possible. My best guess at the present time is that the modem’s Quality of Service traffic categories are the heart of the problem. Every modem, router, pc, etc, runs some type of QOS traffic order that determines the transit priority of the traffic types, the minimum bandwidth and maximum bandwidth. If for example, a device was connected via wifi and running some type of traffic that had a higher priority and maximum allowable bandwidth than your Ethernet gaming traffic, then its definitely possible that the gaming traffic is queued up, behind the wifi traffic, causing the gaming traffic to lag. The wifi traffic essentially claims most of the total allowable bandwidth, starving every other lower traffic category of bandwidth.
Can you do anything with the modem, nope. If you’re a hard core gamer, you should probably be looking at running the modem in Bridge mode with a router behind it. That router has to have some form of adaptive QOS, allowing you to decide what traffic moves first, and by how much (bandwidth). Examples of this are Netgear’s routers that run the DUMA operating system, allowing the user to adjust the traffic priorities and bandwidth.
There are Asus routers as well, which allows the user load Merlin’s Asuswrt and Fresh JR’s adaptive QOS add-on:
What modem are you currently using? The white Hitron CODA-4582, or one of the Ignite TV XB6 modems, which are the Arris TG3482ER3 or the Technicolour CGM4140. The modem model can be seen on the bottom of the modem.
@bob99991 can you log into the modem, navigate to the STATUS .... DOCSIS WAN tab and copy the Downstream Overview table, all the way to the bottom right hand corner of the table. Paste that into a post so that we can have a look at the signal levels. The table will copy and paste like any other document.
Ignore the data that resides above the Downstream overview. That is specific to the modem and shouldn't be posted in an open forum.
@bob99991 those levels aren't bad at all. A couple things to note, you have 4 upstream channels running instead of three. That's a good thing as your upstream performance should be better with 4 channels running. The upstream signal levels are higher than I would expect with this modem. Normally they're in the 30 to 32/33 dBmV range, so, for some reason, there is enough signal loss on the upstream side that the Cable Modem Termination System (CMTS) is commanding the modem to run at a slightly higher power level, which is still within spec.
The modem is running DOCSIS 3.1 on the downstream side, so, the downstream DOCSIS 3.0 levels are a moot point. Unfortunately there isn't enough detail in the data to determine the health of the DOCSIS 3.1 channel which is running in the 275 to 467 Mhz range.
Call tech support and ask the Customer Service Rep to run a signal check on the modem. Ask specifically what the signal levels and signal to noise ratios are for the upstream levels when they arrive at the neighbourhood node. Those levels aren't reported back to the modem, so that requires the end user to ask tech support about those levels. The question of the day is whether or not those upstream levels are in spec when they arrive at the neighbourhood node?
Fwiw, you're not the first customer to comment on slow uploads with 4 upstream channels running. That would cause the lag that your seeing. I'm almost at the point of thinking that there's an issue afoot when the a modem runs 4 channels upstream.
I will call tech support.
I did some reading and saw that viewing a pingplot is helpful. Not sure if I did this right, but I added 10.0.1.1, 99.229.50.1 and google.ca.
Please see below.
Thats the next step, running a pingplot. Your plots are a little interesting. Can you describe how your network is configured? I'm trying to figure out why you show both 10.0.1.1 and 192.168.0.1 in those plots. I would expect one or the other but not both.
Assuming that the plot with 192.168.0.1 is with the modem running in Gateway mode, ping the next hop only, 99.247.142.1 In this specific case, I'm looking for packet loss. Ignore the large latency spikes that you will see. That's due to the fact that the CODA-4582 modem and any ping application don't play well together, so you can ping the second hop (the CMTS) for the purpose of latency testing. It will work for packet loss however.
In the upper right hand corner, adjust the ping time to 1 second. Keep the Focus on Auto. Right click on the column title bar and select MAX and ERR for display. Drag those two columns to the right to sit beside the MIN column. As you go up in time, for the plot display, you get to a point where there is more than one data point per horizontal pixel. At that point Pingplotter averages the data in stead of maintaining the max and min points at any horizontal pixel point. The MAX text data, with the Focus on Auto will show the MAX latency for the plotted time span regardless of the plot averaging that is taking place. The ERR count, with the Focus on Auto will show the number of individual instances of packet loss in the plotted time span.
Ok, so, first step is to run that ping to the CMTS looking for packet loss. Let that run for several hours, unless you see that there is a considerable amount of packet loss on the plot. At that point its time to call tech support and ask the CSR to run a ping to the modem from the CMTS, or run a ping to the CMTS from the modem. Keep pingplotter running. When you see packet loss on the plot, the CSR should show packet loss as well. You can also overwrite the ping interval and put a lower interval in, such as 0.1, 0.05, seconds, etc, etc. The min time would be around 0.015 seconds due to the actual response time from the CMTS. As you go lower in time, you will see regular ping spikes occur. Thats only from the CMTS and is due to a firmware change that occurred in version 2.0.10.27, way back when. Were now up to 2.0.36.T Don't be afraid to experiment with the ping interval time. Just be aware, as you drop the ping interval time down, you will see more data points per horizontal pixel. It will get to a point where running the plot on the lowest setting of 60 seconds won't prevent plot averaging.
Ok, beyond that, you can run a ping test to the Rogers DNS, looking for any latency issues. Set the ping interval for 1 second and ping:
Primary IPV4 DNS: 64.71.255.204
Secondary IPV4 DNS: 64.71.255.198
Primary IPv6 DNS: 2607:f798:18:10:0:640:7125:5204
Secondary IPv6 DNS: 2607:f798:18:10:0:640:7125:5198
Running a test to the DNS keeps the test within the Rogers network and avoids any issues due to border crossing and running in other ISP networks. Prove that the latency is ok, within the network before testing beyond Rogers border.
Fwiw, when I run a ping test for latency purposes, I run it for 24 hours using Wireshark to collect and plot the data. Using Wireshark avoids the plot averaging that you see in Pingplotter.
Give that a shot and lets see what turns up.
Can you log into the modem and check the Software (firmware) version as indicated on the STATUS page. That page is displayed automatically when you log into the modem.
Datalink,
Modem software: 2.0.10.36T6
I took two images of the Pingplot during the worst of the lagging last night. The two were for 99.247.142.1 and the second was for the Primary DNS 64.71.255.204.
@bob99991 it looks like you have a problem with the external cable and / or connectors. You shouldn't have any packet loss to the CMTS, practically speaking. Typically that loss should be under 0.1 %. So, from looking at the first plot, I'd say that you need the services of a tech to inspect the cable and replace the connectors. I'm assuming here that you don't have any packet loss to the modem. If you ran a ping test to the modem, you shouldn't have any packet loss.
If you were to run a command line ping test to the CMTS, that will confirm what your pingplot is indicating. That's a simple command with a command prompt:
ping 99.247.142.1
That will run a single target ping, versus what pingplotter does, which is to ping every hop in the path to the end target. If there is any question about packet loss, a command line ping test will confirm or deny the existence of any packet loss. I'd let that run for an hour or so, and then look at the final results. If there is packet loss occurring, you will see that as the results scroll by. As I indicated before, ask tech support to ping the modem from the CMTS or ping the CMTS from the modem. When you see packet loss occur, the Customer Service Rep should see that as well. There shouldn't be any argument about packet loss at that point.
On the other hand, call tech support and advise the CSR that you have packet loss occurring between the modem and the CMTS. No doubt the CSR will probably run a signal check on the modem, but, that probably won't show anything useful as the packet loss is a momentary disconnection that occurs too fast for the modem to record the data. So, tech support should have first crack at this. Beyond that, if you're not getting anywhere, then @RogersAndy can weigh in on the matter.
Fwiw, here's a gaming thread that Andy is running, which is to address situations such as what you're facing.
https://communityforums.rogers.com/t5/Internet/Rogers-Gaming-amp-Streaming-Lab/m-p/440211#M56121
If you want to run a high speed ping test, download HRPing from: https://www.cfos.de/en/ping/ping.htm
Thats a command line program. To run a continuous pingtest at 200 milli-second intervals, use the following command:
hrping -t -T -s 200 99.247.142.1
Use Ctrl + C to bail out of the test. The -s variable is in milli-seconds. The default is 500 ms.
To dump the results to a file, run: hrping -t -T -s 200 -F pingtest.txt 99.247.142.1
That will create and write to the pingtest.txt file in the same directory as the HRPing executable, although you can point that to any directory and use any file title that you prefer. Use filename.txt, with the .txt file extension so that it can be opened automatically with notepad. Large 24 hour file results should be opened with Notepad++, which easily handles large file sizes. The time intervals can be adjusted up or down. Given the typical result due to the modem internal timing, the lowest that you can use will be the average on any given run plus perhaps 1 ms. That "previous average plus 1 ms" will allow you to run the lowest possible ping interval for test purposes.
For now, we'll leave the packet loss to the DNS alone, but, it won't help when it comes to web page loading. First step is to resolve the local packet loss and go from there.
Edit: Is your external cable underground, or does it arrive via overhead path from a nearby utility pole? Its much easier for the tech to replace the connectors at both ends of the cable from the house to the local tap if it runs underground. Any guesses as to whether or not that external cable has been in use for a few years?
Issues with xbox and ps4 can have an effect if you dont have port forwarding set up (that the firewall is too strict)
That being said.. your signal could be effecting it some as well.
Optimal signal is between + / - 10dBmV.
Your hitting -6 to -8 in a lot of channels.
You would be best to get rogers to send someone out to take a look at the signals.
Optimally you want it to be as close to 0 as possible.
-
7537 views
-
3 Likes
-
-
