*** 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 18.104.22.168 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).
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 22.214.171.124 but more likely in 126.96.36.199 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 188.8.131.52
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 184.108.40.206
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 220.127.116.11T2
List of connected device does not get fully populated
This is a known issue that has been tracked since firmware 18.104.22.168. 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 22.214.171.124T2 (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 126.96.36.199T2
Missing SC-QAM Channels
After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 188.8.131.52T2 to address this behavior but it has not corrected all scenarios.
Investigation continues with Hitron.
The WiFi Survey functionality in firmware 184.108.40.206T2 (and possibly before) reports incorrect SSID names.
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 220.127.116.11T2.
Update April 22: This issue has been resolved in firmware 18.104.22.168
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.
To say this is becoming frustrating is an understatement.
We have had the new modem approximately 2 weeks and we have had a tech out once and chat support has another on the way.
I may have resolved how the samsung S8 connects by setting a fixed IP address, but the iPhones refuse to interact with this gateway.
The only solution we have found is to unplug and replug the modem when the phone cannot get internet.
What happens when the modem is restarted like that??
Can this info not be used to pinpoint the issue?
Chat guy said ", the signal appears weak to the modem. Just to confirm, has there been any changes made to the Rogers cable installation in the home such as added new wires or splitters?" well the tech that visited said the signal was too high and added a splitter to reduce the signal by -7db.
I think that the signal is within spec (highest is 8.000 and lowes around 0) it feels like fluff when the chat guy wants to send a tech. He did says "I think it is the modem from what you are describing" and agreed to have the tech bring a modem.
I am still seeking an answer to "what happens when I "reboot" my CODA modem?" because I can't believe that the solution is not indicated by the fact that this works every time and instantly to get all affected back to being connected to the internet.
This is what I have been experiencing as well. The wifi gets disconnected after a certain time and would give a 169.xx number as its IP. A reboot is necessary to get it to work again. At first, I thought it was one of my devices having an issue so I changed it to a static address and it has been stable so far.
Not sure if the CODA modem/router has a DHCP issue with the assignment of IP addresses.
I have seen others say this an I should have listened.
Added D Link DIR 885L we have had 48 hrs of bliss.
Hopefully this is a permanent solution.
My family does not care so much about speed as connectivity.
I hey high 700s from speed test with ethernet connected Lenovo laptop.
So as much as it sux to spend $$ on a router I think this is the only reliable way to enjoy this new gateway untill Rogers fixes it.
This isn't specifically a Rogers issue. Majority of Internet gateways suck! And its why people recommend you get a real router for many years now. A device that tries to do many things will never be better than a device that is dedicated to doing one thing.
I'm surprised so many people still continue to fight this battle.
I have had this issue three different times and it seems to happen like clockwork every 3 to 4 months. My upload seems like it is capped at 10Mbps (it has not gone past this in a few days testing both day and at night), I am on the 500/20 plan and I always (when its working correctly) get the offered speed both up and down. My modem is bridged, I use an Asus AC5300 router and have for some time now plus I have done the typical things .. rebooted the modem, reset the modem, tried the speed tests with the computer connected directly to the modem .. all the things Rogers asks you to do when you call and each time this has happened they have told me to go a swap the modem for a new one, that actually does work and does bring back the correct speed but why is this happening in the first place? Can I PM someone and have them look into this please, it's get a little tiresome to have to exchange modems all the time and would like to find out what causes this if it is possible.
Current speed test results
I have noticed that both my PC's have had issues obtaining DHCP IP address when doing a renewal after 1 week. It would either get an address after some delay, or I would have to reboot the PC again to get it.
Yeah don't listen to what they are saying. I switched back to an older modem and my speeds on testmy are consistent.... the COD (WHITE Modem) is trash!!! Rogers just doesn't want to admit it! I had no issues till I went to that modem... I have gone back to the older one... can't stant the packet loss and rogers believes speedtest (flash based trash is true yet when I am connected to my work VPN and I am dropping every 2 - 3 minutes now.. and has nothing to do with my works VPN servers... everything to do with my inconsistent and packet losing internet connection...
I have similar issues. I "upgraded" to the white modem about 2 weeks ago and can't keep a consistent download speed from the usual places. Steam used to max out my 250/10 connection easily, but now with 1000/30, downloads will be all over the place ranging from 0 to around 50MB and stalling at 0 for long periods of time throughout. I spoke with someone at Rogers and they apparently updated the modem from their end including reboot and asked me to use SpeedTest. SpeedTest showed around 950mbit which is complete B.S. considering I can't get over 50mbit from ANY of the other speed test sites, Steam, usenet, linux distro downloads etc. Very disappointed with this so far.
So today my house mate and I have been having this issue where the Ethernet connections to our modem ( CODA -4582U ) the wifi still works but the Ethernet connections will drop and then reconnect and then drop again after awhile. I tried unplugging for awhile and plugging it back in but that only helped for like 30 minutes.
Anybody know what might be causing this?
Regarding my wifi issues wherein I lose the ability to connect to the CODA wifi after some time ( I have to reboot the CODA to re-establish the ability to connect to wifi).
This is what I see from my wireless device after a reboot:
And this is after some time:
Any idea on why this is happening on the CODA? I did not have any of these issues with the older black modem/router. Thanks in advance.
Edit: Re-attached screenshots
I think that many of us are in the same boat with the reality of the layout of our homes. Definitely the description of a 2 story townhouse, is probably similiar to my challenge - a very narrow, long linked home, with a ton of walls.
The solution of the Google WIFI gives you a wireless mesh solution and can be easily expanded on.
Others have used a router in bridge mode in a better location.
In my home, one of the worst spots is right where the cable connection got put for the modem, against a sheet of drywall separating our office/basement rec room from the furnace room. The signal has to pass up through 3 feet of drywall, a steel support I beam, and a couch, with the furnace and lots of electrical behind that wall all causing interference. The best location, we now know would have been our living room on the first floor in the middle of the house, away from transmitting through a vertical wall, and no steel beams, and no electrical, but when we installed, we had wired connections throughout the house, no WIFI devices, and ever since we went WIFI, we have been struggling to find the best solution.
Currently my solution is a wired connection to a D-Link 1620 extender which can be a repeater on wireless or wired as I have done, turn off the 2.4 to avoid any further saturation on that frequency, and only unfortunate thing is that we have to switch our connections as we move around the home, but I named the WIFI SSID as west side from the router on 2.4 and 5.0 and from the repeater east side on 5.0 only to make it easier to know which network signal I should be on.
I have gone the bridged router route with improvements before 5.0 came along and before my 2.4 was totally saturated from my neighbours, then I went the router, with another router on the upper floor acting as an access point - basically the same as the 1620 does.
I looked at the Google WIFI solution that was on sale last week on black friday sales, but they were out of stock, and the repeater was also on sale for under 50.00, so I went that route. I am not fully satisfied, it is a compromise, but the reality of the layout of my home. I can't blame Rogers or Hitron for the reality of how WIFI signals work, and the architectural layout of my home. So I work the solutions.
Thanks for telling all of us what you did, it allows us all to become educated on how to work with the reality of the limitations of WIFI, interference, electrical structural walls and so forth.
Good luck with your solution.
Not sure if this is a CODA issue, but we have a Samsung Camera that in the past we were able to connect to wifi to share pics. Now all of a sudden we are unable to do so. Took the camera in for repair and they reset the wifi internally on the camera. Brought it home and it does not work here. All other devices connect without issue, camera gives me the error "reconnect to the ap or ensure that the ap is available". Have rebooted the camera and the Coda and nothing, also tried manually entering SSiD and credentials. Next step will be trying wifi at friends house or work.
Had a similar issue with a printer which wouldn't connect. Found out that it would connect without issue on the 2.4G band. Is your CODA setup to accept 2.4G connections? Have you allowed g/n mixed mode? Hope it works.....
I've switched my modem 3 times already, spoken to technical support varies times. Even have an interaction number after I've escalated the issue, which I receive a call about every week. Technical Support and even the Hitron Engineer still cannot pin point the root cause. Hopefully you guys can give me some ideas, since this issues is almost at 3 months long.
Has anyone faced issues with not connecting to ipv4 sites (ipv6 sites work perfectly fine) on devices wired or wirelessly connected to the Hitron CODA-4582 Router (FW: 33T3)?
We've tried the following...
I've ran an ipv6-test.com test and its unable to connect to ipv4 "unsupported" on one device but successful on another device. For any device that fails it states that the DNS6 + IP4 is unreachable.
Hope you guys have an insight to resolve this issue.