Sharing the results of 4 Astound “technician” visits w/r/t loss of 75% download speed , a broken Hitron modem, and a working useless Hitron replacement. Note that the Crackerjack Box Hitron modems rented from Astound come with a fixed subnet in their “default” ipAddress which is the equivalent to getting a ‘locked’ cell phone. It locks you into that subnet if you add the modem first, but ruins your LAN speeds and address-sifting if you add the modem to an already-existing LAN which uses a different subnet. Of course, deploying no ‘forward’-compatibility, the firmware web page does not allow the customer/admin to modify that ipAddress. That and any other “admin” functionality” does not even exist on their page. It’s called ‘authoritarian’, ant-user, and chiefly, “lame”. Naturally, with so many “default” user/pwd pairs floating around, none worked, esp. because there was no connection made.
That presents issues for those avoiding the security and slow-down associated with ALL WoiFi/wireless junk-tech. Having all ipAddresses statically set and all connections wired with cat-8e/braided, one seeks to have all devices and data-flow on the same subnet. Elsewise may contribute to why loss of tracking mac/ip addressing as well as reason for losing 75% of my paid-for 600mbps speed. You cannot reserve an address for an off-subnet address, so there is a race condition which subtracts also from address cluttering and extra sifting. Anyone using DHCP would have their “race” condition causing consistent inconsistencies. Static is best for any LAN of more than one [real] computer or peripheral. I do not call a tablet, cell, or any other “Cloud” device w/o sovereign WAN-free compute power a “computer”. A tracking and surveillance device by any other name…. In days of old, terminals sharing time/devices/memory with mainframes, this is a repeat, only with AI surveillance passed off as advertising’s data-mining.
So, when the technician from Astound (who recommended the SB8200 as “working effortlessly tried to even connect to the SB8200 with any number of so-called fixed ipAddresses (e.g., 192.168.0.1, 192.168.100.1), even directly to the modem, he incorrectly reconnected cables so that my Ooma and Roku connectivity was gone. Sure, I still had 75% loss and now, more. The term “technician” is misused if you do not understand more than connecting a small set of rentals, while not even knowing what an “arp” or “netstat” command offers in troubleshooting. He tried valiantly yet failed in like.
So, I walked through a shutdown sequence:with a customer support tech from Ooma. Much better. Sharp and logical.effort that wins my admiration.
- disconnect Ooma Telos box from network
- disconnect router from modem (in ethernet port 1)
- disconnect modem from its power source
- after 12 minutes, connect Ooma to the ethernet port 1
- wait another 5 and connect the Ooma box to ethernet port 1
- wait 2 minutes and then add power to the modem
- after 10-12 minutes and all modem lights are on, connect the Ooma box to its power source
- wait about 15 minutes after the small gree and yellow lights are steady and the red top-light turns from a steady red to a steady blue
- verify that the Ooma voip phone is working
- now plug the [TP-LINK] router into the open ethernet (#2) port
- verify that the phone is still working
- verify that an internet connection is working on one of your router’ed computers
- Now I may try putting a switch in port 1 and the Ooma into that switch….