It’ll have a QR code printed on it.
That won’t take you to the router’s web server.
It’ll take you to the play store to download the app. Which requires Play Services and access to your exact location, contacts, storage, call history and messages, just to set up your router.
MFW I first got my current router and went to set it up and couldn’t find the factory ID and password on it anywhere. Then realized it was on a damn app now. Which was bad enough, but after jumping through all the hoops, I discovered that (to no surprise really) what you can set up is very limited.
Sure I should buy my own router or flash an older one… but then again the last bad storm that fried the router this one replaced, the ISP replaced it at no charge. So… I live with it, I guess.
it would still the ISP router be the one that connects to the network outside the building, so chances are that if it comes again over tge network cable, it will still only fry the ISP router
Well you could accept the default generated one, or set it to fe80::1 manually. Don’t most good routers now have a DNS server in? So you could make it router.local or something?
I think some even by default make a DNS entry call router.local or similar pointing to themselves. This isn’t a real problem and if IPv6 were adopted fully, then all routers would likely come with something like this setup anyway.
Oh boy I can’t wait to tell my parents to go to fff8::ab298:42cab3:187daq::1 to get to their router.
It’ll have a QR code printed on it.
That won’t take you to the router’s web server.
It’ll take you to the play store to download the app. Which requires Play Services and access to your exact location, contacts, storage, call history and messages, just to set up your router.
MFW I first got my current router and went to set it up and couldn’t find the factory ID and password on it anywhere. Then realized it was on a damn app now. Which was bad enough, but after jumping through all the hoops, I discovered that (to no surprise really) what you can set up is very limited.
Sure I should buy my own router or flash an older one… but then again the last bad storm that fried the router this one replaced, the ISP replaced it at no charge. So… I live with it, I guess.
Wouldn’t it be more sensible to invest in some surge protection, if that’s an issue where you are?
it would still the ISP router be the one that connects to the network outside the building, so chances are that if it comes again over tge network cable, it will still only fry the ISP router
But then they can have like a bajillion devices connected to their router without any collisions!
Well you could accept the default generated one, or set it to fe80::1 manually. Don’t most good routers now have a DNS server in? So you could make it router.local or something?
I think some even by default make a DNS entry call router.local or similar pointing to themselves. This isn’t a real problem and if IPv6 were adopted fully, then all routers would likely come with something like this setup anyway.
mDNS (.local) is a fairly new thing, and not everything supports it well unfortunately.
DNS never has problems and always works. /s
And neither does DHCP.
shouldn’t fe80::1 always just work if IPv6 is enabled?
If you set the ip of the router to fe80::1 then anything directly connected should be fine to connect using that address.
Actually, it’s probably at http://[fd00::1]/
Unless it’s not and then we get alphanumeric soup