I use Apple AirPort Express as a way to pipe music over AirPlay from Macs and iPhones. It also extends my Wi-Fi.
This used to work very well when I used my Netgear R7000 router. When I upgraded to CODA-4582 I connected the Airport Express via Ethernet to the CODA-4285.
It seems there is a serious Wi-Fi conflict between CODA-4285 and the AirPort Express. Both Airport Express and CODA-4285 are in the same room only about 3-4ft. apart.
If Rogers gave us the option to use a standard modem I would happily purchase my own.
I'm going to follow Dave's advice and switch my modem but I'm definitely going back to the CGNM 3552, as it's pretty obvious the coda isn't quite ready for prime time.
Here's the thing you are forgetting: all modems/gateways need firmware, and firmware is delivered by your cable company. If there are bugs in the firmware, the bugs will stay until your cable company pushes new firmware to it. So, in my view, the last thing you want is to purchase some unusual modem. That just guarantees it will take longer to fix the bugs...
Honestly, here is what I think this comes down to: the last straight modems in Rogersland were the SB5100 Motorolas, which were shockingly reliable. Everything since has had bugs, both in the gateway side and the cable side. (With the DPC3825 8-channel Cisco probably having less... but... it still can't support IPv6 so clearly it has its flaws too) Somehow, people have presumed that a straight modem would be as magically reliable as the old SB5100s. I see no reason that that would be true (unless, perhaps, like the American MSOs, you were still running 8-channel D3 gear today - I presume the bugs in those have long been fixed).
Take, for example, the CGN3ACSMR/Casa CMTS lockup bug. That was nasty and painful. (Meanwhile, my 4582 has been a dream compared to that) There's no reason a straight modem could not have been affected by that bug just much as the gateways.
Hi Dave after multiple reboots and unplugging now all channels are there. I sent you my MAC address in a pm previously.
Woke up to DOCSIS 3.1 (purple downstream light) this morning.
Modem went offline line right at 12:06am and came back up 12:45.
Ironically I had a tech in early yesterday due to intermittent outages (specially during rainy/snowy weather) since a utility pole was replaced in October.
He replaced all the connectors at the cable ends and I also asked him removed a splitter in the external box. He then ran up the ladder to the overhead cables and noitced the connecter was broken and rusty. Dammit Bell/Acon!
Once back online I noticed the singal strength went up, it was usually 4-6 but now it is 6-8.
Sadly during speed tests I would lose a connection, each and every time. I was ready to call this morning about it but then speedtests were stable and then I ntoiced the purple downstream light. Speeds are now rock solid and latency and jitter has droped to single digits.
I do get the odd link error if I put it under heavy load, multiple speeds tests and netflix streams running but much better than before. I don't get these erros on my slower DSL line and I was fine when on .13. Hopefully it is eliminated with the next firmware upgrade.
I'm downtown eatside, eastend of Riverdale.
Speed and Latency are much better in D3.1 that's why as a gamer I've been waiting for so long for 3.1
Do you play online games? if so, can you please test and tell me how much your ping went down?
I play a little, lately it's BF1 on XB1. Didn't have issues before so not sure if I'll notice any difference.
Thanks for the details re: guest SSID. I actually find it weird having a completely open SSID. I think that's more hackable than just simply having it secured via WPA2.
Also, the error message you got most likely means that you hard coded an IP address in to your network card settings when you connected to the guest SSID. If you set the network card to automatically obtain an IP address (DHCP), then the error should disappear.
Thought I already replied to this - I am not statically assigning an IP addresses to anything so I dont know if this is a bug or something else. Would need someone else to compare with who using a CODA-4582 on f/w .19