New firmware for Obi 200/202
IterationIsFailure:
Like many of you, I noticed my OBI202 update (without permission) earlier today to 3.2.1 (Build: 5794EX) contrary to having FW Updates disabled in the UI to prevent such behavior. Clearly, OBI like other companies nowadays seems to give two sh|ts about user trust and respecting settings.
After this fisaco, I even went as far to specifically "suspend" FW updates in the local box UI, which as you'll see, does jack to prevent updates. Perhaps this is more for user pacification than it being actual functional code.
That said, I updated sideways to OBi202-3-1-1-5794.fw from EX version, logged into the OBI website and was greeted with a yellow triangle indicating there was an update for my specific serial number and LOW AND BEHOLD... after agreeing (just to see the web UI disrespects the user settings), it pushed the EX version back to the unit.
So in conclusion, the settings inside the OBI local UI mean jack $hit with respect to disabling FW updates. Apparently OBI has a backdoor that allows them to command and conquer your unit as they see fit - including pushing FW updates, which if and when brick your unit, you're SOL if out of warranty.
Time to find out the server and DNS and blacklist at router level.
Almighty1:
The reason is that 3.2.1-5794EX does really exist at:
http://fw.obihai.com/OBi202-3-2-1-5794EX.fw
I noticed the EX versions are always 3.2.1 while the none EX versions are always 3.1.1
IterationIsFailure:
Quote from: Almighty1 on January 21, 2018, 05:26:30 pm
The reason is that 3.2.1-5794EX does really exist at:
http://fw.obihai.com/OBi202-3-2-1-5794EX.fw
I noticed the EX versions are always 3.2.1 while the none EX versions are always 3.1.1
Interesting point. I wasn't aware there is an offset. That is good know.
So, I disabled OBiTALK in "OBiTALK Service Settings" and the unit now shows as "Offline" on the Obi website, but unsure what consequential problems I'll run into, such as the Google Voice configuration, which I recall having to do via the OBI website.
I pulled DNS calls from the OBI. It contacts fw.obihai.com, which seems to indicate that is choke point to block. Time to test, ;D
WelshPaul:
Quote from: GPz1100 on January 21, 2018, 06:44:59 am
Paul, you have a change log for either of the last 2 firmware updates?
Nope, can't find any release notes on the server for these builds. Not sure if it's because Polycom are taking over and things are no longer a priority, or if it's due to the OBi100 series firmware patch and that OBIHAI don't want to announce that they have fixed that issue in these releases.
It could also be that OBIHAI changed their file name structure and I just haven't found it.
ProfTech:
FWIW, I haven't seen any problems with my 200 due to or during either one of these updates. I even uncovered a fix for an anomaly with TLS I wasn't aware of. But then maybe I was one of the lucky ones that hasn't been bricked.
Navigation
[0] Message Index
[#] Next page
[*] Previous page