Linux WIFI Not Supported by Spectrum/Charter?

[GlowInTheDark]

I actually don't see from OP's postings a statement that it doesn't work (with the Pi), although I suppose you could read that between the lines (as in, why else post at all?).

So, let's be clear (questions for OP):

1) Does it work on the Pi?

2) Does it work under Windows?

Note: If you don't have a Windows to test on, you may need to get one (i.e., set one up). Once you do that, then you should be able to communicate with Spectrum - and see if it is, indeed, a "them problem" as opposed to a "you problem".

Note 2: If you do have a Windows system to test on, and it does indeed work on Windows, but not on the Pi (i.e., the answer to the above two questions are different), then there truly is something bizarro going on.

[ejolson]

I have to agree that it's great as a business plan. Just skim the cream of the crop and by-bye to troublesome minority. Worked for Microsoft (IIRC their magic number was 85%) so... Also understandable these guys shouldn't have to spend big money on obscure OS.

Still not happy but have time to try a few things. Best info from this thread is at least some people do have it working. Thanks.

I have Spectrum Charter here. Except for being unbelievably slow, it does work. If the network is working with an Android phone, that's Linux and working. Many routers and smart switches have Linux inside as do televisions. If any of these devices work on your new network, then the Raspberry Pi should work as well.

The difficulty I've found is when nothing works. Then it might help to have a Windows computer set up for the cable modem repair person to test. My recent experience was that the cable modem repair person brought their own laptop to make sure everything was working.

As many have mentioned, the network protocols are standardized. The buggy DSL modems that required the service provider to route everything through an additional PTP layer are long gone. If your PC works but the Pi doesn't, it is likely to be a simple configuration error on the Pi. Good luck! Sometimes the simple things are the most difficult to find and correct.

[dickon]

If it works wired, it should work wireless. If not, buy a second, wifi-capable Pi (0W, 3, 4, I think), and turn it into an access point connected to the wired ethernet; I do this routinely with Pis, and it works very well.

[bjtheone]

Hold on did I not suggest plugging your own router into their box earlier?

Sorry about that... its what I get for skimming

[neilgl]

No worries.

[emma1997]

OK, so I bought a couple cheap cable routers and when they arrived was very surprised they did not have WIFI built in. Not helpful here. That's the level I was at, spoiled by decades of DSL with modem/router/WIFI all combined in one cheap tiny compact unit so naturally assumed...

This stuff is taking up half the room. Even the old dialup Zoom 56k were not such a mess.

Since then got a lot more up to speed on modern gear. Hours dealing with Spectrum tech support who seemed to know even less about these things than me. At least half dozen different individuals. Finally, contacting billing dept to deactivate the service, got a fellow who knew exactly what the problem was with useful suggestions. Billing mind you.

That particular Spectrum router model is known by gamers (Me, XP, Win95, MSDOS!) nothing but trouble with oddball OSs. Reinforcing what some in this thread suggested, get a different router. Dual band, no coax, (make sure it's WIFI lol) so I have a Linksys EA7300 on the way. It ain't $7 like the first ones but 20 and change so, again, no big risk. Hope I get it right this time.

We shall seeeeeeee...

[wh7qq]

Found the same problem years ago with Starband Satelline (now ViaSat)...Just no tech support for other (non W$/Crapple). No big deal...Linux net stuff is totally basic and standard so it "just works". The hardware had no built in router at that point and I just hooked my Asus RT-N66 to it. Note that AES WPA2 is very finicky and the slightest misspelling or wrong case will prevent association. It might not be optimally secure (but I am out in the boondocks) so I use a passphrase I can recall even with my ageing memory, It is in plain English but with no caps or punctuation, words separated with underscores. Easiest is to copy (^C) it from the router page and paste it (^V) into the RPi.

I hope this doesn't labor the obvious too much but sometimes easy gets overlooked.

[trejan]

Note that AES WPA2 is very finicky and the slightest misspelling or wrong case will prevent association.

It wouldn't be a very good password if it let you in even if you didn't get it exactly right.

[W. H. Heydt]

I'm truly sorry I didn't notice this thread sooner...

Something to know about "cable boxes". They are--as people have noted--combined modems and routers. You can, obviously, connect your own router to one of the ports on the combined unit. There are two important things to know about doing that. The first is that, if the router function is left enabled, you should use a *different* IP block on the second router. Otherwise, you are "double NATting" and that can lead to all manner of weird problems. The other way around that is that such boxes pretty much always can be put in "bridge mode" (just ask tech support how to "bridge my modem" if you can't figure it out on your own, just deflect any questions about why or what OS you're using and insist that you want their box bridged. Stick to your guns.).

Now all of that said, the *first* thing I do when faced with a new box from an ISP is log into it, look at what controls I've got, and start setting it up the way *I* want, not the way *they* have it. The absolute first thing is the change the admin password. Change the ID, too, if you can. Set up the IP block you want use, if different from the default. Pick your WiFi channel(s), set the SSID(s), and passphrase(s) to suit yourself. Shut down any access your ISP has set for random open access or "guest" accounts, though you can just configure the later if you expect to use it.

Only once all of that stuff is it *your* modem/router and not the ISPs.

As others have already said, it is understandable that your ISP doesn't want to actually train their help desk (first tier almost certainly run from a notebook full of scripted questions and responses; second tier will probably have *some* discretion in how they deal with a given problem and you might even hit someone actually knowledgeable who can really *help*, but don't bet on it) to deal with anything other than the lowest common denominator. If all else fails, be prepared to lie about what you're using. In spite of all that, there is absolutely no reason why WiFi access would work from a Win 10 system and not work from a Linux system. After all, the same hardware could be running each of those.

A side not on what to do if you hopelessly foul up the configuration. Somewhere, there will be a small hole labeled "reset" (might be a button, but it's usually a hole). Straighten a paper-clip. Push the end into the hole *firmly*, and hold it there. Power the device on for about 10 seconds. Take the paper-clip out. You should now be reset to the manufacturers default configuration.

(I've been on the other side. I once spent 18 months doing Tier 2 DSL support at AT&T. Over time, *what* we could actually help with got to be less and less. It got to the point that even if you knew how to walk a customer through configuring a router, we weren't *allowed* to.

[emma1997]

Thanks for the tips. A few experienced words like yours will probably save me many hours of researching and trial and error (with my luck, mostly error).

Other than some port forwarding and other basic stuff my own experience here is minimal. Even after writing an IP stack from scratch but that was back in the days of Arachne, well before Windows and Internet. I've been getting by as an appliance user being spoiled by the DSL all-in-one and Verizon babysitting.

I've got at least a dozen plain routers from the days of 'borrowing' local hotspots but that hasn't worked for decades what with all locked by default since N. Might be worth investigating hooking one up as secondary net but best to wait for another go-around.

Hopefully I won't have to get too deep into this as it's not my area professionally or recreationally. Better not get my hopes up though, Linux has also been on my What NOT To Do List but look what happened there. lol

When the new (previously owned) wireless router arrives will be time to play again. I hope it gets here before the Spectrum trial period expires otherwise these three routers will be another 30 bucks down the drain.

I appreciate all the input so far and even if it don't fix this specific problem might come in handy for future projects. IT and networking gear in general unavoidable in this day and age. Long overdue for me personally.