NOTE: Facebook has discontinued Facebook WiFi. It will no longer be available after June 12, 2023. NETGEAR recommends that you choose an alternative captive portal option on your wireless access point.
In firmware release 3.7.10.0 we have introduced Facebook Wi-Fi on WAC720 & WAC730 model access points. This is an authentication method which redirects Wi-Fi clients to your chosen Facebook business page upon trying to join your wireless network. The Wi-Fi client is required to check in to the Facebook page or supply a passcode, which authenticates them to the wireless network.
The following steps outline how to enable, configure and apply Facebook Wi-Fi.
Enable Facebook Wi-Fi.
Facebook Wi-Fi is a Captive Portal, to use it, global Captive Portal Mode must be enabled as well as Facebook Wi-Fi.
1. Login to your access points admin page and navigate to Configuration > Captive Portal > Captive Portal.
2. Select Enable for Captive Portal Mode.
3. On the same page, select Yes for Register with Facebook Wi-Fi.
4. Click Apply.
Configure a Captive Portal Profile for Facebook Wi-Fi.
There are two Captive Portal profiles available on your access point, proceed to edit one and attach your Facebook business page to it.
5. Navigate to Configuration > Captive Portal > Profile Settings.
6. Choose either of the two Profile Name radio buttons, and click Edit.
7. In the Edit Profile Settings page, change Authentication Mode to Facebook Wi-Fi.
Session Timeout value on this page overrides the value configured on the Facebook Wi-Fi Configuration page.
8. Click Add Page, then click OK to confirm the redirect. The Facebook Wi-Fi Configuration page is presented. If you are not currently signed into Facebook, you are required to sign in to proceed.
9. The following settings are required for configuration;
- Facebook page: Select your Facebook business page. You are required to login to the Facebook account.
- Bypass Mode: Allows Wi-Fi clients to skip the check in process by providing a Skip check-in link or using Require Wi-Fi code, the code is defined here, and each Wi-Fi client is required to enter it to access the Wi-Fi network.
- Session Length: Select the length of time the Wi-Fi client will have Wi-Fi after they check in.
- Terms of Service: Optional. You may add your own Terms of Service.
10. Click Save Settings, and close the page to return to the Edit Profile Settings page.
11. The Profile Name must be enabled to use it on a wireless network, if not done so already, select the Admin Mode check box.
12. Click Apply.
Apply Facebook Wi-Fi to a wireless network (SSID).
13. Navigate to Configuration > Security > Profile Settings.
14. Choose a Profile you wish to apply Facebook Wi-Fi to, by selecting the radio button, then click Edit.
15. If you have not already configured your Security profile settings, please do so now.
- Wireless Network Name (SSID): This is the wireless network name broadcast to Wi-Fi clients.
- Broadcast Wireless Network Name (SSID): Yes is required for Wi-Fi clients to find the wireless network.
- Wireless Client Security Separation: Useful in a guest network. This allows Wi-Fi clients to connect to the network, but are isolated from each other.
- Authentication Settings: To redirect Wi-Fi clients direct to your Facebook Wi-Fi page, Open System should be used.
- Captive Portal: Select the Profile Name configured in steps 5 - 12.
16 Click Apply.
When a Wi-Fi client attempts to connect to your wireless network they will be redirected to your Facebook business page. Depending on your Facebook Wi-Fi configuration the Wi-Fi client will be required to check in, skip check in or enter a passphrase to bypass check in, before being authenticated to the network.
After you add a captive portal for Facebook Wi-Fi, the associated portal splash page might not open under some circumstances, allowing users Internet access without logging in. This security limitation is implemented by Facebook Wi-Fi, not by NETGEAR. If a user opens a browser and attempts to access a website over HTTP (by default, over port 80), the user is directed to the splash page. However, if a user attempts to access a website that does not use HTTP, the splash page might not open and the user can access the website without logging in. For example, this situation occurs if a user opens a browser and accesses a secure website over HTTPS (by default, over port 443), or if an application uses HTTPS to send traffic to the Internet.