At this point, if you look carefully at the WinMRT ping times, you can see that the average and worst case ping times have doubled from this morning, in some cases tripled. Keep tracking the WinMRT results please.
At some point can you run a ping test to google and post those results: ping www.google.com -n 20
1. Are you running an ethernet or wifi connected device?
2. Can you log into the modem, navigate to the STATUS.... DOCSIS WAN page, copy the downstream and upstream tables and
paste them into the thread.
3. Can you run a wired speedtest at http://speedcheck.rogers.com/en.html and www.speedtest.net using the Toronto Telus server
and post the results.
4. What internet plan are you on, 100/10 or 250/20?
5. Are you located in a house or apartment, condo, highrise, etc, etc.
6. By now that modem should be running firmware version 4.5.8.16. While you are logged into the modem, can you check the
Status page and confirm that.
Your downstream levels are high, but given the fact that you're in an apartment that doesn't surprise me. The upstream levels are ok where they currently are. The downstream levels shouldn't cause huge issues at the levels that they are currently at but I'd be happier to see them closer to 0 dBmV. I would suspect that your modem is connected to a Multiple Dwelling Unit (MDU) which resides in a utility room in the basement of the apartment. I wonder how much of this ia a network issue, with the delays that are seen on the tracert, and how much might be attributed to the MDU. When an MDU issue comes up, it can be difficult and time comsuming to rectify. Can you run a trace to google.ca and post the results, just to see how it turns out versus your previous trace. Do the trace times ever drop down to a reasonable 20 to 40 ms across the board?
For the purposes of the discussion, the MDU or node can be considered as one in the same, depending of course on how large your apartment building is, and there is the chance that you are connected to a neighborhood node instead of an MDU. What I wanted to see with a trace to google was whether or not the same high trace times would be exhibited throughout the path. I wasn't looking specifically for a trace return from google itself. Looking at the trace to Rogers.ca, none of the hundred ms plus times are seen, as they were in the original post. The issue of high ping and trace times has come up again in various discussions and unfortunately I don't have an answer for that. Personal opinion its beyond a tech issue and into network capacity issues. How to get someone to examine the issue of routing times through Rogers system and peering with other companies seems to be a mystery. What we need on this board is a contact point with the Network Operations Center, someone who could look at the loading of those servers and do something about the routing or initiate some action to see those times improved. At this point would send a pm to @CommunityHelps looking for assistance. Not trying to pass the buck, but I think this is above anything I or the mods can do, but the mods can contact the staff who can look into issues such as this.
- last edited on by
RogersMoin
To request the firmware update to version 4.5.8.16, follow this link @CommunityHelps to navigate to the CommunityHelps page when you are signed into the forum. On the right hand side of the page is a link titled "Send this user a private message". Use that link to navigate to the next message composition page, fill in the title, and your modem MAC address and Cable Account Reference Number in the text area. The Cable account reference number is located at the top of the Internet section of your bill. The account number that you normally see or use is comprised of various home services such as Internet, Home Phone, Home Monitoring, etc, but the requested reference number is within the Internet section of your monthly account statement.
The modem MAC address can be found on the sticker at the back of the modem, or in the HFC MACC Address located in the Status page of the modem when you are logged into the modem.
So, send in the info with a brief explanation that the modem has not been updated. Hopefully you will see the update late tonight.
If you have port forwarding set, you should have set up a static IP address first using the DHCP reservation function. If I remember this correctly, its in the BASIC.... LAN setup page. Once that is set, you would then reboot the modem, login again and set the port forwarding to that specific IP address.
Alternatively, you can kill the port forwarding rules. set UPNP to enabled, reboot the modem and then start the game. With UPNP set, the modem should set the port forwarding rules as required for the game. Note that the modem only holds 9 port forwarding rules, so, if you have previously set rules, that might become an issue if the total is more than 9 rules. I don't know if the first rules are turfed, or if the last entered rules are denied if the rule list is full and you attempt to enter additional rules.
Note that either the UPNP is disabled with the static IP and port forwarding rules set manually or, there is no static IP address and port forwarding rules and the UPNP is enabled to handle port forwarding as required.
I also should have asked, connected via ethernet or wifi?
Trying to remember.. are you using it BRIDGED or in gateway mode?
Either way.. WITH the new firmware patch on the ACSMR, it SHOULD have lower ping times (at least TO the modem)
Nope, the CGN3 is still on an older firmware.
the ping times between a device and the CGN3 have some minor spikes.. which the newer firmware on the CGN3ACSMR has fixed.
My guess would be loading issues with the neighborhood node, which your modem is connected to. But, there may be other possibilities.
1. Are you running wired or wifi connections for gaming?
2. Are you using the modem only, or running the modem in Bridge mode with a third party router behind it?
3. Can you log into the modem, navigate to the STATUS... DOCSIS WAN page, copy the Downstream and Upstream tables and paste them into the thread.
4. Can you run a speed test using http://speedcheck.rogers.com/en.html and www.speedtest.net using the Toronto Telus server and post the results.
As for gaming with distant servers, yep, that will be a problem depending on where the server is located. That really depends on the peering agreements that Rogers has with other companies, and that unfortunately is a black hole as no one on the Rogers staff has to this point explained what agreements are in place and how users are able to benefit from those agreements, or suffer from the lack of agreements with downstream companies.
-
41506 views
-
159 Likes
-
-
