Problems with initial connection to Wi-Fi network
Dave Peterson
via web
I successfully connected to the ad-hoc network from a laptop, but I don't believe the UFO ever restarted after I entered my Wi-Fi network information. Now it is not on the Wi-Fi network and I cannot get it to show on a Devices list for the ad-hoc network. I have unplugged and replugged a couple of times and it goes through the light pattern of steady, blinking, then steady again, but no way to reach the ad-hoc network.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by emile on 19 Feb, 2012 11:27 PM
Since the WiFi configuration has been entered, it is plausible that when power cycled the UFO is attempting to connect to the configured access point. The top LED starts blinking about 20 second after the UFO is plugged in. If the LED stops blinking like in your case, it means the association to the WiFi router has completed successfully. That is probably why you cannot see it as ad-hoc device anymore. The only case when the UFO top green LED shows successful connection but the UFO is not accessible from an iPhone or iPad connected to the same network, is because of a problem with the DHCP. What router (brand/model) do you have and are you using a special DHCP server?
3 Posted by Dave Peterson on 19 Feb, 2012 11:35 PM
I have the iPad app, and have tried using it, but it says "No devices found in your local Wi-Fi network". My router is an Apple Airport Extreme, model number A1301. No special DHCP configurations that I know of.
Support Staff 4 Posted by emile on 19 Feb, 2012 11:42 PM
We are testing regularly with several models of Airport and the only known problem is when using the "Extending the Network" setting with Airport hardware version 1. If that is the case let me know.
We had at some point a problem with units configured with a wrong password that exhibited a behavior similar to the one you described. I cannot say for sure because it is not clear whether the UFO you have has timed out after about four minutes of trying to connect or not. To force the UFO to start in ad-hoc mode regardless, since there is not reset button, follow this procedure: 1) plug-in the UFO and wait for top LED to turn steady on (about 4-5 seconds) and unplug; 2) plug-in again and wait for top LED to turn steady on (about 4-5 seconds) and unplug; 3) when plugged in the third time in this sequence, it will ignore any WiFi configuration and go straight into ad-hoc mode.
Hope this helps.
5 Posted by Dave Peterson on 20 Feb, 2012 01:00 AM
I went through the manual reset described, and I believe I have successfully entered my network information. The light is a steady green, but it still does not show up on the app for iPhone or iPad. I checked Airport settings and don't see anything that would indicate I'm using "Extending the Network".
Support Staff 6 Posted by emile on 20 Feb, 2012 07:59 PM
Please confirm that after startup the top LED is blinking for some time and then it becomes steady green. If this is the case, the UFO has connected to the Airport. It may not have acquired the IP address correctly because otherwise it would be accessible with the iPad. The "Extend the Network" would be useful only if you have multiple Airports.
If instead the top LED is steady green without blinking, the unit is damaged and we need to send you a replacement.
Please confirm which is your case.
7 Posted by Dave Peterson on 20 Feb, 2012 08:07 PM
After doing the unplug-replug sequence to reset, it showed up as an ad-hoc network again, but the light was blinking yellow. It continued to blink yellow until I entered network information and clicked OK on the dialogue box. It then restarted, blinked green for a few seconds, then went to a steady green. This all looks correct on the UFO side, but it can't be found by the iPad or iPhone apps.
Support Staff 8 Posted by emile on 20 Feb, 2012 08:15 PM
Can you please let us know the firmware version on your Airport? It appears the UFO is not getting an IP address from the Airport DHCP. Also, it could be useful to check on the Airport log if this is the case. You should be able to see on the log the event of the UFO associating but not in the DHCP table. The UFO WiFi MAC address starts with 00:02:72.
Thank you.
9 Posted by Dave Peterson on 20 Feb, 2012 09:00 PM
My firmware is version 7.6.1. I cannot find the Airport log - Apple seems to have hidden it quite effectively.
Support Staff 10 Posted by emile on 20 Feb, 2012 10:19 PM
I just completed a successful connection of a UFO with the Airport Extreme 1st generation A1143 at the office, firmware 7.6.1. A video capture of an Airport utility session showing the settings used is at:
http://...mov
Please check if you notice some relevant difference in the settings. Wireless Security, Radio Mode, and Access Control are probably the most relevant.
We have another Airport Extreme at an outside testing site. i am waiting to hear confirmation of their model number A1354.
Support Staff 11 Posted by emile on 21 Feb, 2012 07:21 PM
I have received confirmation that the Airport used in our outside test site with ten of our products, is an Airport A1301, that is the same you are using. I have personally attended the setup of those units and I confirm they connected right away without a glitch. I am not sure it is relevant, but the complete model number is AirPort Extreme
BCGA1301 IC-579C-A1301.
It is possible you have a defective UFO. Would you have the chance to try it with another router?
Support Staff 12 Posted by marco on 22 Feb, 2012 05:18 PM
I am closing this ticket as solved. The issue was related to connecting the UFO to the Airport "guest" network. Clients on the "guest" network cannot "see" any of the devices on the "private" network. For the UFO to work with the iPad and iPhone app, the network must allow for broadcast UDP messages and it appears that the router blocks these packets for the guest network.
When connecting the UFO to the Airport "guest" network, on the Airport, the "Allow guest network clients to communicate with each other" option under the Guest Network tab must be enabled.
marco closed this discussion on 22 Feb, 2012 05:18 PM.