http://www.dslreports.com/forum/bad-new-2wire-firmware-push-23080119 en Sat, 11 Feb 2012 01:32:29 EDT Sat, 11 Feb 2012 01:32:29 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23254552
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!]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23254552 Wed, 28 Oct 2009 12:29:44 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23194986 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23194986 Fri, 16 Oct 2009 14:29:46 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23194969
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.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23194969 Fri, 16 Oct 2009 14:27:03 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23143181
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!]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23143181 Tue, 06 Oct 2009 22:31:57 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23141470
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.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23141470 Tue, 06 Oct 2009 17:03:49 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23140430
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.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23140430 Tue, 06 Oct 2009 13:48:42 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23140362
Thank you for the pricing information; it is very helpful. If you would not mind, please, keep us updated on the success of your 2701HG-B's JTAG re-flashing; I am also interested in how long it takes 2Wire to conduct the JTAGing and then get it shipped back to you. By the way, I, too, have the original packing materials for the 2701HG-B--Pack Rats unite!!!

I thought someone had mentioned that the shipping was for overnight delivery, though, your $11.00 and $6.00 charges seem somewhat inexpensive for overnight shipping. What delivery time/schedule is your package/2Wire being shipped under? Again, thank you for these specifics and we all look forward to a great and success update on the JTAGing.

Thank you, cowbert!]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23140362 Tue, 06 Oct 2009 13:34:09 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23139814 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23139814 Tue, 06 Oct 2009 11:59:46 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23138670 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23138670 Tue, 06 Oct 2009 07:56:06 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23138662 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23138662 Tue, 06 Oct 2009 07:53:32 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23137332 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23137332 Mon, 05 Oct 2009 21:32:01 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23137071
Would you mind to let me know how much the shipping cost you? I am considering sending a 2701HG-B to 2Wire, to get it JTAGed. Thank you.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23137071 Mon, 05 Oct 2009 20:48:11 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132508 Re: bad new 2wire firmware push? again...]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132508 Sun, 04 Oct 2009 23:56:03 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132424
I had a wired [VOIP host] and a wireless device [desktop wired to an AP in the basement] and possibly a laptop [don't remember if it was left on at that time or not] connected when the firmware was upgraded, and they're none the worse for wear. As far as they're concerned, the network went down for half a minute, then came back up.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132424 Sun, 04 Oct 2009 23:32:39 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132385
I apologize if you have read this, as I replied to this, earlier; I am only posting, again, in case you missed this. May I inquire as to how much it cost you to RMA the 2701HG-B back to 2Wire, for a JTAG? I have one 2701HG-B that works, albeit with speed and wireless issues and one 2701HG-B that is not working, at all.

Thank you, again for this information, cowbert.

--Voltron]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132385 Sun, 04 Oct 2009 23:19:43 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132372
Yes, I agree with wayjac; that is good to know. Let me ask you this, DrStrange: when you received the upgrade, did you have any wired and/or wireless devices connected to the gateway AND RUNNING, during the upgrade? Without any notice from AT&T, regarding the pending firmware upgrade, I did not know to disconnect anything; so, as is usual for me, I have a wireless ethernet bridge connected, wirelessly, to the 2701HG-B and it was connected, when the firmware was upgraded. Since your download/upload speeds and wireless connections are not having any problems and I am experiencing both, particularly the wireless issues (although the speed issues are somewhat more frustrating), I wonder if it is because a wireless client was connected, at the time of the update. If I were updating the firmware, manually, I would never have anything connected, let alone running, at the time of the update. If this is the case, then, a request to AT&T to reflash the gateway with 5.29.109.5, at a specific time or within a specific timeframe would be extremely helpful, to troubleshoot these issues. I only hope that AT&T is willing to do such a thing. So far, those at customer/technical support do NOT want to even discuss possible issues regarding the firmware.

Does anyone know how we can reach those responsible for the firmware updates, at AT&T, to schedule a reflash? Thank you, everyone for your assistance; all this information is extremely helpful.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23132372 Sun, 04 Oct 2009 23:16:10 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23130367 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23130367 Sun, 04 Oct 2009 15:02:46 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23128634
No connection problems with firmware 5.29.109.5 on a 2701HG-B. Noise margins and other stats are same as before. All is well.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23128634 Sun, 04 Oct 2009 01:53:51 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114659 The att key code supports PPPoE, PPPoA, Static and Dhcp accounts
There are att legacy customers with each of the above account types]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114659 Thu, 01 Oct 2009 14:49:24 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114567 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114567 Thu, 01 Oct 2009 14:37:08 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114489 said by DrStrange:

