Can you log into the modem and check the WAN Address on the STATUS page. That page is shown when you log into the modem. At the upper right hand corner, in the WAN Address data field, there should be two IP addresses, one IPV4, as in 192.168.0.1 for example, and one much longer ugly looking IPV6 address, as in: 2001:0db8:85a3:0000:0000:8a2e:0370:7334.
Assuming that you see both addresses, your pc and xbox should have an IPV6 address as well. I would reboot both. After the reboot, if you run an ipconfig command on the pc at a command prompt, you should see an IPV6 address at the top of the data fields. If so, your pc is using an IPV6 address as a primary address. If you run a test at ipv6-test.com, and see the failure due to filtering IPV6 ICMP, that indicates that your Windows firewall and perhaps antivirus firewall as well require exemptions to allow IPV6 ICMP. After you have entered that exemption, reboot the pc, and run the ipv6-test.com test again. Just to note, I've seen flaky results from that site, so, refresh the page a few times, looking for consistent results, test to test. That will give you some confidence that the results are accurate.
For the xbox, does the IPV6 address show up in the IP address field, so that you know that the xbox has picked up an IPV6 address?
With the addition of IPV6 recently, that gives the Xbox one additional path for matchmaking and gaming. The XBox will decide for itself which path to use, IPV6, IPV4 or Toredo. I don't believe there is any indication as to which path it has decided to use. So, that could mean that you could have a restricted NAT, as in IPV4 NAT, but, with IPV6 up and running the Xbox is perfectly content to use it. One thing to note, there is no crossover of IPV4 to IPV6 players. You're either in an IPV4 world or IPV6 world.
- last edited on by
RogersMaude
Thank you very much for the reply.
About IPv6 Test: Turned off Windows Firewall and that did the trick (thought I disabled it earlier when I got bitdefender)
For the xbox, does the IPV6 address show up in the IP address field, so that you know that the xbox has picked up an IPV6 address?
No, it shows the IP address '192.168.0.12'. The same IP address it used to set up Teredo as a port forward rule in my modem automatically.
I take it this means that I have to set up a Static IP with my IPv6 IP as my IP address? The problem is that I don't know which one to use. My WAN setting IP is different than the multiple ones I got in IPconfig.
Thanks
@jallan44, is this an XBox 360 or XBox One? The Xbox 360 does not support IPV6, the Xbox One does.
Please ensure that the bitdefender firewall is up and running. It wasn't my intention for you to disable the Windows firewall, but to add the necessary IPV6 ICMP exemption to allow Windows full access to IPV6. Just want to make sure that your pc is firewalled.....
@JohnBeaudin wrote:
I am on .25 as well, I was hoping for a latency improvement especially for online gaming, but it's similar to previous firmware version.
The latency has greatly improved but only for ICMP. No change for ICMPv6 and more importantly for TCP. I believe there is a little improvement in UDP but I need to perform further testing.
Unfortunately, there are other issues with this firmware. Nevertheless, I am still working with Hitron on getting further improvements.
Dave
@Slipstream1982, your signal levels are fine, as are the signal to noise ratios. The spiked ping responses, which are due to the way that data is processed by the Puma 6 chipset probably look something like this:
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3697iE19F43892310542F
Or like the other first two to three rows of images in my image library:
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158
Those images are from ping tests, from my CGNM-3552 to the Casa CMTS to which the modem is connected. So, thats not pinging an end target somewhere, just the network entry point. Note that this isn't a Hitron modem issue, its a Puma 6/6MG chipset issue. Those chipsets are used by a few modem manufacturing companies and as a result, by numerous ISPs.
@RogersDave is currently addressing this issue, along with numerous other Rogers staff. He is currently awaiting further updates from Hitron regarding required changes to the next trial version 4.5.8.25.
Fwiw, Rogers is well ahead of any other modem company or ISP on this issue. Most of the others are still in the "nothing wrong with our equipment" stage. Hopefully you will see further news regarding 4.5.8.25 fairly soon.
Have a look at message #142 above from @RogersDave.
Its also possible that three days ago your CMTS was switched from a Cisco CMTS to a Casa CMTS, going from 20 channels to 32. This problem gets worse as the channel count goes up. So, its just coincidence that you bought a new router at the same time. Possibly you were't paying close attention to those return times before, and now you are. It won't matter whether you run the modem in Gateway mode or in Bridge mode with a router, the results will be the same.
With the modem in Bridge mode, run a trace to anywhere, it won't matter where. The first IP in the trace will be the router. The next IP will be the CMTS. Ping that CMTS address. Run 100 pings, 1000 pings, your choice. You will see ping spikes during that test if you sit and watch the ping return times scroll by. The high ping times will be random, in terms of the ping time themselves, and the time between the ping spikes.
Thats due to the modem, and that is what Rogers is working on, with Hitron and Intel.
I suspect that its pure coincidence, or perhaps you may not have noticed previously. I don't believe that any telecommunications company anywhere has the resources to switch major components across the network all In one day. There has to be several hundred if not several thousand CMTS's across Rogers cable system, and beyond the simple physical installation, there would be post install configuration changes required to go from a Cisco CMTS to a Casa Systems CMTS. That would slow the process down. I doubt that its a plug and play routine to switch out a neighborhood CMTS. In any event, you've missed most of the fun with the high ping situation and Rogers is making good progress on this. Keep your eyes open for further news on this.
And yes, you will see ping spikes when you ping the CMTS and when you ping the modem using the default Gateway address when the modem is in Gateway mode. Pinging 192.168.100.1 is the web server, which is close in terms of results but not exactly the same as pinging the Default gateway address.
-
602600 views
-
669 Likes
-
-
