re: no special characters in passwords
If you switch to bridge mode you can change your password and add special characters. I only tried adding a ".".
I finally got the .23 push to my new modem I swapped out last week. Well, I would suspect the firmware here as I have 3 channels missing post .23 upgrade. All channels were visible on .19 code. @RogersDave Rather than swap out to yet another modem, is Hitron looking at this as a firmware issue?
Just had my CODA-4582 (non black dot) upgraded to .23 this morning. Some wireless devices would not connect when I got home. Did a hard boot of the CODA and devices able to connect.
Was able to connect to devices that were hardwired as normal and speed seems normal after the .23 (approx 750 down and 30 up) from outisde my network.
Also noticed people were talking about missing channels, so far all 32 present and accounted for.
Also noticed that LAN connected devices shows the devices connected, while on .19, was only seeing 1 device. Some devices that I know are wireless are showing up as connected via ethernet.
Wireless connected devices also works and so does site survey.
YYZSAM...did you apply for the .23 trial or just happen to get a .23 release? I am trying to understand what the various release contain e.g 220.127.116.11 (.19 & .23). Intially thought that DOCSIS 3.1 was release dependent but apparently not. It's more related to a CMTS ugrade at the headend and area bandwidth issues. What are your new speed readings and have they improved from .19 Also trying to find out what the optimum OFDM readings should be.
Thanks Sam....Exactly what I was looking for. Didn't realize the Beta pgm started May 2016. Since Rogers L2 is still working on my issue...I may wait to hear back before joining the Beta Trial...although really everyone on the Gigabit plan are Beta testers. Good stuff! Speed test results from three servers (Bell, Shaw, Rogers)...same results in Native or Bridge mode....Top speed was 512 once on Docsis 3.0...on Feb 5.
|OOKLA Speed Tests / Date - Time||Bell/Toronto||Shaw/Winpeg||Rogers/Tor|
|Feb 6 - 11:15 DOCSIS 3.0 (18.104.22.168)||269/45-13||329/36-31||310/47-8|
|Feb 6 - 16:40||91/28-11||92/32-30||88/41-5|
|Feb 7 - 07:40||259/45-6||350/32-31||340/48-8|
|Feb 7 - 11:30||279/45-9||350/37-30||398/37-5|
|Feb 7 - 16:45||268/35-14||334/29-29||333/22-10|
|Feb 8 - 08:10||296/47-6||347/38-30||381/48-8|
|Feb 8 - 11:30||293/46-10||346/37-30||438/48-8|
|Feb 8 - 16:05 DOCSIS 3.1 (22.214.171.124)||89/17-10||91/19-32||91/26-4|
|Feb 8 - 20:10||89/38-11||91/34-30||90/38-4|
|Feb 9 - 08:15||318/46-7||358/34-29||328/46-4|
|Feb 9 - 11:30||91/47-6||91/37-30||90/41-7|
|Feb 9 - 16:45||92/41-17||92/32-30||92/31-10|
|Feb 9 - 21:30||90/20-20||89/26-32||82/30-9|
|Feb 10 - 10:00||273/46-6||352/34-29||374/41-7|
|Feb 10 - 16:30||247/19-17||334/19-30||323/28-8|
If you haven't already, power cycle the modem by pulling the plug.
It's what usually works for me when I lose channels.
I did a pin reset and unplugged for a minute. Result, channels are back. This must certainly point to code, reboot cycle, or NVRAM erase code.
Continuing testing on .23, just came across another switchport 1 issue. I plugged my RaspberryPi in port 1, negotiated to 100Mbps, which is correct, but then unplugged and plugged in my chained gigabit switch. The port stayed green, indicating 10/100. The modem then did not respond to a 192.168.0.1 ping. Had to unplug and plug back in for port 1 to auto-negotiate to 1Gig (yellow light) again.