I'm not an AT&T customer, so anything affecting AT&T customers won't necessarily affect me.
Your 2wire can be updated if it has a public ip address, and still has the att key code

There are ways to prevent a att 2wire from being updated
Change the key code to one that is not assoiciated with any ISP
Configuring for bridge mode]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23114489 Thu, 01 Oct 2009 14:24:00 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23111318 :

I opened a ticket with 2wire on 9/27 via »support.2wire.com/

You have to create a login first, then use the "ask a question" option, since it's about one of their equipment models, you leave it on 2wire products.

I posted the fullest possible bug report I could get, which wasn't much since I did not have the ability to access the UI. Since it appears that you can access the UI, then you're going to have to look for the relevant logs and do more testing, particularly doing a factory reset and reflash using the web interface. Also you should have access to more extensive logs (turn on syslog facility if you have to so you can trace exactly what happens right before the reboot). Since I was unable to access the UI AND my reset button was not working the way it should be working, I had little choice but to submit a superficial looking ticket because I could really only stick to reporting symptoms and the state of things and could do very little field testing. In any case, I used the relevant terminology in my report (as I'm a real-life network engineer during the day), so that I wouldn't look like some random clueless person that was being vague about everything.

2wire replied asking for SN and ISP hoping to be able to remote to the modem, but as I expected, they could not, so 2 days later they sent me an RMA address for their JTAG facility in Arizona. No charge, but no promises either (and I had to pay outbound shipping).]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23111318 Thu, 01 Oct 2009 01:44:38 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23111299 sudden 2700HG-B failure]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23111299 Thu, 01 Oct 2009 01:36:17 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107776
EDIT: AT&T sould still be notified even if 2Wire is the source of the firmware. It would save their techs and support people a lot of headaches.

I'm not an AT&T customer, so anything affecting AT&T customers won't necessarily affect me. I have a 2701HG-B running firmware 5.29.47, but I haven't seen any firmware upgrades.
[EDIT: Firmware upgrade hit on 10-3 at 4:50AM]

I just checked manually for a firmware upgrade and got a message that '2Wire is having technical difficulties'. I wonder if someone clued 2Wire in to the issue and they took the upgrade offline to debug it?

[Edit: I see someone has clued them in, but the upgrade apparently doesn't cause everyone problems]]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107776 Wed, 30 Sep 2009 13:59:35 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107571
May I ask the specifics on shipping the modem to 2Wire? Would you mind telling me how much will be your total cost and to what version they are re-flashing the modem? I have been considering sending one of my modems to 2Wire, as well, as I have two of the 2701HG-B modems. I hope these questions are not too personal; I would appreciate any information you may be able to provide for me, as attempting to reach "technical support" at 2Wire hasn't been successful. I emailed them last week and have failed to hear anything from them. Thank you, cowbert!

--Voltron]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107571 Wed, 30 Sep 2009 13:28:21 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107262 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107262 Wed, 30 Sep 2009 12:45:23 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107131
Since it looks like you can still access your UI, I would work with wayjac and start looking at logs...]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107131 Wed, 30 Sep 2009 12:23:57 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107053
In some respects, I was glad to read your post. I have been an elite AT&T DSL subscriber for over two years, using the 2Wire 2701HG-B gateway and have loved it. I have never had any problems. The modem came with and *was* running firmware version 5.29.47. Then, early Tuesday morning, between 3:00 AM and 5:00 AM, on September 22, 2009, I received my first and only firmware push-installation, upgrading my 2701HG-B to version 5.29.109.5. Since that installation, my wireless clients have been unable to connect to the gateway and my (download) speed has dropped by 50%! Other than that, the modem looked fine and the line was still provisioned for the elite speeds; AT&T claimed that things looked fine on their end, as well. A second installation of an identical 2701HG-B modem with firmware version 5.29.109.5 is also displaying the same wireless and speed-related issues. I am with you; all these problems started after the firmware update.

Has anyone else experienced such issues? Have you recently received a firmware update from AT&T? AT&T told me they started this update near the beginning of September and I am seeing many users frustrated with strange issues, mostly speed issues, that have appeared, suddenly. I live in Indiana and I can easily say that I have spent many hours troubleshooting this problem and so far, everything points back to the firmware update; nothing else has changed on my end.

