Monday, October 18, 2021 8:34:05 PM

Connecting G-3 series to internet using WiFi

8 years ago
#32 Quote
1.  Connecting and logging in using LAN
  a.  power on gateway and wait for "Internet" LED to stop blinking
  b.  Connect G-3 Gateway's WAN/LAN port to your PC's Ethernet port using Ethernet cable.  Verify "WAN/LAN" LED is now on.
  c.  open web browser on your PC and enter "http://10.168.1.98" (without quotes) in the address field

2.  Connecting and logging in using WiFi
  a.  power on gateway and wait for "Internet" LED to stop blinking
  b.  on your WiFi enabled device scan for and connect to the omnisense_xxxxxxxx wifi network.  Ignore warnings that there may be no internet connectivity.  Tap on the connection name and then tap "manage router".  If that does not work try opening a web browser enter "http://192.168.88.1" (without quotes) in the address field

3.  You should now see a login page prompting for username and password.  Use the default username and password from the label on the bottom of the gateway.

4.  Enable WiFi
  a.  Mouse over the "Network" drop down menu and click on "WiFi"
  b.  click "Scan" and you should see a list of available wireless networks
  c.  Click "Join Network" for the network you wish to join
  d.  If the network you are joining uses wireless security then on the next page " Join Network: Settings" enter the "WPA passphrase" then click "Submit".
  e.  On the next page scroll down to bottom and click "Save & Apply"
  f.  The WiFi LED should now be on or blinking, and after a delay of up to 2 minutes the Internet LED should come on.

READ THIS IF YOU ARE USING WIFI (STEP 2 ABOVE) TO CONNECT TO THE GATEWAY  !!VERY IMPORTANT!!
After step 4.e above where you clicked "save and apply" your laptop's wifi connection to the gateway will likely be disconnected which will make the gateway think "these changes are bad, they caused the laptop to be disconnected" and the changes will be "rolled back".  You will see a message that says "Failed to confirm apply within 30s, waiting for rollback...".  This is a safety feature meant to prevent you from making a change that prevents future access to the gateway but in this case you need to override the rollback.  To do this you need to reconnect your laptop's wifi to the gateway using step 2.b above and you should then see in the same browser window you used to "apply the changes" a popup with a red button that says "Apply Unchecked" which is geek for "make the changes anyways, damn the consequences".  Click on that red "apply unchecked" button and you will force the changes to be saved.  

Final note - If you really did screw up and the changes really are bad you can always recover with a factory reset by holding down the reset button for at least 15 seconds until all the LEDs go on then all go off except for power after which you can release the reset button.
0
8 years ago
#62 Quote
Known limitations and bugs:

1. If you configure a WiFi client connection and for whatever reason (typically incorrect password/key or not near the WiFi network in question) the gateway cannot connect as a client to that WiFi network the gateway will disable its own WiFi Access Point (AP) mode of operation.  In other words you won’t see it anymore, forever, unless you disable or delete the offending client connection.  The reason is that the radio is continuously scanning trying to connect as a client and while it scans as a client it cannot function as an Access Point.
  a. One workaround is to reset to factory defaults by holding down the reset button for ~15 seconds.  This should wipe out the configured WiFi client settings and allow normal WiFi AP functionality after the unit reboots.
  b. Another workaround is to connect by wired Ethernet and delete the offending client connection.

2. When you scan for available WiFi networks or enable or disable a WiFi connection that causes the radio to be restarted and will cause any connected devices to drop their WiFi connection.  For many devices including Windows 7 and iOS you have to configure the interface to automatically reconnect OR you will have to manually reconnect.  Even if you configure automatic connection you may still have to manually refresh the web page to see the changes that have been applied.

Item 1 above is less than ideal but stems from the fact we are stretching the limits of the WiFi asking it to act concurrently as both a client and a AP.  While we could detect the repeated failing attempts to connect as a WiFi client and disable that connection it would cause problems for situations where users have correctly configured a WiFi client connection and for whatever reason the connection is temporarily interrupted.  In other words there is not good way to distinguish one scenario from the other.

0