01-05-2017 11:03 AM - edited 05-02-2017 07:09 AM
*** This post was last edited May 2, 2017 ***
Good morning Community,
As I mentioned in a post two days ago, we have received the next firmware 2.0.10.20 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.
However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.
In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂
UDP Packet Loss
The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.
Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).
Bufferbloat
When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.
Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 2.0.10.27 but more likely in 2.0.10.28 and a change in network configuration.
The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.
Update April 22: This problem seems resolved in firmware 2.0.10.27
5 GHz WiFi Low range for channels 36 to 48
Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.
Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.
Workaround: manually select higher channels (149-153-157-161)
Update April 22: The channel selection algorithm has been improved in firmware 2.0.10.27
Loss of OFDM Channel Lock
Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.
Update April 12: This problem is resolved in 2.0.10.26T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 2.0.10.13. We are making improvements at every firmware but it is not a perfect system.
The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.
NAT Loopback not working for wired clients
When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.
Update April 12: This problem is resolved in 2.0.10.26T2 (not confirmed)
LAN Counters not working
Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.
This problem has been reported to Hitron for investigation.
Unexpected modem reboot
Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.
Update April 12: This problem is resolved in 2.0.10.26T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
WiFi Survey
The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.
Guest Network
When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless". This has been reported in firmware 2.0.10.26T2.
Update April 22: This issue has been resolved in firmware 2.0.10.27
Update May 2: It seems this issue is not fully resolved and still experienced by some users
Future Planned Improvements
The following are items that we are working on in parallel of the above.
Dave
*Edited Labels*
04-26-2017 11:17 AM - edited 04-26-2017 11:18 AM
04-26-2017 12:20 PM
@Mythen wrote:
Ok so anyone else having the same issue as us Atlantic crowd with twitch. I have the Google DNS in my windows network settings. Haven't had a chance to see if it was better. But seemed to make a difference. Does this make any sense?
Can you post your tracert -d information using both the Google and Rogers DNS settings? That'll let us know.
If we can conclusively prove that the DNS helps, then that's probably something that Rogers can really easily fix.
04-26-2017 12:23 PM
04-26-2017 12:26 PM - edited 04-26-2017 12:27 PM
@Mythen Did you do one to Twitch? I only see the google.ca ones. I also don't see the IP addresses in the google.ca trace, so it's unfortunately not very helpful.
04-26-2017 12:28 PM - edited 04-26-2017 12:29 PM
04-26-2017 12:31 PM
.27 has been leaps and bounds better for me. My Smoke ping graphs have been way smoother. I've ditched Twitch due to its slow protocol and moved over to BEam and it has been nothing but amazing lately.
I'll try twitch out again just to see whats what, but its always given me random issues that are not connection related but related to the kinda clunky Xbox twitch app, which is why i abandoned it, that and Beams FTL protocol and interactive streams is bad A**.
04-26-2017 12:37 PM
04-26-2017 01:06 PM
@Mythen wrote:
I'll do a twitch one later this evening. Can you post the command you want me to try?
Unfortunately I'm not familiar with the DNS entries for twitch servers -- does anyone here have an idea?
Once you figure out which servers are being used (which you can probably do by just using the browser's network inspector), do a "tracert -d {twitch server}" using both Rogers and Google's DNS. Maybe even OpenDNS for fun.
The -d only reports ip addresses as opposed to hostnames, so it helps to see exactly what is being resolved.
I tried it myself, just by going to their homepage, and wow, I'm not impressed. The video was choppy and stutters. Failed connections all over the place, and it's not even touching my network capacity. It's also resolving to the same DNS entry for me. Considering that I have no problem with other streaming services, it's not fair to fault Rogers if the service itself is poor.
> video-edge-781dc0.ord02.hls.ttvnw.net Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: video-edge-781dc0.ord02.hls.ttvnw.net Address: 192.16.66.85 > video-edge-781dc0.ord02.hls.ttvnw.net Server: [192.168.1.1] Address: 192.168.1.1 Non-authoritative answer: Name: video-edge-781dc0.ord02.hls.ttvnw.net Address: 192.16.66.85
04-26-2017 01:08 PM
@Mythen wrote:
@Jeffj. Beam is that a different way to watch twitch streams if so how do I use it?
Its actually a different streaming service owned by Microsoft and is intigrated into Windows 10 and Xbox one by defauly. It also has the fastest latency free streaming protocol in the market.
http://www.beam.pro
Check it out.
04-26-2017 03:22 PM - edited 04-26-2017 03:23 PM
Community,
I do not want to hijack this interesting discussion around Twitch but have some other updates and questions.
A few users reported performance issues with 2.0.10.27 in this thread in via private message. It is taking a long time but I'm reviewing every single one of them, trying to find an explanation.
Regarding Twitch in Atlantic, it is also on my radar and want to look at it, just swamped with other items at the moment.
Now for the question, we had an old item on the issue list where some of you were unable to access Samba shares over WiFi on the CODA. This has been marked in my tracking list as resolved since firmware 2.0.10.23 but I'm hearing that some users are still experiencing issues.
I would appreciate feedback on this either way to assess if this is still an issue or not.
Thanks
Dave
04-26-2017 03:36 PM
04-26-2017 03:39 PM
@RogersDave I'm currently watching some streams on Twitch.tv and experiencing a lot of buffering. This buffering has been going on for to 2-3 weeks now. I think this Twitch problem not only applies to the Atlantic region, but as well for Ontario.
04-26-2017 03:52 PM
04-26-2017 04:07 PM
Any update on this? I still contiune to have issues.
04-26-2017 04:23 PM - edited 04-26-2017 04:24 PM
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
tracert -d www.twitch.tv
Tracing route to e9221.e2.akamaiedge.net [104.93.188.110]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.0.1
2 16 ms 14 ms 7 ms
3 13 ms 14 ms 15 ms 67.231.222.249
4 45 ms 38 ms 38 ms 69.63.250.197
5 61 ms 54 ms 54 ms 209.148.229.245
6 72 ms 62 ms 80 ms 209.148.229.229
7 62 ms 63 ms 58 ms 209.148.230.10
8 * * * Request timed out.
9 61 ms 59 ms 61 ms 104.93.188.110
Trace complete.
this is a trace using the google DNS
04-26-2017 04:28 PM
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
tracert -d www.twitch.tv
Tracing route to e9221.e2.akamaiedge.net [104.93.188.110]
over a maximum of 30 hops:
1 <1 ms 1 ms * 192.168.0.1
2 11 ms 8 ms 9 ms
3 11 ms 11 ms 19 ms 67.231.222.249
4 43 ms 46 ms 38 ms 69.63.250.197
5 59 ms 54 ms 55 ms 209.148.229.245
6 58 ms 71 ms 61 ms 209.148.229.229
7 60 ms 62 ms 60 ms 209.148.230.10
8 * * * Request timed out.
9 58 ms 55 ms 61 ms 104.93.188.110
Trace complete.
this one is using the Rogers DNS
04-26-2017 04:31 PM
@Mythen wrote:Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
tracert -d www.twitch.tv
Tracing route to e9221.e2.akamaiedge.net [104.93.188.110]
over a maximum of 30 hops:1 <1 ms 1 ms * 192.168.0.1
2 11 ms 8 ms 9 ms
3 11 ms 11 ms 19 ms 67.231.222.249
4 43 ms 46 ms 38 ms 69.63.250.197
5 59 ms 54 ms 55 ms 209.148.229.245
6 58 ms 71 ms 61 ms 209.148.229.229
7 60 ms 62 ms 60 ms 209.148.230.10
8 * * * Request timed out.
9 58 ms 55 ms 61 ms 104.93.188.110Trace complete.
this one is using the Rogers DNS
Be sure to flush your dns cache when you switch DNS server or it wont even make a request ot the new dns when you switch them if the cache hit on the computer is valid (which it will be).
With these results it appears its still using googles cached dns results
ipconfig /flushdns
04-26-2017 04:34 PM
@Mythen unfortunately the twitch.tv traceroute itself doesn't help -- we need the servers that are actually providing the streaming.
If you press F12 in your browser, you can head over to the network tab and see the actual requests (including server names) that are used to provide the streams.
For example, I just tried now and it is video-edge-83437c.ord02.hls.ttvnw.net
04-26-2017 04:34 PM
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 12 | 80 | 71 | 0 | 0 | 1 | 0 |
- 1 | 112 | 111 | 7 | 11 | 19 | 12 |
| 67.231.222.249 - 1 | 112 | 111 | 7 | 17 | 523 | 8 |
| 69.63.250.197 - 1 | 112 | 111 | 35 | 47 | 550 | 47 |
| 209.148.229.245 - 1 | 112 | 111 | 50 | 61 | 562 | 53 |
| 209.148.229.229 - 0 | 116 | 116 | 55 | 64 | 75 | 67 |
| 209.148.230.10 - 1 | 112 | 111 | 56 | 61 | 83 | 59 |
| No response from host - 100 | 23 | 0 | 0 | 0 | 0 | 0 |
|a104-93-188-110.deploy.static.akamaitechnologies.com - 1 | 112 | 111 | 53 | 63 | 570 | 56 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
with rogers DNS
04-26-2017 04:40 PM - edited 04-26-2017 05:36 PM
@Jeffj wrote:
Be sure to flush your dns cache when you switch DNS server or it wont even make a request ot the new dns when you switch them if the cache hit on the computer is valid (which it will be).
With these results it appears its still using googles cached dns results
ipconfig /flushdns
Changing the DNS servers [in windows] will automatically do that.
You can verify that you're getting the correct results by using nslookup instead, and manually specifying which server to query.
The results are actually the same:
> video-edge-83437c.ord02.hls.ttvnw.net Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: video-edge-83437c.ord02.hls.ttvnw.net Address: 192.16.66.49 > twitch.tv Server: google-public-dns-a.google.com Address: 8.8.8.8 Non-authoritative answer: Name: twitch.tv Addresses: 52.36.196.57 50.112.196.159 52.41.96.17
> video-edge-83437c.ord02.hls.ttvnw.net
Server: dns.cs.net.rogers.com
Address: 64.71.255.198
Non-authoritative answer:
Name: video-edge-83437c.ord02.hls.ttvnw.net
Address: 192.16.66.49
> twitch.tv
Server: dns.cs.net.rogers.com
Address: 64.71.255.198
Non-authoritative answer:
Name: twitch.tv
Addresses: 50.112.196.159
52.36.196.57
52.41.96.17
04-26-2017 04:41 PM