WAC730 Captive Portal - Facebook - Issues

[schumaku]

WAC730, standalone, v3.8.3.0, two SSID in service, FB Login proof of concept for customer demonstration

Created a new SSID, assigned the second captive portal NETGEAR-1

Configured the second captive portal NETGEAR-1 (why ever this profile name can't be renamed - Netgear does still not understand [my!] profile design concept you have stolen from another vendor), Captive Portal Mode (x) Enabled, Register with Facebook WiFi (x) Yes, Profile Name NETGEAR-1 [x] Admin enabled, Authentication mode: Facebook Wi-Fi, Facebook page: [set].

When accessing the SSID, the captive portal page does show up very unreliable - all current Windows 10/Android/iOS/macOS. When it does show up, we can check in to the Facebook site. And the access works kind of as expected. IF you have ever the chance to check-in on the FB site. [ISSUE!]

When now attempting to manage the WAC730 over the LAN, the Captive Portal does jump in - why ever, always. Regardless if calling https://wac730-1.[whatever.dom.ain]/ or https://[WAC730-LAN-ADMIN-IP]/ (same with http), the FB WiFi Captiv Portal does jump in:

...now we're nice, and [Check in] at the site...

 


...we can click on [Continue browsing] as many times as we want, the browser does call the LAN IP (as originally requested), and the [Continue Browsing] page does come up again. The WAC730 Web UI is not accessible over the LAN at this state. Even if trying a new session, a different browser - we're really captured. But not by accessing the SSID ... by attempting to manage the WAC730 over the LAN!

Obvious [BUG]. Firmware is current as of Support / WAC730- ProSAFE Business 3 x 3 Dual Band Wireless-AC Access Point v3.8.3.0.

Proof of concept failed, looks like we won't get an order Netgear WLAN equipment for this customer @RaghuHR. Bugware. Untested. Back to the skunkworks. 

Now I don't wonder why the Nighthawk router model(s) supporting FB WiFi are suffering from basic functionality issues as well.

[schumaku · Accepted solution]

Dear Raghu,

Briefly tested the updated Beta firmware (3.8.3.11), connected to the FB enabled ESSID, get prompted in the captive window (OK on Windows (Chrome), Chromebook (Chrome), and macOS (Safari). Once authenticated, the WAC730 Web UI is normally reachable. Will have to wait at least one hour until the authentication does expire. Then (or more tomorrow) we will try if the "normal" management ESSID does still require the authentication.

The access to the WAC730 admin Web UI is fine again the other day, no more forced FB logins on accessing it. Thank you again for taking care!

Regards
-Kurt

[RaghuHR]

Hi @schumaku

Could you please download the detailed logs from monitoring page and share with us? We will check and update.

Thanks,

Raghu

[RaghuHR]

Hi @schumaku

Quick question - Could you please let me know the MAC address of your wireless station?

Thanks,

Raghu

[schumaku]

Uh, what wireless STA? The workstation with the Web browser is (modern times) connected by Wi-Fi to that very same (W)LAN, it's some Inhell AC7260 adapter.

Reading between the line - does the WAC maintain a list of MAC address or prefixes to determine if the client has to be captured to the portal? Not the worlds best idea if true.

We must be able to maintain the WAC from any location, using any kind of connectivity.

Will share the logs when I have some better network coverage again - replying from rhe dog walk.

[schumaku]

Hi @RaghuHR, you got PM (STA MAC, WAC730 log) as per your request.

[RaghuHR]

Thanks. Will check and update

[schumaku · Accepted solution]

Dear Raghu,

Briefly tested the updated Beta firmware (3.8.3.11), connected to the FB enabled ESSID, get prompted in the captive window (OK on Windows (Chrome), Chromebook (Chrome), and macOS (Safari). Once authenticated, the WAC730 Web UI is normally reachable. Will have to wait at least one hour until the authentication does expire. Then (or more tomorrow) we will try if the "normal" management ESSID does still require the authentication.

The access to the WAC730 admin Web UI is fine again the other day, no more forced FB logins on accessing it. Thank you again for taking care!

Regards
-Kurt