CODA-4582 - Open Issues for Investigation

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
Showing results for 
Search instead for 
Did you mean: 
Reply
I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation

Alternately, just try nping (part of nmap) in echo mode. Setup a server somewhere and flood UDP pings and see how much loss you get.

https://nmap.org/book/nping-man-echo-mode.html
I'm a Reliable Contributor
Posts: 577

Re: CODA-4582 - Open Issues for Investigation

I will make the switch back to the CODA-4582 sometime this week. I will be playing a couple games of LOL and will use the raw network logs and translate it into a graph which shows the packets lost/min.

I will also be running the test with less than 10 devices connected to the modem, and 10+ devices connected to it. This test should be run on firmware .26 in order to verify if the reboot fix actually worked. There's limited feedback on .26, so hopefully there's more feedback in the next few days.

I'm a Reliable Contributor
Posts: 603

Re: CODA-4582 - Open Issues for Investigation

@RyzenFX

 

Thanks for your contribution to the community.

I Plan to Stick Around
Posts: 205

Re: CODA-4582 - Open Issues for Investigation


@Telek wrote:
Alternately, just try nping (part of nmap) in echo mode. Setup a server somewhere and flood UDP pings and see how much loss you get.

https://nmap.org/book/nping-man-echo-mode.html

 its not just lost packets its out of order packets.  iperf might be more suitable as it will verify if the data recieved is the same as sent and if the order is correct. 

 

Highlighted
I Plan to Stick Around
Posts: 26

Re: CODA-4582 - Open Issues for Investigation


@Telek wrote:

@Datalink wrote:

After looking at a League of Legends data capture and from running UDP ping tests to pingplotter.com, I'm not convinced that the UDP problems are all attributable to the modem.  I think the data path from the start point to the end point might be playing a big part in the UDP problems, but, that's for Dave to confirm or deny. 


All attributable? No. But as others have mentioned the AC modem didn't have nearly the same level of the problem as the CODA one does.


  That. Since switching to 3552 kids have not any packet loss or ping problems with any of the games. Only  thing that  changed was the modem. 

I Plan to Stick Around
Posts: 11

Re: CODA-4582 - Open Issues for Investigation

I need to disable IPv6 on my CODA-4582 Modem. Unforutnately Rogers IPv6 causes connection issues with some EA games on the Xbox One. The most recent is Mass Effect Andromeda that makes it impossible to play multiplayer with Rogers Internet. NHL 17 also has this issue but only in head-to-head games. 

 

I have tested this enought to confirm 100% it is a Rogers Internet issue. The issue is gone when using an IPv4 only connection. Is there anyway to disable IPv6 on my modem?

I'm a Regular
Posts: 304

Re: CODA-4582 - Open Issues for Investigation

Noticed some slowness in recent days and also some random time-outs when attempting to load certain sites. Started running ping plotter over the last few days and notice a lot of packet loss at multiple hops when testing IPv6 (using Google). The problem is consistent, meaning the packet loss is always there every time I test. There are zero issues with IPv4 (no packet loss and consistently low pings). Not sure if this problem manifested itself in firmware .26. I'm running CODA in bridge mode with Asus RT-AC68U. IPv6 is configured correctly on the Asus. Anyone else having issues with packet loss using IPv6?
I Plan to Stick Around
Posts: 205

Re: CODA-4582 - Open Issues for Investigation


@J04DAN1 wrote:

I need to disable IPv6 on my CODA-4582 Modem. Unforutnately Rogers IPv6 causes connection issues with some EA games on the Xbox One. The most recent is Mass Effect Andromeda that makes it impossible to play multiplayer with Rogers Internet. NHL 17 also has this issue but only in head-to-head games. 

 

I have tested this enought to confirm 100% it is a Rogers Internet issue. The issue is gone when using an IPv4 only connection. Is there anyway to disable IPv6 on my modem?


I'm over 24h of game play into the new Mass ffect on Xbox One with IPV6 enabed and have not experienced the same issues.  Something else must be afoot for you. 

I Plan to Stick Around
Posts: 18

Re: CODA-4582 - Open Issues for Investigation

I just bit the bullet and bought a router from Best Buy. Now I'm solely on IPv4 I couldn't play P2P games. All server based games worked fine though before.
I Plan to Stick Around
Posts: 11

Re: CODA-4582 - Open Issues for Investigation

Unfortunately no it is a Rogers issue. I have tested this many ways. It also only impacts Mass Effects MULTIPLAYER. Steps I have done to confirm the issue is with Rogers. 

 

1. NAT is Open on Xbox One with a static IP address assigned and all the ports suggested by Microsoft and EA for Andromeda correctly routed to Xbox One 

 

2. Every other multiplayer game works perfectly including recent releases like For Honor, Battlefied 1, Madden 17, Destiny, Ghost Recon Wildlands, Rainbow Six Seige. 

 

3. The issue is not present if I use my cell phone as a mobile hotspot and connect to Xbox Live. The phone is giving an IPv6 address as well but whatever routing issue is present with Rogers Cable Internet is not present on their mobile network. 

 

4. I have used two separate modems the older CGN and now the new CODA modem and both had the same issue. 

 

5. The issue is not present when I took my Xbox to a family members house whose Rogers modem was running an older firmware that was only providing IPv4 addresses. When only connected to IPv4 the issue again was fixed. 

 

6. I have factory reset both modems I tried, tested with UPNP on and off, tested with DMZ on and off. Factory reset Xbox One, and hard booted Xbox One multiple times. 

 

No matter what troubleshooting step I took Mass Effect Andromeda multiplayer and NHL 17 head to head both are completely unplayable as neither will connect to the opponent/host while using Rogers Cable Internet with an IPv6 address.