When you consider that Comcast has been running IPV6 for a while now, its surprising that the client doesn't support IPV6. I would think that a number of people with Comcast must play LOL. The strange thing about the indication that IPV6 isn't supported is that its not mentioned on the main support page.
Ah. Alot of comcast are experiencing connection issues with the old client. It's 5 years old though Riot has the money and time, they don't have the time to atleast make the old client support IPv6? That should've been done a year ago....
I play a game called league of legends and usually i get constant 29 ping, but as of yesterday it has increased to 42 I asked others who had rogers if their ping had increased and they all said yes. How long is it going to take to get fixed?
Having the same problem had 25-30 ping 3 days ago, yesterday it was mid 50's and today its mid 40's
increase in latency doesn't necessary mean it is a Rogers problem. Do a traceroute as suggested by gdkitty and I think it would give everyone a clear understanding where the increase in latency time is. If it is in a router/hop beyond Roger's control, then there is not much Rogers can do.
It has already been just over 72 hours. Will send. However, regarding the IPv6 issue, I am on a macbook pro, will it be difficult to disbale it?
Did you receive the firmware yet? If not, I suggest you send a PM to @CommunityHelps with your account number, and MAC number of the modem and ask them to manually push the latest firmware to your cable modem.
the .16 firmware addresses the league of legend issues, I am sure of it.
Here is a tracert from the other day. Not at home so I cant get one for right now. Looks like hop 7 is the problem
Tracing route to INTEL_CE_LINUX [188.8.131.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 11 ms 15 ms 10 ms INTEL_CE_LINUX [184.108.40.206]
3 20 ms 14 ms 14 ms INTEL_CE_LINUX [220.127.116.11]
4 26 ms 32 ms 16 ms INTEL_CE_LINUX [18.104.22.168]
5 14 ms 30 ms 173 ms INTEL_CE_LINUX [22.214.171.124]
6 28 ms 22 ms 17 ms van58-9-230-230.dynamic.rogerstelecom.net [126.96.36.199]
7 113 ms 103 ms 56 ms van58-9-230-138.dynamic.rogerstelecom.net [188.8.131.52]
8 58 ms 57 ms 52 ms eqix-ch2.chi01.riotdirect.net [184.108.40.206]
9 65 ms 56 ms 51 ms INTEL_CE_LINUX [220.127.116.11]
10 53 ms 56 ms 53 ms INTEL_CE_LINUX [18.104.22.168]
11 57 ms INTEL_CE_LINUX [22.214.171.124]