@RogersDave I was reading the notes for 220.127.116.11 and it mentioned that it includes support for band steering. Can band steering be enabled through modem the interface, or can it only be enabled through your end?
In 18.104.22.168, we have moved the buttons for band-steering and DFS in the customer interface. These will show up under a new "Advanced" tab in the wireless menu. They are both disabled by default but now customers will have the option to enable them.
@RogersDave is there any truth to the rumors of another new modem to replace the CODA-4582?
We did announce that we would be launching a new gateway in 2017 in our financial report. That's all I can tell.
Recently my router was updated to the 22.214.171.124 firmware, and it seemed to have returned some of the problems i had before i had the 126.96.36.199 firmware. Noticeably higher ping times and latency in games like League of Legends, Overwatch, Team Fortress 2, etc. As well as noticeable packet loss. So for reference Overwatch on 188.8.131.52 getting 30-35ms, and 184.108.40.206 getting 50-60ms. And as well on league 25ms -> 40-50ms respectively. Wondering if that is an issue for some other users of this router who are gaming.
Update on this @RogersDave - I'll be doing a factory reset tonight to hopefully revert back to .27 - the latency issue continues to be a problem and it's significant enough that I need to revert. Hoping the next beta patch fixes this issue as it impacts how I make a living
I am still having the issue with this. I picked up the modem just last week. Is there a resolution?
Software Version 220.127.116.11
When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless".
I have been experiencing issues with my Nest Thermostat, Nest Protect and Nest Cam with intermittent connection to my Coda 4582 router since early May. Everything was working great before that. After spending 3-4 hours trying to resolve this problem with Nest and Rogers support and experimentation with various router settings, has not solved the the issue.
I can only suspect that the new firmware is the culprit.
I would appreciate it Rogers could add this to the list of issues to investigate.