Personal opinion, on any firmware update, especially if you have any issues following the update, reboot/restart the modem at the very least. I'd suggest a factory reset, but, at this point I'm not sure what that will load, the same 220.127.116.11, or will it attempt to return to 36T6? I suspect that returning to 36T6 requires deliberate action from Rogers staff.
I've always found that a modem reboot at the very least, moving from there to a factory reset, has been required to see the modem function as expected after a firmware update, despite the reboot that is scheduled into the update.
In this particular case, this is a big jump, moving to a new kernel.
I'm still on 36T6 at the moment.
When you try 192.168.0.1, does it go to the login page and not respond to the user inputs, or, does the browser simply hang and not access the page?
When in doubt, you should be able to call tech support and ask the tech to factory reset the modem again, that is of course assuming that the tech can actually access the modem.
@RogersIan should be watching for comments such as these.
One thought that comes to mind is to delete the existing Lan and Wifi network profiles from the pc so that windows regenerates those profiles. That shouldn't make any difference, but, there's always a possibility that it might.
Right now it is a wired connection to my PC, but I will try resetting. Previously it was simply Automatic everything but now StaticIP+DNS was needed to actually access internet.
Initially, as others reported, the UI on 192.168.0.1 partially loaded but we saw Login Failure - UnknownError.
I tried logging in now with 0 changes and I actually got the login prompt (previously was just a Chrome-side error 400.
So yeah, this is consistent with the past 2 days of me dealing with this.
1. UnknownError in HTML, can't login
2. If I can login, the UI works for a few seconds or is just empty
3. If I factory reset it works for a little bit, then regresses to #1 or #2
Seems Rogers Tech Support also cannot access the modem when I am unable to. At least it's not my end. Almost certain it's the firmware!
I received 18.104.22.168 over the weekend and with testing against 22.214.171.124, I saw no improvement of my existing issues.
- I cannot forward IPV6 DNS using DHCP
- Issue still exists with my smart devices on 2.4Ghz band
- DDNS pick list unchanged
- 5Ghz wireless is more unstable from 126.96.36.199 (I had to unplug/plug my modem)
If possible, can the 188.8.131.52T6 feature be retained on future 7.1.1.x versions?