Please, let's get as much information, as possible and let's see if *we* can troubleshoot this issue. Thanks!

--Voltron]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23107053 Wed, 30 Sep 2009 12:14:44 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083945 You did a very good job of troubleshooting

Its not any help but for a short time the default was 192.168.0.0]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083945 Fri, 25 Sep 2009 18:33:01 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083910 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083910 Fri, 25 Sep 2009 18:25:17 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083771 said by cowbert:

Because this particular 2700HG-B no longer services DNS, DHCP, or HTTP requests, and the reset button is not working properly
Your 2wire is useless you could ignore some issues but the reboot is too much to ignore
Factory reset in the gui or the button (press and release)]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083771 Fri, 25 Sep 2009 17:55:25 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083705 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083705 Fri, 25 Sep 2009 17:37:35 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083642 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083642 Fri, 25 Sep 2009 17:21:59 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083593
It is doing PPPoE correctly, and I can use it as an unmanaged network switch (at least until it reboots itself). After a reboot, it will resync to the dslam and I can get on the web and it will pull down at 6Mbps (Elite).

Everything would be fine except for the constant reboots (and the fact that I can no longer manage it, but my network topology hasn't changed in at least 6 months anyway).]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083593 Fri, 25 Sep 2009 17:10:26 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083588
I've never heard of a firmware update push via AT & T. That had never happened to me when running those 2 wire gateways. If you can't get the thing configured, I would spring for a Netopia modem, model no. 3347 ver. 2, which is used by the SBC Business Class. It is solid. In agreement with Dr Strange, the power supply on the 2700-2701 series do tend to have a short lifespan. They tend to give out a lot sooner than the gateway itself. ]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083588 Fri, 25 Sep 2009 17:09:21 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083513 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083513 Fri, 25 Sep 2009 16:52:12 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083419 Now having the modem just go bad/defective /down is a distinct probability if you are not getting any communication.
particularly if its self rebooting.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083419 Fri, 25 Sep 2009 16:36:10 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083307 can only resolve (i.e. work) IF the router is able to act as a DNS server, which mine can no longer do as of Thursday!

Furthermore, accessing the router through a brower can only work IF the router is actually listening to web browser requests which I have repeatedly said is also broken here (this is the 3rd time I am pointing this out, by the way).

Because this particular 2700HG-B no longer services DNS, DHCP, or HTTP requests, and the reset button is not working properly, I am hypothesizing that there is a major firmware problem with it. Since I have not changed any settings on this device since 2008, it means that it must have received a bad firmware update automatically from upstream.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083307 Fri, 25 Sep 2009 16:13:44 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083174 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23083174 Fri, 25 Sep 2009 15:49:42 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082879 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082879 Fri, 25 Sep 2009 15:02:12 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082857 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082857 Fri, 25 Sep 2009 14:58:56 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082787
Presumably hitting the reset button *should* have set everything back to 192.168.1.0/24 but it did not.]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082787 Fri, 25 Sep 2009 14:48:35 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082237
»2Wire 2701HG-B basic wireless setup]]> http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23082237 Fri, 25 Sep 2009 13:28:27 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23081796 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23081796 Fri, 25 Sep 2009 12:14:11 EDT http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23081769 http://www.dslreports.com/forum/Re-bad-new-2wire-firmware-push-23081769 Fri, 25 Sep 2009 12:07:32 EDT http://www.dslreports.com/forum/bad-new-2wire-firmware-push-23080119
2wire 2700HG-B self-reboots every 15-30 minutes

2700HG-B lost ability to hand out DHCP IPs (nothing listening on UDP 67)

2700HG-B does not start up its web interface either (port 80 closed). Standard nmap port scan of all ports in /etc/services shows nothing open...

Holding down the reset button for 10, 30, 60, 120 seconds (while 2wire is powered) doesn't perform a factory reset.

This is starting to smell like a bad firmware push (if those are actually done).

Is there another way to peform a factory reset if MDC is unreachble (since no server is running on port 80 on the device) and the button doesn't do anything? Hope it doesn't require a JTAG short.

At least a factory reset would let me login to the MDC and grab some line data...]]> http://www.dslreports.com/forum/bad-new-2wire-firmware-push-23080119 Fri, 25 Sep 2009 01:51:05 EDT