how-to block ads
|
Voltron
join:2007-08-04
Bloomington, IN
| reply to daveinpoway
Re: bad new 2wire firmware push?
Hello, daveinoway:
Thank you for your information; all is very helpful. As a point of note, I would regularly check with my 2701HG-B, as to the status of any available updates and for the past two-plus years, I never had one available. I was running 5.29.47 and clicking on the update button, within the 2Wire software, would always state that there were no updates available. Until I started this troubleshooting, I was using an AT&T activation key. Wayjac has stated that by using either a manual activation key and/or placing the 2701HG-B into bridge mode, one can stop the push-installation of newer firmware by AT&T (Wayjac, are you certain on these points? I thought I read where someone was doing this and still received a push-installation update.). I use the non-bridge/NAT mode of the 2Wire, but, I wish I would have known that using the manual activation key would have stopped the push-installation. As others have mentioned, I would prefer to be the one conducting a manual installation of firmware, for many reasons, but, one main reason is to be certain that all other activity is halted, during the installation. Another reason is simply so I am aware that something is about to, is, or has changed on my 2Wire gateway. While others have had their gateways updated, without issue, for whatever reason, it appears that others, including myself, have not escaped, unharmed. And, as of today, I am on my second week of diminished speed and my wireless clients cannot connect, not to mention the hours of my time that have been used to troubleshoot these incredibly frustrating issues. | |
daveinpoway
Premium
join:2006-07-03
Poway, CA
1 edit | Something else of interest- I have also have access to another 2701HG-B that was shipped out in April 2008 (not a typo) and never used until this week. It was shipped with the 5.29.109.5 firmware loaded into it. This means that the new firmware has been available for at least 18 months (perhaps significantly longer).
One might wonder why this amount of time has not been sufficient for 2Wire to learn about the problems with this firmware. If they know about the problems and are pushing the firmware out anyway, this doesn't seem right.
Stop the presses! I see here »How to get a new 2wire home gateway? that the new firmware was available as far back as August 31, 2007! Definitely plenty of time for 2Wire to be aware of the problems. | |
Voltron
join:2007-08-04
Bloomington, IN
| Hi, daveinpoway:
I, too, have seen and was aware that 5.29.109.5 has been out for quite a long time; it was curious to me, too, whenever I would check for updates, within the 2701HG-B, that it would always say that I was up-to-date, when I knew there was newer firmware "out there." I guess I should consider myself "lucky" that AT&T decided to wait until the beginning of September 2009, to push this firmware out to me.
As someone who likes to be up-to-date on system/software patches and firmware, knowing there was a newer version available and I was unable to patch the gateway bothered me, since we do not have control over the firmware updates. I assumed that if AT&T had not pushed this firmware out to me that it meant that I wasn't vulnerable to known attacks, via the 2701HG-B. After all, it is in AT&T's best interest to keep their end users free from such attacks. My assumption was that everyone would be looking out for everyone else; again, especially, since AT&T and 2Wire lock out the firmware updating process to users. When such updates are pushed out, without user intervention, let alone any notice, with so many users, it is unthinkable that there would not be some users with bad experiences, unfortunately. For what it is worth, I think users should be given the opportunity to either let the updates take place, automatically or be responsible to manually update the gateways, themselves. I am certain I am not the only one who has thought this. Having said that, I respect AT&T for wanting to maintain their own firmware, if it means keeping their network better protected. But, when it dampens users' experiences, the process should be reexamined.
In the end, I hope to have a complete and painless resolution, as soon as possible. Both 2Wire and AT&T are aware of my specific issues; we'll wait and see how these issues get resolved. I will do my best to keep everyone updated. Everyone else should feel free to continue contributing their experiences to these forums and to the Internet, at large, as we continue to gather more information.
Thank you, everyone! | |
Voltron
join:2007-08-04
Bloomington, IN
| reply to cowbert
Hello, cowbert:
I am curious to know if you have heard anything from 2Wire, regarding the JTAGging of your gateway. As I previously said, I have two gateways and one needs JTAGged and I am curious as to how long the entire process may take.
Thank you for the information. | |
cowbert
join:2006-12-28
Canaan, CT
| it's supposedly in the mail on its way back atm. Never got a tracking # from them so no idea where it is in the system. They implied they got it to enough of a state that DHCP and stuff work, but since they never hooked it up to a DSLAM they could not test the continous rebooting issue. | |
Voltron
join:2007-08-04
Bloomington, IN
| Hello, cowbert:
I was wondering how the JTAGging turned out? Are you using the 2701HG-B gateway that you had 2Wire JTAG and, if so, how is it doing? Does everything seem normal? Was the whole process worth it?
Thanks for any information! | |
-
|
