We're currently offering our members an exclusive opportunity to participate in a trial of the new firmware for our Fido Home Internet Wi-Fi Modem (CGN3AMF). For details of this program, please click here.
This thread will be used for your feedback regarding the firmware. We've invited some folks from the Network team to participate in this thread. Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.
Thanks for your continued feedback and support!
-- List of Changes --
18.104.22.168T4 (March 28, 2018)
Most likely not firmware related issues. Ask technical support to check your cable connection. I'm using my FIDO modem in Bridge Mode running old firmware version 22.214.171.124 and current uptime is 24+ days without any connection issues.
I've been on the trial for a couple of weeks and it looks like connection loss issues are back.
I'm using the router as a combined modem/router and it happened while streaming music/streaming music/light social media usage on two separate devices.
Sent a message to the admin I got in touch with RE: participating in this trial, hoping to get an answer.
Haven't received any improvements since participating in this pilot.
I'm cancelling my internet with Fido tomorrow. Not really interested in dealing with more disconnections while I'm trying to work from home and stream music. The most simple of tasks shouldn't cause so much headache... Easy fix: goodbye.
Has anyone else had their modem bricked by the firmware update? I signed up to be part of the program on Thansgiving weekend, appeared to have the update pushed to my modem on October 13 (Friday) which promptly bricked my modem. Only the power light comes on after power cycling or pushing the reset button. I PM'd fidosolutions on Friday night was told they'd get back to me by Monday. It's now Wednesday and I've been without Internet for 6 days now and have only been told to wait.
It's the same problem that Rogers experienced in http://communityforums.rogers.com/t5/Internet/Bricked-Modem/td-p/383170 so obviously Rogers knows about this issue. Why is it taking so long to respond to me?
I am sorry that you experienced an issue with the firmware upgrade process. This is an extremelly rare occurence (I have seen only one other case of that) where a modem becomes completely unresponsive after a firmware upgrade.
The modem has 2 firmware banks. We pushing an upgrade through the network, the secondary bank gets updated. If the modem can't boot on this firmware, it will automatically revert to alternate software. It seems that this failsafe mechanism didn't work in your case unfortunately and your modem will need a replacement at this point.
The issue we experienced on the Rogers network back in January (the issue you linked) was a completely different situation, not caused by a firmware update.
Thanks @FirmwareTrial for getting back to me. So how do I go about getting my modem replaced? Do I have to call into tech support to either get one shipped or dropped off or can I get it swapped at a Fido store? I see in that other thread that one can get a Rogers modem swapped at a Rogers store, but I'm not sure the same applies to Fido branded stores and Fido Internet users.
I have received the firmware upgrade. I see no change (except the software version in the web UI). LAN ethernet ports still do not light up (except during power cycle then promptly shut off).
I had received two modems (for two homes) on the same day, same account etc. The other modem does not have this issue.
Do I require a new modem to gain full functionality (of wired ports) or is there a simple fix I am missing? I did not perform a factory reset but I have power cycled the modem a few times since.
Hey @cmcm and thank you so much for the feedack.
It looks like this issue only affects one of your modems.
Having the modem replaced here would be the way to go.
You can visit one of our stores to take care of that. To find a store near you, you can use our locator here.
fw version 126.96.36.199 fixed my issue that I did not notice before until I tried to configure port forwarding for a specific client on my network.On .17 Trying to access the port forwarding page will not work and eventually kick me out of the router admin page. Only solution was a reboot. This issue did not occur with the latest fw.