Ditto. Slightly different in practice but essentially the same thing here.Interesting - I've (effectively) been with the same ISP for many years but, possibly because I was considered "competent/qualified enough" have always had admin access to and connect a supplied router when one was provided - in the "very early days - pre-wifi" but "post dial-up" my "router" (10 Base T based?) was a self-built PC running Smoothwall Linux. WiFi came later with a Linksys "@ home" unit (which is still working, behind the main router). Currently there are two other WiFi routers behind the main one primariy for other family members use. I'm the admin for all of them.The easiest I think and in my experience is to use the same WiFi SSD and credentials in the new router as with the current pre-fiber. Not only easy w.r.t. RP3A+ but also for your smartphones etc. Don't do multiple changes at once; 'just change internet pipe', not your whole set of devices at home. I know many people get into lots of trouble sometimes when they switch ISP and/or router. Not seldom, those routers are cheap, have almost no configuration setting and they are simply owned and administered by the ISP, not you.
I actually had/have my own router and WiFi APs, so do not use what the ISP offers. I actually refused it (is a law for it where I live, freedom of customer premises equipment), also monthly fee is a bit lower. I also use RPi3B as WiFi AP so anyhow completely my own WiFi connectivity.
IIRC when we moved house a few years ago the router etc. came with us - only the fibre-optic/cable link, tv box etc. had to be "installed" ie. routed/installed within the house.
Trev.
Code:
^ | #Internet v+--------+|ISP Hub | #cable modem mode+--------+ ^ | v+--------+|firewall|+--------+ ^ | #intranet v+------+|switch|+------+ ^ | +-+-----------+ | | v v+-----+ +--------+|wired| |wireless||stuff| |stuff |+-----+ +--------+The downside is I have to maintain the firewall, dns and dhcp myself. That's also the upside because I know for certain only 'port 22' is inbound (key only) and everything on my intranet stays connected when the ISP decides to drop a firmware update on the hub and reboot it. All I lose is the intranet whilst "firewall" negotiates with the rebooted hub for a new ip address.
No need to split things up as much as I have. A suitable managed router with a web interface (?or maybe a pihole?) plugged into the hub would suffice. The above design predates the rpi. It used to be an old PC running FreeBSD 4.x before wireless was really thing!
It is flexible though. For the longest of time we suffered from wireless DEAUTH. Eventually I added in an rpiZW hotspot with logging to confirm that.
If ever I revamp "firewall" I'll probably add a wireless dongle which I can temporarily activate when the ISP hub goes down, the idea being I'll be able to tether it to my phone for those times when yet another contractor digs in the wrong place.
Come to think of it, due to the above, I don't actually know if it's possible to change the SSID on an ISP hub. I never thought to ask because I always assumed it would be possible - because of course it's possible when you buy your own wireless router. Now that I am thinking about it there's good reasons to not allow it.
Statistics: Posted by swampdog — Sun Sep 29, 2024 2:17 am