(24 Jan 2008)
Automatically Updated Firmware Breaks Static DHCP
I've been using static DHCP from an Actiontec MI424WR wireless broadband router, provided "free" with my Verizon FiOS Internet service, to assign IP addresses on my home network. Early this morning, a member of my family complained that the big blue "e" on her laptop wasn't taking her anywhere, and it quickly became apparent that the wireless adapter wasn't receiving a DHCP lease.
I dutifully logged into my router's web admin console, went to:
'Advanced' > ('Yes') > 'IP Address Distribution' > 'Connection List' > 'DHCP Connections'
Lo and behold, all the MAC address to IP address mappings that I had painstakingly entered into the DHCP table were gone! I tried creating a new static entry for the MAC address in question, but after saving it, nothing was added to the table, and releasing and renewing the DHCP lease on the notebook only brought up an IP address in the zeroconf range (169.254.0.0/16).
Sure I could've switched to a static IP on the laptop or dynamic DHCP, but I was still disturbed by the apparently spontaneous loss of static DHCP functionality. Fortunately, I stumbled into a forum posting which saved me much hair-pulling:
http://www.dslreports.com/forum/r19848466-Actiontec-Firmware-40161560107-Bug-Static-IPs
It seems the router had been kind enough to automatically upgrade its firmware to the latest release, 4.0.16.1.56.0.10.7, which is apparently breaks static DHCP. Supposedly, this is "a 'known issue' that is being worked on." Thanks, Actiontec.
Firmware Restore
Fortunately, our friends at Actiontec also provided for firmware rollbacks, and roll back I did:
'Advanced' > ('Yes') > 'Firmware Restore' > 'Restore Backup Firmware'
The installed firmware version prior to the upgrade (4.0.16.1.45.160.27) had been saved, and after clicking the button and waiting for a minute or so as the rollback was applied and the router rebooted, my static DHCP entries were once again visible, and I was again able to establish a DHCP lease on the laptop that had lost connectivity.
(As with any firmware update, be careful with this stuff, kids. It might brick your shiny expensive gadget.)
Disabling Automatic Firmware Updates
For good measure, I disabled automatic updates:
'Advanced' > ('Yes') > 'Firmware Upgrade' > Set 'Upgrade from Internet' to 'Automatic Check Disabled'.
(Update - 13 Feb 2008 - For some reason, even after disabling automatic firmware update checks, the firmware continues to be automagically updated. I downgraded for a second time, but the new firmware keeps coming back, as persistently as the Terminator. Perhaps the firmware is being pushed to me by Verizon rather than pulled by the router.
Ugh, yet another ISP-supplied device with ISP-specific customizations that's become a source of frustration in my life. I might just go back to using my own router, although the Verizon installer, in his infinite wisdom, ran coax from the router to the ONT (Optical Network Terminal) rather than good ol' cat 5, so I'd have to run some cable or get a MoCA adapter or compatible router. I suppose I could run DHCP services from another device, but that would be yet another box taking up space and sucking up electricity. Oh well, I still have some time before the DHCP leases expire...)
Customer Disservice
Unfortunately, I was inclined to doubt that Actiontec had released new firmware just for fun, and although the latest release had that nasty static DHCP regression, it might very well have included some critical security or stability updates. 411?
The Actiontec website at www.actiontec.com was not very helpful. The router in question, again an MI424WR, was not listed under 'Support' or 'Downloads' as far as I could tell, only under 'Products'. Visiting Verizon at www.verizon.com and wading through FiOS support wasn't especially fruitful, either, although I can't discount the possibility that some useful information was buried in there somewhere.
Craving instant gratification, I called the number listed for FiOS support, 1-888-553-1555. Toying with the irritating automated interactive voice response system led me to a "router" option that tested my connection and told me it was just dandy, which I already knew. Despite ominous warnings of high call volumes and delayed responses, after screaming "agent" a few times, I was quickly connected to a live service representative.
To her credit, the rep seemed patient, willing to help, and spoke in a clear American English accent, with a bit of a Southern twang. She didn't initially seem to understand the static DHCP issue, though it is admittedly somewhat esoteric, and I might not have communicated it in the best way. I explained to her that I was interested in information on what changes might have been made in the latest firmware release, and she put me on hold while she tried calling Actiontec. She got back to me with a very long web link that had apparently been verbally communicated to her and which only led her to a "page not found" error. At some point, she indicated that she'd been told to try directing me to the 'Firmware Upgrade' page on the router's web console, but I expressed that I'd already been there, and there didn't seem to be any relevant information.
Perseverantly refusing to be stymied, she told me she'd try making another call and again placed me on hold. This time she told me that although she'd had trouble understanding her contact at Actiontec through a thick accent, it seemed the firmware was geared towards faster router boot-ups, and that an email should have been sent by Actiontec to my primary Verizon email address (which I never use) with the information I'd been seeking. I verified that I'd received the email, which had a hefty 99 MB ZIP archive ("BHR_Self_Helps.zip [sic]") attached, and I thanked the Verizon rep for her efforts.
Low expectations spared me from any disappointment. After unpacking the ZIP archive, I found an odd collection of directories with names like "Commander Blasius" and "new Gary" containing what appeared to be end user documentation in the form of DOCs, rich text files, and images. The "Firmware Upgrade" folder seemed to have some promise but contained only a rich text file with a walkthrough of the firmware upgrade process, which had been designed intuitively enough that I'd already found it without consulting any documentation.
(Update - 13 Feb 2008)
On a Wednesday, around 6 p.m. Eastern Time, I went to Actiontec's web site and filled out their Technical Support Request Form. The MI424WR was included in their "Product" list, as was Verizon under "Where Purchased". I described both the static DHCP breakage and the persistence of phantom automatic firmware updates after automatic checks had been disabled. At 6:29 p.m. Eastern Time, I received an email response from Actiontec:
We've seen more calls regarding this and the issue is currently under review by VERIZON. Until new firmware code is released however there is no correction.
I am impressed that Actiontec Technical Support responded in a timely fashion. I would have been more impressed if some fix had miraculously been implemented over the course of three weeks, or if the issue had never arisen to begin with.
(6 votes)
