Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Reply
Armega
I Plan to Stick Around

‎01-07-2015 10:17 PM - last edited on ‎03-25-2015 11:22 AM by Retired Moderator RogersJermaine

Posts: 13

Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Hi,

 

I just signed up with rogers internet last week, I was on a very low plan with bell prior to that. World of warcraft was always running with about 20-30ms, and very low pings with programs such as ventrilo.

 

However after I switched to rogers fibe 60 and the Cgn3 i began encoutering high latency issues. My internet videos and webpages download extremely fast. I have tried Wired and Wireless on multiple computers.

 

I went on to the Techxpert and they couldnt find any problems on their end, they did the port forwarding for me and the DMZ with no results. Anyways I followed many of the suggestions on the forums here to try and resolve my issues. The latest one being I got a 3rd party router, the Asus RT-AC87U, a 300$+ Router to try and fix my problem, even after bridging my Cgn3, which a techXpert confirmed was in bridge mode, and had my Asus Router connected, I noticed no change and still have very high latency.


I really don't know what else to do, like I said I had a really low bell service prior but it ran WOW and my other services great. I just don't get it. I've spent hours in the evening tallking to techXperts to no avail.

 

Any other assistance would be Greatly appreciated.

 

 

***edited labels***

Labels:
Message 1 of 30
1,462 Views
Report Content
Reply
0 Likes
Datalink
Resident Expert
Resident Expert

‎01-07-2015 11:10 PM - edited ‎01-07-2015 11:10 PM

Posts: 6,297

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Check your mail.  I sent a homework list in response to your previous message. 🙂



Message 2 of 30
1,438 Views
Report Content
Reply
0 Likes
Armega
I Plan to Stick Around

‎01-08-2015 12:31 AM

Posts: 13

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Ok so to answer the first few questions.

 

(1) It is an amber light on the back of my Cgn3 and computer, the connection i play with is wired,

 

(2) The hardware acceleration you told me of under the Lan, switch control. The two options under it are "enable jumbo frame" which is disabled, and "Nat Acceleration" which is set to Level 2 CTF.

 

 

Next, the version for the Cng3 is 4.2.4.5.

 

Here is the wired router ping results. Don't know if I did correctly I don't know much.

 

C:\Users\Ty>pathping 192.168.0.1 100

Tracing route to 0.0.0.100 over a maximum of 30 hops

  0  No resources.

C:\Users\Ty>ping -n 100 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 21ms, Average = 5ms

C:\Users\Ty>pathping -h 100 192.168.2.1

Tracing route to 192.168.2.1 over a maximum of 100 hops

  0  Ty [192.168.0.10]
  1  192.168.0.1
  2     *        *        *
Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Ty [192.168.0.10]
                                0/ 100 =  0%   |
  1    5ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1

Trace complete.

C:\Users\Ty>

 

 

 

I am on the rogers Hybrid Fibre 60 plan, I see download speeds of 85ish, and uploads around 11 for wired. Wireless is around 30 mbps, but thats because the laptop that i used for that test isn't able to pick up the 5ghz network.

 

Those values were consistant on the three sites you gave me.

 

 

Here are the down and upsteam tables.

 

Downstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Signal noise ratio (dB) Channel ID 1 597000000 256QAM 0.400 40.366 2 2 591000000 256QAM 0.600 40.366 1 3 603000000 256QAM 0.700 40.366 3 4 609000000 256QAM 0.300 40.366 4 5 615000000 256QAM -0.200 38.983 5 6 621000000 256QAM -0.500 38.605 6 7 633000000 256QAM -0.500 38.983 7 8 639000000 256QAM -0.900 38.983 8 9 645000000 256QAM -0.800 38.983 9 10 651000000 256QAM -0.900 38.983 10 11 657000000 256QAM -1.100 38.605 11 12 663000000 256QAM -0.900 38.983 12 13 669000000 256QAM -0.700 38.605 133 14 675000000 256QAM -1.100 38.983 134 15 681000000 256QAM 0.000 38.983 135 16 687000000 256QAM 0.000 38.605 136 17 693000000 256QAM -0.500 38.983 137 18 699000000 256QAM -0.900 38.983 138 19 705000000 256QAM -0.600 38.983 139 20 711000000 256QAM -0.800 38.983 140

