Announcements
Don’t miss your chance to add AT&T Protect Advantage. Peace of mind, starting at $15 per month. Open enrollment ends 3/31. See all protection plans.
Astrum

Contributor

 • 

15 Messages

Fri, Jan 17, 2020 1:20 AM

BGW security issue (?) not prompting access code (even on changes)

Got a BGW210-700 with a fiber 1000 connection.

First thing I did was change the access code via the IP.

I’ve not been prompted to enter access code since (aside from one random prompt.)

My 5268 used to prompt me often... on every single change, even during the same session.

I can’t even force the BGW to prompt for the access code no matter what I do. (Changed Access Code (again), Closed windows, cleared cookies, ‘forget network’, then reconnect, changed WiFi PWs etc... even used different browsers.)

Remote access is disabled.

It would seem that anyone that is on the network even just once can make any changes they wish.

This can’t be how it’s supposed to work, as even on the access code page itself, it warns that further changes will require it, ‘so you better not lose it.’

Cannot figure this one out.

Thanks in advance!

Manufacturer ARRIS

Model Number BGW210-700

Software Version 1.6.7

First Use Date 2020/01/16 19:10:03

Time Since Last Reboot 00:05:08:13

Current Date/Time 2020-01-16T20:11:33

Datapump Version A2pvbJ042w.d26r

Hardware Version 02001C0046004D

Responses

Transponder

ACE - Scholar

 • 

346 Messages

4 weeks ago

Well, for one thing your firmware on the 210 is about 7 versions out of date. The latest is 2.5.6. Not sure why because ATT actively pushes the latest firmware. The version you have is very buggy. You can find the latest to download over on dslreports. com or call ATT and they can remotely push it to your gateway.

And I think for most settings ATT assumes that devices on the local ethernet network are authorized and wifi clients need to have the wifi password to connect. Not saying that is the best way to handle it though. My experience in the past is that most settings can be changed but a few do require the access code.

Award for Community Excellence 2019 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Astrum

Contributor

 • 

15 Messages

Install tech expressed layers of surprise when the firmware didn’t update. He assumed it was up to date. (Therefor, so did I)

Maybe it’s waiting for idle devices and no U-verse TV DVR action to do its thing.

I’ll get it off DSL reports and see if that works.

Thx!

Astrum

Contributor

 • 

15 Messages

I dl the .bin and it will not update.

I restarted the gateway and disconnected all devices. Tried again using a lan connection...

The update button also isn’t initiating the gateway to restart either (which per the grey help menu states it should.)

I browse to the file, open, click update, and all I get is the blue status bar and crickets.

tonydi

Guru

 • 

532 Messages

It may be that it won't update from that old of a firmware directly to the latest. You might need to try a FW close to the one you have to see if it will install and then you can jump to the current one in a few steps.

It isn't the first time I've seen someone who has been unable to update FW, though. One time the user did a factory reset and that solved the issue.

OR, given the nature of the QC with these gateways, it could just be a bad unit.

Astrum

Contributor

 • 

15 Messages

So this is getting strange.

I found the error in the logs that said the file size was too large.

I did a factory reset.

Then, I was pushed to 2.4.4

So I thought that’s good.

But when trying to do the latest firmware version, I’m now getting a new error.

I’m on my phone now so I don’t have the exact error, but it was along the lines of “DefferedUpdate enabled cannot update from WEBUI”

It was in red text at the top of the screen.

But now my logs have disappeared!

All that’s showing up are firewall logs now.

Missing is everything else, along with the drop down that allowed you to filter the log types.

I guess the firmware update took that away because the whole page looks different.

Does it reappear in the latest update?

I’ve been fiddling with this for over 10 hours now.

Enlightening.

tonydi

Guru

 • 

532 Messages

That message means AT&T has stopped you from doing a manual FW update. There must be some sort of mechanism that sets that flag right after an update since I've only seen this when someone gets an update and then tries to do another in short order. I don't know if the flag gets removed after some period of time or what.

That being said, there doesn't appear to be anything in 2.5.6 that is worth messing with. People who had issues on 2.4.4 still have the same ones on 2.5.6 and people who had no issues didn't find any new ones.

Transponder

ACE - Scholar

 • 

346 Messages

If you haven't done a factory reset after the 2.4.4 upgrade, I would do that. It's not always required after a firmware update but it often helps.

Award for Community Excellence 2019 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
tonydi

Guru

 • 

532 Messages

I suggested that and he already did it. But you couldn't easily see that because this $*^%#&$#&$# forum update that AT&T did loves to hide certain replies in the thread.

Astrum

Contributor

 • 

15 Messages

Wow, that’s strange the replies disappeared. How do they decide which replies to 86?

In any event, is there a way to get my logs back?

As I said in another reply, all that remains on the log page post-update are firewall logs.

L2, L3, etc are all missing.

In fact, the entire page looks to have been redesigned specifically to only show firewall logs.

I used to get a page that was halved with a side-scroll that allowed viewing long log lines.

Now, it looks like an excel spreadsheet.

Thank you all!

Edit: clarity.

(edited)

tonydi

Guru

 • 

532 Messages

They don't delete the replies, they just "hide" them behind a link that says 'View previous replies'. But it's really random and easy to miss when you're scrolling down a long list of replies.

As far as the logging, just like with all of the other horrible choices they've made with these gateways, no way to tell what was in their heads when they made this change to the logs.

Astrum

Contributor

 • 

15 Messages

Oh wow, they hid logs on purpose? And they’re even gone from the latest update?

That is crazy to me, as the only users using the IP to access the router are likely people who’ve been doing things that way for years, and have the ability to understand logs... or at least find places like this on their own without bothering ATT TS.

My first thought is it confuses people... but the people most likely to be confused are using the app to manage their network and wouldn’t see the logs anyways.

It’s almost like they’re daring people to use a dumb switch to take the gateway out of the picture entirely— thus relieving ATT of all responsibility for support.

That’d be some next level 3D chess :)

More than likely they are hiding some tracking activity or some such stuff that wouldn’t be popular with privacy advocates.

Hmm.

(edited)

tonydi

Guru

 • 

532 Messages

Well, they aren't "hiding" logs and in fact, I'm taking your word for what the logs used to look like. I don't have examples of any logs earlier than what 2.4.4 has. Whatever difference there is has to be intentional.

And to be clear, they don't want people to bypass the gateway and apparently they've said so in their TOS although I've yet to find where. The lack of ability to do things like collect data is a good possibility for why they want their equipment in place.

(edited)

Astrum

Contributor

 • 

15 Messages

Example of the (useful) logs I downloaded before they changed it to firewall only (which is not at all relevant to troubleshooting.)

(edited)