4 edits |
[Firmware] SBG6580 new firmware SBG6580-8.5.0.0-GA-05-15-NOSH *Breaks SBGs*The interface is soo much better now, new option for the wireless (can select G/N, no need for B). Users who have received this firmware update report issues staying connected. Their sbg6580 freezes after 15-30 minutes! See also ---> » yeah |
|
|
Re: SBG6580 new Comcast firmware :) SBG6580-8.5.0.0-GA-05-15-NOSHApparently this new firmware release also fixes the "Access Denied" problem: » Re: [Equip] sbg6580 "Access Denied" |
|
|
Lucky1345 to evox2008
Anon
2013-Dec-12 5:03 pm
to evox2008
Switching to G/N mode runs the wireless OK for a few mins, then the connection drops. I can still see my wireless network but cannot connect to it. Also, when hard wired, I get 169.254 ip address after another reboot, wifi runs for a few mins and drops again... endless loop Can anyone confirm this? |
|
|
How many wireless/guest wireless networks can you have at once with this new firmware? |
|
|
MI Trouble to Lucky1345
Anon
2013-Dec-12 6:59 pm
to Lucky1345
I am having the same trouble, just started two nights ago. Just now see they upgraded me and could be the problem. |
|
|
to Darknessfall
said by Darknessfall:How many wireless/guest wireless networks can you have at once with this new firmware? 2, one primary and 1 guest. |
|
|
DanM64 join:2013-01-10 Mokena, IL
1 recommendation |
to evox2008
Re: [Firmware] SBG6580 new Comcast firmware :) SBG6580-8.5.0.0-GA-05-15-NOSHGlad they finally fixed the IPv6 hangup problem. This was a long overdue update!
Is the sbg6580 IPv6 capable now? |
|
your moderator at work
hidden : Friendly delete
|
|
to DanM64
Re: [Firmware] SBG6580 new Comcast firmware :) SBG6580-8.5.0.0-GA-05-15-NOSHsaid by DanM64:Is the sbg6580 IPv6 capable now? It still looks disabled. Everything in the UI only mentions IPv4, and there's this message in the logs: Overriding MDD IP initialization parameters; IP provisioning mode = IPv4 |
|
|
Eric859 to Lucky1345
Anon
2013-Dec-13 2:25 pm
to Lucky1345
Re: SBG6580 new Comcast firmware :) SBG6580-8.5.0.0-GA-05-15-NOSHI can confirm the outages with the new firmware. I've been having loss of connectivity issues for 3 days now. |
|
netcool Premium Member join:2008-11-05 Englewood, CO |
netcool
Premium Member
2013-Dec-13 2:57 pm
said by Eric859 :I can confirm the outages with the new firmware. Can you try a factory reset? This should not cause issues now but will erase all your stored settings. |
|
|
to evox2008
Re: [Firmware] SBG6580 new Comcast firmware :) SBG6580-8.5.0.0-GA-05-15-NOSHI am having problems as well. I can connect via Ethernet, but as soon as I connect to wifi the modem freezes and I have to reboot. |
|
DanM64 join:2013-01-10 Mokena, IL |
to evox2008
I really like the new firmware! I have my WiFi set to b/g/n, and haven't had any problems with it hanging up at all. I also tried setting it to n only which works fine also. |
|
|
Talenus to evox2008
Anon
2013-Dec-14 5:05 am
to evox2008
This software caused my sbg6580 to freak out. I lost all wireless and couldn't get online wired. I put the modem in bridge mode and was able to connect hardwire, but no wireless access. Took it out of bridged mode and lost the ability to ID the network within windows and was stuck with a 169. IP.
I called comcast and asked for support. They advised me that they do not support 3rd party hardware. I pointed out that it was the software that comcast designed and implemented and they agreed. I asked them if your software breaks my hardware how is that the manufactures responsibility? The rep got into a broken loop about how he knows how frustrating it is and that I can call the manufacturer. I know it was software issue and after several factory resets I was finally able to get a stable connection. I had to re implement all of my custom settings which are the same now as they were before this "UPGRADE"...and now it works.
I used to work for comcast and I would never have guessed they would fall so far below their previous levels of customer service and integrity.
Long story shot...hit that reset button and then implement your settings again and it should work...the jerk on the phone wouldn't even acknowledge I had an issue, "I cant confirm your connectivity issue at this time". FAH! |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
|
NetFixer
Premium Member
2013-Dec-14 8:31 am
said by Talenus :I know it was software issue and after several factory resets I was finally able to get a stable connection. I had to re implement all of my custom settings which are the same now as they were before this "UPGRADE"...and now it works. That is a very common symptom for many resi/soho modem and router devices after a firmware upgrade. I have had to do the factory default reset and manual config with many different boxes from Cisco/Linksys, D-Link, Motorola, Netgear, et al. One of the reasons this can happen is because after a firmware upgrade, the config parameters may not be stored in the same physical memory locations (and/or the stored data format has changed), and the factory reset clears out what has become bogus information (which can in many cases interfere with normal operation). Some vendors are "nice" enough to do a forced factory default reset as part of the firmware upgrade, but usually the end-user is left hanging to sort things out on their own. |
|
jlivingood Premium Member join:2007-10-28 Philadelphia, PA |
to gruvii
said by gruvii:I am having problems as well. I can connect via Ethernet, but as soon as I connect to wifi the modem freezes and I have to reboot. What OS do you have? Where are you located (nearest major city)? What version of 802.11 are you using (a/b/g/n)? Are there other WiFi clients using the network as well? What SSID are you connecting to? Your private SSID or xfinitywifi SSID? |
|
1 recommendation |
I use Win8, Win7, 2 android phones (v. 2.3.7). I'm in northwest suburb of Detroit, MI. I set mine to G/N. When it's only 1 wireless client - it's better, it rarely freezes up. As soon as I enable the 2nd, my sbg freezes - have to reboot. Have done the factory defaults, same. I am using my private wi-fi at home. I wish I was on the old firmware.. I could deal with ip6 issues, but this makes me upset and frustrated |
|
|
Went through the same woes and gyrations already mentioned... but finally got things running again.
As far as I can tell it required some action from the Comcast end, because I was at this for many hours. At first they couldn't "see" the modem then I cycled power and they fiddled over there and said it was up even though I had the same symptoms... "call the manufacturer, etc. etc."
Good bye!
Tried another factory reset, waited a bit and magically this time it was up. Followed by manually setting up the config and such, of course.
Schmantzy admin pages now, but basically no Help anymore. Waiting to see how awful the new layout is to use on a tablet.
No new manual available that I can find, a pain with no online Help and rearranged screens. |
|
jlivingood Premium Member join:2007-10-28 Philadelphia, PA |
said by dilettante:Went through the same woes and gyrations already mentioned... but finally got things running again.
As far as I can tell it required some action from the Comcast end, because I was at this for many hours. At first they couldn't "see" the modem then I cycled power and they fiddled over there and said it was up even though I had the same symptoms... "call the manufacturer, etc. etc."
Good bye!
Tried another factory reset, waited a bit and magically this time it was up. Followed by manually setting up the config and such, of course.
Schmantzy admin pages now, but basically no Help anymore. Waiting to see how awful the new layout is to use on a tablet.
No new manual available that I can find, a pain with no online Help and rearranged screens. So you had the dropping issue and did a reset and now it is fine?? |
|
2 edits |
What I saw was that first my WiFi devices lost connectivity, then my hard-wired devices did. Could not get to the admin pages of the SBG, so tried cycling power and waiting for "normal" lights. Still no-go. Two hardwired devices did get 169.x.y.z addresses and could see each other through the SBG's switch. After a reset (pinhole on the back of the SBG) I saw that I got a 192.x.y.z on a hardwired Windows PC and a weather desktop gadget updated its display and WinUpdate started downloading. I was able to get to the SBG admin page logon and saw the new look and 2013 Copyright so I knew firmware had been pushed. Before I got a second chance at a logon (looking up the default credentials in the old manual) the SBG admin pages were dead again. At no time did any of my WiFi devices ever get connected but then again everything was back to factory settings so of course they failed authentication. Fiddled with this a couple of times, scratched my head, and one time got logged on to the admin pages and checked the Status page and everything was reported as online... but I could never even get to a Google home page before it all fell over again. Drove around to some open WiFi hotspots with an Android tablet to get online and try to determine whether we had a local service outage. This process could easily be a whole ton easier, a small web page accepting a Zip Code and reporting back known status in the area would be a lovely thing to have. Some of the hotspots would connect but had no Internet access so I almost concluded they were on Comcast themselves and we had a local service outage... still no idea what that was about. Went to bed. Next day same thing yet. Decided to go out and shovel snow. Still no go. Called Comcast for assistance, and the automated thingy on the phone said it could not see my modem. Finally got a person who said it wasn't online, had me cycle power, then claimed to have reprovisioned it. Still no go. Conclusion "you'll have to call Motorola." Had him verify for me that he could now "see" the modem from his end before hanging up. Well, better than a truck roll at least. Cable TV working through the same cable the SBG normally uses so at least physical connectivity was intact. Got off the phone, tried another reset, still no go. Maybe 30 minutes later another pinhole reset, went to a hardwired PC, and saw "local connectivity" with a 192.x.y.z address but then gradually things began to wake up. Got to the SBG admin pages, logged on, reconfigured, logged off. Now saw WiFi devices get connected (as expected due to reconfig) and could get to the Internet. World saved! In the absence of detailed information and understanding... all I can imagine is that the reprovisioning was necessary and it took quite a while to "take." |
|
|
PeterM
Anon
2013-Dec-15 8:05 am
Just found out that my modem IP address changed from 98.x.y.z to 67.a.b.c This was the reason why I could not connect to my IP Camera. I also experienced wifi problems..... I have to reboot the cable modem to resolve problem. |
|
|
popol1234 to evox2008
Anon
2013-Dec-16 12:00 am
to evox2008
Re: [Firmware] SBG6580 new firmware SBG6580-8.5.0.0-GA-05-15-NOSH *Breaks SBGs*Same connectivity issues as reported above since the firmware change !
I have to reset my gateway every 15-30 min... what a nuisance !
Opened a ticket with Comcast tonight...
Did anyone found a fix for this ?
Thanks |
|
|
to evox2008
Hi guys, just as an update on my situation.
Every time I had an intermittent drop, I reset my modem.
After having done so 3-4 times, my connection seem to have stabilized. Also, I did call Comcast and ask them to reset the modem on their end, which they did.
I don't know if this helps, but I didn't change the SSID/password from the default.
And, my signal was set at 5GHz for some reason. I changed that to 2.4GHz. I left the rest unchanged.
Now, I don't have any issues. |
|
jlivingood Premium Member join:2007-10-28 Philadelphia, PA |
to evox2008
Due to ongoing issues with thus vendor firmware we are rolling back. If you reset your modem you should go back to the old version.
We believe the device vendor has enough data to understand the issue and work to resolve it soon, but while they do so it seems more prudent to temporarily roll back. |
|
|
popol1234
Anon
2013-Dec-16 7:05 pm
Quick Update:
I was surprised to see the old interface again earlier today (now back on sbg6580-6.5.0.0-GA-00-226-NOSH) but it took two other calls to Comcast which after hours of testing resetting and factory defaulting would not resolve the situation...(both concluded they wanted a tech to come out tomorrow despite my mentioning this whole firmware drama) but I now see that I am miracoulously back in business since about 1 hour... Will wait a little while more before cancelling the service call... |
|
DanM64 join:2013-01-10 Mokena, IL |
to jlivingood
Just curious- now that the firmware was rolled back, will the IPv6 connectivity issue with a factory reset be back?
Everyone may want to avoid using the factory reset button until the new firmware is reinstated!
Another thing I liked much better with the new firmware- now that we're back on the old, all 3 of my upstream channels show the same power level. The new firmware shows different power levels on each channel which is accurate. |
|
jlivingood Premium Member join:2007-10-28 Philadelphia, PA |
said by DanM64:Just curious- now that the firmware was rolled back, will the IPv6 connectivity issue with a factory reset be back?
Everyone may want to avoid using the factory reset button until the new firmware is reinstated!
Another thing I liked much better with the new firmware- now that we're back on the old, all 3 of my upstream channels show the same power level. The new firmware shows different power levels on each channel which is accurate. In that case try not to reset your device I guess! |
|
riffin1 join:2013-12-17 Saint Paul, MN |
to evox2008
Mine was working great, then the firmware was upgraded. Took about an hour to get the thing to work. When the firmware was rolled back the modem would not lock and go online. I can log into it. Devices will connect. No net. Any ideas? |
|
|
Yes, IM netcool your MAC and he will have you online. Your sbg is trying to get ipv6 address by default instead of the ipv4. |
|
|
i'm having the same issue. New registration so I can't IM yet. access denied. Is there another method of getting info to you? sbg6580-6.5.0.0-GA-00-226-NOSH Acquire Downstream Channel Locked Connectivity State In Progress Access Denied Boot State In Progress Unknown Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 105 561000000 Hz 6.3 dBmV 38.2 dB Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 Ksym/sec 15700000 Hz 39.7 dBmV |
|