Visitor
•
3 Messages
Arris SB8200 Events Log Web Page Bad HTML (Table Truncation)
FYI. There is a software defect in the Arris SB8200 software. If there are too many events logged, the html table definition containing the events in the Events Log webpage (cmevents.html), will be truncated within a row causing invalid html and a badly formatted and displayed webpage. Looks like the html table is constructed in a fixed length buffer resulting in truncation on overflow.
I tried to report this bug at ask.arris.com but they seem to be having issues with account management between ask.arris.com and commscope.com and I could not login.
Here are my versions and a screen capture.
Model: Arris SB8200
Hardware Version: 6
Software Version: AB01.02.053.01_112320_193.0A.NSH
Configuration File:d11_m_sb8200_extremespeed_c01.cm
[Image Removed: "Personal Information"]
EG
Expert
•
111.7K Messages
4 years ago
FWIW, Comcast is not responsible for any Arris firmware deficiency, nor can they do anything about it except maybe to pass it along to them. Good luck !
0
0
user_964a9e
Visitor
•
3 Messages
4 years ago
Yeah, I know. Posting here so others know why their modem event log web page looks like crap. I actually scrape the logs in Node-RED to save to a SQLite database for historical analysis and review but now have to deal with the invalid html. And rebooting doesn’t necessarily clear it up since the logs are in NVRAM and not deleted. The html shows a hidden form submit to clear the logs but I have not been able to successfully invoke it. This used to be exposed back before the move to user/pw authentication.
0
0
Andyross
Gold Problem Solver
•
8K Messages
4 years ago
The 8200's event log has always been an issue. Even worse, when it starts to get above a certain size it gets very slow to display. At some point, it will cause the web service to lock up totally and you have to reboot the modem. The modem itself will still work, but none of it's web pages will be accessible.
0
0
user_964a9e
Visitor
•
3 Messages
4 years ago
The UI will also lock up and stop accepting connections if there are more than a couple simultaneous unclosed logged-in sessions, as might happen with automated scripted access.
0
0