Upstream Overview Port ID Frequency (MHz) BandWidth Modulation Type Signal Strength (dBmV) Channel ID 1 30596000 6400000 ATDMA 41.000 2 2 23700000 6400000 ATDMA 41.250 3 3 38596000 3200000 ATDMA 41.250 1

 

 

 

The trace and ping results are here:

 


 

C:\Users\Ty>tracert 12.168.209.68

Tracing route to 12.168.209.68 over a maximum of 30 hops

  1    20 ms     8 ms     2 ms  192.168.0.1
  2    11 ms    11 ms    12 ms  7.11.164.13
  3    15 ms    19 ms    16 ms  69.63.254.53
  4    18 ms    17 ms    15 ms  69.63.251.50
  5    29 ms    29 ms    28 ms  209.148.224.254
  6    30 ms    59 ms    88 ms  ae53.edge1.Toronto2.Level3.net [4.31.208.129]
  7    32 ms    49 ms    39 ms  ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]

  8    36 ms    39 ms    40 ms  ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]

  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Ty>

 

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Ty>pathping 12.168.209.68

Tracing route to 12.168.209.68 over a maximum of 30 hops

  0  Ty [192.168.0.10]
  1  192.168.0.1
  2  7.11.164.13
  3  69.63.254.53
  4  69.63.251.50
  5  209.148.224.254
  6  ae53.edge1.Toronto2.Level3.net [4.31.208.129]
  7  ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]
  8  ae-2-70.edge3.NewYork1.Level3.net [4.69.155.81]
  9     *        *        *
Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Ty [192.168.0.10]
                                0/ 100 =  0%   |
  1    7ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2  ---     100/ 100 =100%   100/ 100 =100%  7.11.164.13
                                0/ 100 =  0%   |
  3   24ms     0/ 100 =  0%     0/ 100 =  0%  69.63.254.53
                                0/ 100 =  0%   |
  4  ---     100/ 100 =100%   100/ 100 =100%  69.63.251.50
                                0/ 100 =  0%   |
  5  ---     100/ 100 =100%   100/ 100 =100%  209.148.224.254
                                0/ 100 =  0%   |
  6   45ms     0/ 100 =  0%     0/ 100 =  0%  ae53.edge1.Toronto2.Level3.net [4.
31.208.129]
                              100/ 100 =100%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  ae-2-70.edge3.NewYork1.Level3.net
[4.69.155.81]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  ae-2-70.edge3.NewYork1.Level3.net
[4.69.155.81]

Trace complete.

C:\Users\Ty>

 

 

and my Ethernet card is a Realtek Pci E, GBE Family Card.

 

 

 

 

Message 3 of 30
1,425 Views
Report Content
Reply
0 Likes
Highlighted
VivienM
I'm an Advisor

‎01-08-2015 07:32 AM

Posts: 928

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

@Armega wrote:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

 

 

Sorry to distract from the problem at hand, but why are you running the original version of Windows 8? Windows 8.1 (6.3.9600) is a free upgrade and probably has fewer bugs...

 

As for the problem at hand, those ping numbers to the default gateway are extremely troubling. In those numbers, is 192.168.0.1 the CGN3, or is it your expensive Asus router?

Message 4 of 30
1,388 Views
Report Content
Reply
0 Likes
jimboden
I'm an Advisor

‎01-08-2015 09:15 AM

Posts: 1,524

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

My ASUS RT-AC68U router's IP address is 192.168.1.1. Not sure why it's different from the OP's. I also have a CGN3 bridged to my ASUS. When I ping my router, I always get <1ms according to the router itself. When I ping using the Windows Command Prompt, results are usually .2-.3ms.

