Hello.
So I recently bought the OBI202. Turns out I got hardware version is 1.4 and software version 3.0.1 (Build: 3932).
It was easy to configure with two Google Voice numbers (phone & fax), and turned on AccessFromWAN. After confirming everything's okay, including accessing the OBI202 from the wired WAN port, I then plugged in the WiFi dongle and got that working. Again, I was successful accessing the OBI202 configuration from the (now WiFi'd) WAN port at the unique IP address it's getting from my DHCP lease server. I configured the DHCP lease server to always issue that MAC address that same IP address so it doesn't move around.
Fast forward to today. I am trying to get access to the OBI202 to "snapshot" my network equipment configurations. Nothing changed since I was last on the OBI202. In fact, nothing changed anywhere on that VLAN. The OBI202 had not even rebooted (it's on a UPS to protect it from power glitches).
Using
obitalk.com, I am successful getting into the Expert Mode configuration. I see the IP address is as I expected: what I assigned a couple weeks earlier. The box behaves correctly using
obitalk.com.
I confirmed from my router's DHCP lease server combined with my log files that there are no duplicate IP addresses on that VLAN.
I am about to save a copy of my configuration to my local computer. I can only do that from the OBI202 web server. So I type my IP address into my web browser and, lo, it fails. My web browser says the web page isn't there after a few seconds of "Waiting for web page to load".
Using ***0 and 30#, I determine that the OBI202 still says AccessFromWAN is enabled. I also see this on
obitalk.com.
I connect a straight-thru RJ45 cable from my computer to the OBI202 LAN port. My computer gets an IP address in the 192.168.10.0/24 network and I am successful getting access to the OBI202 web pages using 192.168.10.1. I disable AccessFromWAN and save that configuration. After disconnecting the RJ45 and getting back on this VLAN, I am unable to get to the OBI202 at port 80. I am not surprised.
I reconnect the RJ45 and re-enable AccessFromWAN; ***0 + 30# confirms that AccessFromWAN is enabled once again. I disconnect the RJ45, get back on my home VLAN, and try again to connect to my OBI202 network address at port 80. No joy in Mudville.
Why did my OBI202 decide, seemingly spontaneously, to refuse to obey AccessFromWAN? Anyone have a similar experience? How did you solve this?
Yes, I can connect my RJ45 and get access but that's not the way it's supposed to work.