
New Member
•
10 Messages
current firmware version of the bgw210-700?
1. What is the current firmware version of the bgw210-700?
2. And how often does this update to a new version?
3. I keep seeing my modem reboot itself every day or two. Could a firmare update be causing this?
pdhaudio83
New Member
•
20 Messages
4 months ago
so my "newish" 210 finally upgraded itself to 3.20.5, and surprisingly shows it hasn't rebooted in over 9 days. anyone else that's seeing improvement?
0
0
mdreinders
New Member
•
16 Messages
4 months ago
All right. Because there is so little left to do, the tech this afternoon switched me to another fiber port across the street. Again, this is fiber so, it's up or it's down. But at least they are trying.
The only other thing he mentioned is that my CO does have 10Gbps capability. OMG. Really? I don't even think that's live on the AT&T website to upgrade to. But it's an option. Crazy speeds.
I'm just hoping my connection stabilizes. I would gladly welcome pdhaudio83's 9 days of uptime. ;)
- Michael
0
0
JefferMC
ACE - Expert
•
32.3K Messages
4 months ago
The "X" in "XGS-PON" stands for 10. The "G" for Gigabit. The "S" for symmetric. Everywhere that XGS-PON has rolled out has 10 Gbps capability, even though AT&T is only selling 2 Gbps and 5 Gbps at the moment.
0
0
Nickzel
New Member
•
5 Messages
4 months ago
Well my "new" 210 has rebooted 4 times in the last 5 days.
0
0
pdhaudio83
New Member
•
20 Messages
4 months ago
What is your datapump version (system info?) I noticed that mine is newer than when I initially had problems (.d27n now vs .d27j earlier)
0
0
mdreinders
New Member
•
16 Messages
4 months ago
Well, oh well. :(
About 5 minutes after I started up my computer to start work for the day...another reboot. Just odd behavior. This makes me believe there is SOMETHING on my computer causing this. But, again, I do very similar things every day and this only happens about every other day or so.
At this point, there's no point in engaging support...there's nothing else they can do. For now, I will live with it. Hopefully, a firmware update will be released that resolves this. However, we have no evidence that the code on BOTH the 210 and 320 has this issue.
And the troubleshooting flowchart here doesn't make sense with the hypotheses I just mentioned as others across the country are seeing the same behavior and are not using the same hardware and software on my computer as me. :)
So, I'll update this thread as news warrants. I will try not to spam too much. ;)
Thanks, everyone for their help.
- Michael
0
0
JefferMC
ACE - Expert
•
32.3K Messages
4 months ago
Based on the scattered reports of issues from people who have the BGW210 and BGW320, the new firmware and are, or are not, having issues, the following areas have been standing out:
1) People who use Passthrough (and thus likely have Wi-Fi turned off) are not having issues
2) People who turn off IPv6 seem to not have the issues.
I have a 210 at 3.20.5 and no issues. I have IP Passthrough, don't use the Wi-Fi and have IPv6 turned off.
I would suggest that if you do have IPv6 turned on, and don't have to have it, turn it off and see what happens. Report back with success or failure.
[It empirically makes sense that it's a Wi-Fi issue, but I've seen two reports that turning off IPv6 fixed this issue for that user. It may be something else entirely. But the more we can find out about the problem, the more likely it is we can get AT&T to fix it.]
0
0
pdhaudio83
New Member
•
20 Messages
4 months ago
I'll reiterate that nothing has changed on my setup/wifi/computers at all since the daily reboots, EXCEPT... datapump versions is now .d27n instead of the old .d27j that the older boxes (that rebooted daily) had.
0
0
JefferMC
ACE - Expert
•
32.3K Messages
4 months ago
@pdhaudio83 Aren't you fiber? The datapump versioning is for code related to DSL processing. I'm also surprised that would change without an overall version change.
0
0
pdhaudio83
New Member
•
20 Messages
4 months ago
yes I am Fiber- 1G. And while I don't know that datapump is (seems related to Oracle), that's the *only* thing that has changed in the recent days, so I can only assume either improvement there or magically the issue stopped here in Chicago
0
0