For 99% of customers they probably just push the change out to the router, so they wouldn't have to do anything.
What they should have in there is something along the lines of "If you're using a non 2D router, then see www.xyz.com for new settings.
![]() ![]() ![]() ![]() |
|
For 99% of customers they probably just push the change out to the router, so they wouldn't have to do anything.
What they should have in there is something along the lines of "If you're using a non 2D router, then see www.xyz.com for new settings.
Yeah, they just assume you're using their supplied router - if you're swapped it out, then how they meant to know, and hope you know what you're doing :)
The joys of being a geek ;)
Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand
LinkTree - kiwiblast.co.nz - Lego and more
Support Kiwi music! The People Black Smoke Trigger Like A Storm Devilskin
NZ GEEKS Discord______________________________
They may not know on a per-customer basis, but they should have some awareness that some people will have their own hardware. Particularly when they were a bit "geeky" in the Snap days.
Given they are pushing out settings to customers - surely they would have a record of receipt (of settings), or a record of systems being online/available post push?
What would they do with it? It's not practical to contact every customer that the update didn't go through for. It's a given if you're using non ISP gear then you need to support that yourself.
an automated email to the account holder? something like...
-----
Hey we changed some things - if your stuff is broken - check this page that shows the current requirements for BYO hardware
I wonder if there is a slight change in what pppoe settings are accepted on the vocus stack vs the snap stack that people are being migrated off?
That could be the case - as per my first post - I experienced a minor outage the day prior to this happening, but it self rectified (with a bit of a kick onthe ont which i assume did some kind of line reset/establishment.
Its feasible something broken on there end with the migration, then started working again, then broke again.
|
![]() ![]() ![]() ![]() |