NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WAC730 Captive Portal - Facebook - Issues
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.
lifesupp! message
Hi, I got this message, "lifesupp! message", while doing a resync (complete history follows) and I think I need some help from experts due the previous messages in this forum about this error. - My nas is a ReadyNas Pro with 6 bays, all equipped and disks were synced. - After a failure in disk 2 I procced to replace it but, during the resync, the disk 6 started to report failures. - At some point I got the following mail from the NAS: > Complete RAID volume synchronization in C. However, the array is still degraded mode. This may be due to failure of disk synchronization damaged or the presence of a disk array in multiple parity disks. - Looking at /proc/mdstat gives me this information: > Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] > md2 : active raid5 sdf5[8](S) sda5[0] sde5[7](F) sdd5[4] sdc5[6] sdb5[2] > 9743966480 blocks super 1.2 level 5, 16k chunk, algorithm 2 [6/4] [U_UUU_] > md1 : active raid6 sdf2[8] sda2[0] sde2[6] sdd2[4] sdc2[7] sdb2[2] > 2096896 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU] > md0 : active raid1 sdf1[8] sda1[0] sde1[7] sdd1[4] sdc1[6] sdb1[2] > 4194292 blocks super 1.2 [6/6] [UUUUUU] > unused devices: <none> - Status in control panel So, the question now is: what are the following steps? I have ssh access and a good technical background. Thanks.Wireless devices connected to WN3000RPv3 but no data (after FW upgrade)
I have just recently upgraded my N300 extender to the latest firmware package available (1.0.2.24). This was because I was having difficulty connecting several devices (iOS) to the WiFi. After the firmware upgrade all my devices are connecting, but they are not getting beyond the repeater to the router and all network access is refused. I can see that the extender has been assigned 192.168.1.250 and that is what my devices are using as Gateway/DNS. I have a wired device connected to the extender (via a switch) and that is getting a Gateway/DNS of 192.168.1.254 and is functioning just fine. So why are devices going through WiFi not getting through. Any steps I can take to remedy this issue?
