So, a small update from me, for what it's worth at this moment...
I did get a CODA replacement modem delivered last week. And on Saturday around 2pm, I replaced my modem, just to give it a shot....
At the initial time of install, it took nearly 30min before to CODA modem would establish a stable link, every time it grabbed it and the @ symbol stated to flash, with a few seconds the uplink would drop and the upload arrow would begin flashing again, and within a few more seconds either the @ symbol would try again, or the download arrow would start flashing with no upload arrow and eventually grab the upload and try again.... as I said, about 30min of strange behavior....
Then it was good for about 2 hours, around 4:30pm, it dropped again, but I wasn't home, so I only have my various logs to show this, but after about 25min, the connection restored itself, without a manual reboot of the modem....
Now... since that event at 4:30pm Saturday, until now, about 4pm Monday, EST..... my service hasn't dropped.
Now that said, I have my CODA in bridgemode, so I have no access to the login/configuration pages, and cannot verify what firmware version I am on at this point, or if that 4pm event Saturday was a firmware patch or just a drop...
I can however confirm, that I have had both a valid IPv4 and IPv6 address this entire time, I havnt been monitoring the IPv6 address itself, but the IPv4 is still definitely static and no longer randomized from Rogers.
It's too early to claim the issue is resolved, but it is stable for myself at this time.
I would like to raise a few issues that may need to be considered by bridgemode users and Rogers tech support though...
if Rogers has transitioned from "Automatic" or Randomized IPv4, to Static IPv4, then users like myself, may need to adjust our network setups...
I'm positive nearly all Rogers Bridgemode users, have their WAN setup for 'Automatic' IPv4, and not for Static IPv4. And depending on lease time settings, auto reboot settings, and specfic router firmware and models, our routers may be asking for a new IPv4 address, but receiving the same IPv4, and therefore our routers are confused they didn't recieve a new IPv4, and choke out... hence ISP DHCP errors... because in Automatic IP, the DHCP should issue a new IPv4 when asked too, not issue the same one...
This COULD be one possible part of the issue leading to this problem happening over time, and not always repeating exactly the same way for everyone.... However, I myself am still setup for Automatic IPv4 not Static, and have been ok for the last 48hours....
The main part of the issue though, I still believe, is the removal/discontinued use of IPv4 entirely. As stated by another user above, IPv4 addresses disappeared to 0.0.0.0, while the IPv6 address was still valid. As I said previously, without Rogers informing anyone, especially 3rd party Router manufacturers, they were doing this, there is no built in support for most devices to handel the loss of IPv4 while still having IPv6.
Again, I cannot confirm if a firmware patch was pushed to the modems, or who it was pushed too specifically, or if this was a networked sided change, but it does appear at this moment to be working for myself, no more loss of IPv4 WAN address. I did not personally ask for any NEW patch to be pushed to my modem manually, I did ask several times before my replacement modem to have the firmware rolled back to a previous verison, but they declined and insisted I try a new CODA device instead. Which wasn't new btw, it was clearly "renewed"/used, clear scratches and light cosmetic damages on the rear of the unit in general, and all around the ethernet outlets.
Anyways, I cant do much more but continue to speculate on things until Rogers puts out some kind of official statement about the disconnect of IPv4, confirms the change to Static IPv4 in the mean time, and ensures their entire Canada wide tech support team is fully aware and upto speed on all the changes made, including if bridgemode users need to setup Static IPv4 instead of automatic or if 3rd party routers need to update thier firmware for Native Solo IPv6 services to be accepted in the loss of IPv4, because as it stands, Asus confirmed to me they support dual stack but ipv4 is a requirement still and if lost the IPv6 would not be used to replace IPv4 wan, they are also working on a solution to this issue but are having a hard time themselves as Rogers has not been openly forthcoming on these verifiable and non-verifiable changes to their network and implementation dates for future changes....
