Still on 126.96.36.199T6 not sure if it's just taking a while for the 35T1 version to roll out to everyone in the testing program?
The last couple of mornings the CM rebooted itself. I'm not sure if it just crashed or what? the dhcp server still occasionally dies.
I do notice in the port forwarding section, there is a very long list of ports that have been forwarded via upnp. I guess it just remembers them forever and never clears them out. my devices seem to just request new sets of ports when they reboot, and the gateway keeps the old rule in place.
I'll probably just run it in bridged mode until i get new firmware to test. this version is pretty trash since i have to reboot it manually pretty frequently.
one question for other people on the forum. do any of you condition your power? I'm wondering if some of the instability is just dirty power, or spikes or dips in the voltage for some reason.
I believe if you pm communityhelps they should beable to push the firmware to you if not you will have to wait till whenever Rogers Sergio comes back. Do you happen to use the DHCP reservation? I was having trouble on one device losing connection when all other devices worked fine.
*Once I removed the manual reservation it stopped losing the connection.
The dhcp server on the CODA is just screwed. it gave out different ip addresses to the same devices with the same macs. reservations don't seem to improve anything. it lists devices as unknown when other times it does know the device name. it's like someone wrote a dhcp server from scratch as their first coding project.
tired of that, stuck it in bridge mode. using a dd-wrt router now which works just fine.
After this update it seems my modem has a lot of new features. Seem to be having trouble saving settings now. Has anyone else had problems with saving settings?
Interesting I'm seeing the exact opposite for me, this firmware is hitting max speed tests during the 5-10 pm hours every time I test. Previous firmware it was all over the place.
Mind sharing your signal levels and maybe some speed tests? What package are you on? Could perhaps be congestion in your area.
@soundwave80 if you haven't done a modem reboot since the firmware update can you do that by running it via the modem's user interface, or, just pull the power plug, wait 10 to 15 seconds and plug it back in to force a restart.
Is the XBox connected via ethernet or wifi, and if its via wifi, is it via 2.4 or 5. Ghz network?
|1||01/01/1970 00:00:24||68000401||warning||ToD request sent - No Response received;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;|
|2||01/01/1970 00:00:31||68000500||critical||TFTP failed - Request sent - No Response;CM-MAC=-MAC=a;CM-QOS=1.1;CM-VER=3.1;|
|3||01/01/1970 00:00:31||68001101||critical||TFTP Request Retries exceeded, CM unable to register|
|4||01/01/1970 00:00:18||68000401||warning||ToD request sent - No Response received;CM-MAC=;CMTS-MAC=bd:1a;CM-QOS=1.1;CM-VER=3.1;|
|5||01/01/1970 00:00:31||68000500||critical||TFTP failed - Request sent - No Response;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;|
|6||01/01/1970 00:00:31||68001101||critical||TFTP Request Retries exceeded, CM unable to register|
|7||01/01/1970 00:01:04||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;|
|8||06/08/2018 20:40:03||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=:1a;CM-QOS=1.1;CM-VER=3.1|
Do you know what these errors mean? just disconnected