During Setup, once the Gateway Puck is connected to your router it will display the WiFi icon.
In the next Setup step the Gateway will attempt to communicate with the Flair servers. You'll see this screen:
In some cases, a router might not permit the Gateway to communicate with the Flair servers. This could happen for a few reasons:
- Router security settings are preventing the Puck from connecting to the internet
- The DNS server is preventing a connection to the Flair servers
- The router needs a firmware update
Please check your router's settings to see if there are any security settings that are preventing a connection from the Puck to the Flair's servers. The Puck's MAC address is found in the Puck's Status menu.
Remove/Disable Advanced Router Security Settings
If you have advanced security settings set up on your router, remove or disable them.
Try Using a Guest Network
If you don't want to alter security settings on your home WiFi network, you can set up a guest network with reduced security settings and attempt to connect the Gateway Puck(s) to that network. You'll need to do a "Forget WiFi" on the Puck prior to trying Setup again.
Try Updating the Router Firmware
Check to see if a firmware update is available for your router. If so, install the update, go into the Puck’s Settings menu and do a “Forget WiFi”, and then retry WiFi set up.
Test Access to Flair Servers
Try the following to test to see if your router's DNS server is allowing a connection to the Flair servers.
- Open a terminal window on your computer and issue the following command. The command can be entered on any type of operating system (Windows, Mac, Unix, etc).
- You should see something like the following if the nslookup is successful:
- If you see something like this ("Server: Unknown"), then there's an issue with DNS lookup.
- If the DNS Lookup above failed please issue the following command. This pings Google’s DNS server.
- If the ping is successful, you’ll need to change your router's default DNS server to 188.8.131.52 (Google's DNS server).
- If the ping replies with an IPv6 address (example in image below), no packets received, or other issue, it's probably because IPv4 has been disabled. You’ll need to enable IPv4 in your router settings.