current firmware version of the bgw210-700?

I have been experiencing similar issues with my 5 year old BGW210-700 since 12/12/2022.  I know this because I was bypassing the gateway altogether until that time. It appears my market (Cumming, GA) had the fiber infrastructure upgrades to support XGS-PON. This has been a rolling upgrade across the country. When this happened, my bypass method stopped working as the bypass scripts were not interpreting the new management certs.

None of that matters as it pertains to your issue except what a personal friend and AT&T tech told me today when I called him. AT&T knows that the older versions of the BGW210-700 have a hardware issue with XGS-PON at certain firmware releases, including all the latest releases. Newer version of the hardware versions of the 210's seemingly work just fine. Armed with this info I called AT&T today, was escalated up to another tech that admitted almost as much on my call. He offered to replace my BGW210 with another but he said it was a shot in the dark if I would get an older model or a newer model as all of them are refurbs at this point.

So they offered me a gift card for my troubles and if I upgraded to 2gig service would ship me out a 320 and a tech to make the adjustments. The gift card will cover the increase in cost for 6 months and then I will decide if I will change my infrastructure to support the faster speed. I really don't need faster speed, but I do need consistent internet as I work from home.

Nacman- I *just* got my router replacement tonight- it was dated manufactured 12/22. Not bad at all. I installed and will see what happens.

And to clarify- I believe the 12/22 was likely a refurb date. Just my guess.

@pdhaudio83 Good to know, i might have rolled the dice if I new there were current hardware versions that new.  Do you mind posting the hardware version of the new 210 you got when you have a chance to look it up? You will see below the hardware version from mine. Also this cut n paste was the firmware version it was at when I was in bypass mode and not using the gateway at all. It never upgraded cause it wasn't connected :) - Now it is at 3.18.5 I think,

@Nacman 

So they offered me a gift card for my troubles and if I upgraded to 2gig service would ship me out a 320 and a tech to make the adjustments.

They will not ship you a BGW320 to replace a BGW210-700. The phone customer service rep as no control over the shipment process regardless if they add notes to your account. The pull sheet in the warehouse will just be another BGW210-700 for a self-service install. Yes it most likely be a reconditioned unit. as the First Use Date indicates.

You need a tech to install a BGW320 and activate the internal SoC ONT since AT&T procedure is to primarily reserve BGW320s for Fiber 2000 and Fiber 5000 in most markets due to supply chain shortage. Yes a tech may install a BGW320 and use your existing standalone ONT but the tech will need a manager override.

Note: If you receive a BGW210-700 with an older version of Firmware is should update as soon as your connect it or within 24 hours to the latest Firmware 3.20.5

Dave

That is exactly why I upgraded my service to 2gig to get the 320. BTW, the 210 is now at the latest release, I got it overnight after a forced reset and the my service is still crap out of the back of it. Latency all over the place at it's worst I have seen 3000+ms to only be followed by 3 or 4ms a few minutes later. Speeds (Edited per community guidelines) too now at .9Mbs up and 40-60 down. Last month before X-PON roll out I was always between 940-960 synchronous and 2-3ms ALL THE TIME. Flying in my F-16 homebuilt cockpit with guys over in Europe is my relaxation, but since 12/12 I cant fly due to the terrible latency. 

I now understand that I may be able to go back to bypassing the new setup using a different approach than eap_proxy method I was using. With the number of NAT entries on my setup going through the 8192  limit regularly I think I will investigate removing that issue by bypassing again down the road

No one here should be fooled thinking they are getting new BGW210.  

As @dave006 points out, Att strictly controls firmware version on the device. 

I too have been experiencing random reboots. A few days ago I performed a factory reset.  Things are more stable but more time is needed to be certain.  These reboots appear to be recent as of latest update. 

My main concern at this point is user reports rebooting occurs even after a factory reset.  My service here is 100/20 copper. 

@dave006 - I rarely get on forums, just don't have the time or need until I get stumped. I was over at DSLR and was reading up on what I believe to be my future situation starting tomorrow with the ATT visit. I also assume you are one and the same Dave006 over there? You have a lot of good info after reading what I could this morning.

It looks like from your posts over there that I will not be able to bypass the 320 since I will be using the internal ONT on the 320GW.  So I plan to put it into IP-passthrough.  My issue is my fiber currently terminates on the second floor of my house and my entire system of servers and switchgear is in the basement. House is fed with 24 runs of CAT6 to anything that needs a connection. I only use Wifi for phones and laptops.

In my current setup, I run Cat6 out of the ONT to the basement into the 210GW.  My assumption is ATT will not move my fiber to the basement and I will need to have the 320 placed upstairs. I have 10GB switchgear I could use. 

I guess my question is since I will be paying for 2gig service what are my options, if any, to get that speed out of the 320 down to my infrastructure? I don't care to get 2gb to any one device, not needed, but the aggregate would be nice. 

I don't have any conduit in place between floors as I wired it just prior to sheetrocking it. If I could run fiber from the patch I understand they will install, what specs do I need on the type of fiber patch I would need? 

-Nac

Checking back in- so far with my refurb 210, I have not had downtime/reboot since I installed it. Going on 4 days without a reboot.