Message 5 of 30
1,359 Views
Report Content
Reply
0 Likes
Gdkitty
Resident Expert
Resident Expert

‎01-08-2015 09:59 AM

Posts: 14,033

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Assuming the CGN3 is properly bridged... and that the 192.168.0.1 IS the ASUS, and not the CGN3..
(one quick way to test.. would be to in a web browser.. go to 192.168.0.1 and see what web page comes up)

 

Than i would likely think a LINE/WIRE problem, between the PC and the router, or the PC/CARD itself.

 

NORMALLY when we see the ping jumps like that, its from it going to the CGN3, NOT bridged.

 

 



Message 6 of 30
1,349 Views
Report Content
Reply
0 Likes
jimboden
I'm an Advisor

‎01-08-2015 10:29 AM - edited ‎01-08-2015 10:40 AM

Posts: 1,524

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Had briefly forgotten, but the CGN3's IP address is 192.168.0.1 when it's not bridged. I assume that did not change with the recent firmware update. Going back and reading the thread from the beginning, it seems to me the router is not set up properly. The OP should not be able to see IP address 192.168.0.1 if the CGN3 is bridged properly.

Message 7 of 30
1,340 Views
Report Content
Reply
0 Likes
Armega
I Plan to Stick Around

‎01-08-2015 10:37 AM

Posts: 13

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Right now it's just my computer to the cgn3 , all those tests were done connected to it as datalink asked me. Now as for the computer card itself I don't know as I tried another computer and got the same results pinging and trace.

When I had my Asus connected prior to the cgn3 and had the Cgn in bridge mode I noticed zero difference in world of Warcraft and other internet programs.

I also got new cat 6 cables when I picked up the router and used it. And I followed Rogers instructions on how to set it to bridge and had a techxpert confirm it was in bridge mode when I had it hooked up.
Message 8 of 30
1,328 Views
Report Content
Reply
0 Likes
Armega
I Plan to Stick Around

‎01-08-2015 10:45 AM - edited ‎01-08-2015 10:46 AM

Posts: 13

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

The reason I can see the Cgn3 Ip is because I factory reset a day after I no difference with the router hooked up. I guess when I get home from work I should set it all back up with the router and ping and trace?

The reason I did that is because Data asked me for information from my Cgn3 page and I couldn't connect to it with the router hooked up.
Message 9 of 30
1,321 Views
Report Content
Reply
0 Likes
jimboden
I'm an Advisor

‎01-08-2015 10:47 AM - edited ‎01-08-2015 10:56 AM

Posts: 1,524

Re: Help Please, Just got Fibe 60 with Cgn3, Having terrible latency issues with online games.

Armega:

 

The poor ping times with the CGN3 are well documented on these forums. My ASUS router gets ping times <1ms every time, no exceptions. You can use your router for ping times, trace routes, etc. when the CGN3 is bridged to it. Go to Network Tools and have a look after it's connected again. Trust me, you will really like the ASUS and it should take care of the ping issues you see on the CGN3.

 

EDIT: We were both composing messages at the same time. Yes, you cannot connect to the CGN3 when it's in bridge mode. The latest firmware update caused that problem. Before it, I could sign into the CGN3 in bridge mode. Why Rogers changed it is beyond me, but we've lost an important feature and no one wants to do a factory reset just to look at signal strength readings or see the latest firmware release. I'm hoping some gurus on different forums will come up with a solution.

 

I just pinged my ASUS router and here are the results:

 

PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=0.285 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=0.169 ms
64 bytes from 192.168.1.1: seq=2 ttl=64 time=0.155 ms
64 bytes from 192.168.1.1: seq=3 ttl=64 time=0.146 ms
64 bytes from 192.168.1.1: seq=4 ttl=64 time=0.127 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.127/0.176/0.285 ms

Message 10 of 30
1,313 Views
Report Content
Reply
0 Likes
Topic Stats
  • 29 replies
  • ‎01-07-2015 10:17 PM
  • 1463 views
  • 0 Likes
  • 5 in conversation