AccessFromWAN being ignored by OBI202??
xzaphod:
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.
Shale:
Can you ping your OBi202? A subnet problem could give that kind of symptoms... make sure that the IP you hand out to the OBi is in the same subnet as the computer.
xzaphod:
Good point! I checked my router. Both clients (OBI202 & computer) are on the same VLAN, same subnet, and are using the same WLAN (wireless LAN) radio on my WiFi router. The subnet is a /24 with no further partitioning.
I ran Wireshark to watch the computer's network traffic. When I ping the OBI202, I see the computer sending multiple ARP (Address Resolution Protocol) "Who has <OBI202 IP address>?" requests on the VLAN but I don't see the OBI202 responding to that ARP request. There is a lot of other traffic on the wireless network interface: this is certainly working. Wireshark on my computer is limited in that it is not a full WiFi packet sniffer; I cannot see the OBI202 traffic with my router's radio, just what traffic would get back to my computer. [Perhaps time to get a WiFi packet sniffer?]
It would seem the OBI202 isn't responding to ARP requests when other devices on the OBI's network ask for its IP address. This would appear to be a change in the OBI202 behavior because a couple weeks ago I was successful configuring the OBI202 from its WAN interface.
Any suggestions?
QBZappy:
Quote from: xzaphod on June 02, 2013, 10:06:22 am
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.
At this point confirm the OBi ip by using the phone attached to the Obi. Dial ***1. Is it the ip address you expect? Can you successfully ping the address.
xzaphod:
The problem is averted! I'd like to say "solved" but I cannot make that claim.
Performing the diagnostics that led to my most recent post on this thread got me a-thinkin' about what might be happening on my home network. The home network is composed of multiple VLANs and multiple WLANs with multiple WiFi router radios broadcasting different SSIDs.
I remembered I'd set up another WLAN (SSID) on the same router radio that the OBI202 is using. This was for redundancy and not a vital component (at least not yet). So I turned off the broadcast of that SSID from that router's radio and, lo!, I could ping and connect to the OBI202 web interface. Woohoo! At least a little.
I have been trying to figure out why the OBI202 wouldn't respond to the ARP request when the router's radio is broadcasting two SSIDs (each with a different set of credentials). I don't understand enough of WiFi to develop a credible hypothesis.
Anyone able to proffer an explanation? I'm stumped.
Edit: The router radio was broadcasting two SSIDs on the same MAC address. With just one SSID on the MAC address, the OBI202 web interface seems to work.
Navigation
[0] Message Index
[#] Next page