OBi202 new firmware?
meerkat:
The question is not how to use OBI as DHCP client (which is a default setting anyway), the need to use static IP is mostly used by power users to bind particularly device statically - printers, OBI box etc -- in order to facilitate setting up different firewall rules and to ease admin scripting.
OBI advertises and provides such static configuration setting. Yet their firmware squarely breaks this basic setting, in two consecutive ROM releases.
Agent88:
Quote from: wasagabeachvillage on August 01, 2013, 12:38:45 pm
what's new ? I'll tell you what's new ! The "latest" firmware (4041) just bricked my 202.
Thanks Sherm
Same here. What's up with this? Now I can't communicate with my Obi202 no matter what I do. [ignore]
Just noticed: FAQs no longer work. Has Obihai gone out of business?
FIXED!! Discovered my problem was my own making.... I have a USB Wi-Fi connection.... tried to update F/W via wi-fi.
Connected ethernet cable, rebooted 202 and everything back to normal. Even the previously reported f/w update fail was corrected without any more effort.
YongChen:
My (4109) upgrade:
It failed on the 1st try through obitalk.
It failed on the 1st try via ***6.
It went through on the 2nd try via ***6. It took about 3min. I can make calls with FPL and GV accounts.
No wifi, set DHCP on OBi202 (I dont use the router function on OBi202). The ip of OBi202 is static.
Maxxodd:
Are there changelogs listed somewhere for the newest firmwares?
TheDreamer:
I hadn't seen this thread when I was trying to update....
For some reason today, I visited obitalk...and saw that both my 110 and 202 were in need of updates. I tried the 202 first, it failed via obitalk. Tried again, still no go. Started looking around on alternatives.
Ended up trying through the web interface, except I was on my 110 because I wanted to move where syslog was going to. Also updated it to use local ntp servers, instead of pool.ntp.org.
had to reboot before I could do firmware update, then did firmware update.
No problems that I can see with that.
So, I then went to my 202, moved its syslog, had already changed it to use local ntp, except that I had moved my local ntp servers so updated that too.
It didn't say that it required a reboot after I made those changes, could see syslog output at new location immediately after I had submitted the change. But, I rebooted the 202 first, and then did the firmware update.
Things looked alright, shows version 3.0.1 (4109), except the interface shows "reboot required". So, I rebooted again. It still says "reboot required".
Didn't see anything about this on the new firmware post, wonder what's changed....
GV is working, I had deleted sipgate as SP2 a couple of weeks ago (don't recall which device needed update when I had visited then, but it was only one of them and it updated successfully via obitalk
Can't tell why its saying reboot required...
Noticed that both "reboot required" and "config current" are accessed as "./caution.png"....
The Dreamer
Navigation
[0] Message Index
[#] Next page
[*] Previous page