NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Failover
4 TopicsFeature request - LB2120 LTE Router -use mobile broadband by default and failover to wireline
How do I submit a feature request? Currently my LB2120 LTE router can "Use wireline broadband by default and failover to mobile broadband." However, I need it to "use mobile broadband by default and failover to wireline broadband."I have much better wireless broadband, but have a slow DSL line that I would like to use as a backup.Thanks!5.1KViews1like1Commentwndap360 radius failover with 3.6.9.0 firmware not working
Hello, we are just cleaning up our WLAN infrastructure, and for this we upgrade the WNDAP360 AP from firmware 3.5.6.0 to the most recent 3.6.9.0. In the same step we also change the radius infrastructure to use two new servers instead of one old server. Upgrade and Radius work fine under normal conditions. But what is not working, is the failover to the secondary radius server, when the first one is not responding. The primary Radius server is 192.168.163.9:1812, the secondary one at 192.168.163.10:1812 Both servers are running Windows 2016 Server, with NPS installed and configured for Radius. In the log of the AP I see this: Jun 1 17:36:05 hostapd: wifi1vap7: RADIUS Authentication server 192.168.163.9:1812 Here a station connects with WPA2-Enterprise and auth via the primary radius server works fine Jun 1 17:36:18 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: associated Jun 1 17:36:18 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 17:36:18 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 17:36:19 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 WPA: pairwise key handshake completed (RSN) Jun 1 17:36:19 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: authenticated - EAP type: 25 (PEAP) We then disconnect the station, and shut down the primary radius server. Then we try to connect to the station again, but here we see repeated auth failures: Jun 1 17:38:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: associated Jun 1 17:38:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 17:38:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 17:38:35 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 17:38:53 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: recvd disassoc msg from STA, reason code (8), rssi (67) Jun 1 17:38:53 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: disassociated At the same time, we see many ARP requests on the LAN for the IP 192.168.163.9 from the AP (So the AP is trying to find the now gone radius server) We did leave the primary radius server turned off for about 15 minutes, and the AP did still try to find the 192.168.163.9 radius server, no failover Then we turned the primary radius server on again, and authentication works fine again: Jun 1 17:52:37 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 17:52:37 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 17:52:38 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 WPA: pairwise key handshake completed (RSN) Jun 1 17:52:38 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: authenticated - EAP type: 25 (PEAP) Also when we reboot the AP with the primary radius offline, it does not pick the secondary radius server. FW Version WNDAP360_V3.6.9.0 Config Version 4.0 CMAPD Version: 1701.27.1803.40 Jun 1 02:00:50 init: init: starting pid 1808, tty '/dev/ttyS0': '/sbin/getty -L ttyS0 9600 vt100' Mar 17 15:29:06 udhcpc[656]: Sending discover... Mar 17 15:29:06 udhcpc[656]: Sending select for 192.168.163.233... Mar 17 15:29:06 udhcpc[656]: Lease of 192.168.163.233 obtained, lease time 2678400 Mar 17 15:29:10 kernel: php used greatest stack depth: 5092 bytes left Mar 17 15:29:10 kernel: php used greatest stack depth: 4764 bytes left Jun 1 18:25:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: associated Jun 1 18:25:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:25:17 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 18:25:17 hostapd: wifi0vap2: RADIUS Send failed - maybe interface status changed - try to connect again Jun 1 18:25:17 hostapd: wifi0vap2: RADIUS Authentication server 192.168.163.9:1812 Jun 1 18:25:35 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:25:53 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: recvd disassoc msg from STA, reason code (8), rssi (67) Jun 1 18:25:53 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: disassociated Jun 1 18:26:07 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: associated Jun 1 18:26:07 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:26:07 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 18:26:25 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:26:43 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: recvd disassoc msg from STA, reason code (8), rssi (67) Jun 1 18:26:43 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: disassociated Jun 1 18:26:58 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: associated Jun 1 18:26:58 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:26:58 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: EAP Identifier of the Response-Identity does not match (was 0, expected 1) - ignored Jun 1 18:27:16 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.1X: aborting authentication Jun 1 18:27:34 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: recvd disassoc msg from STA, reason code (8), rssi (68) Jun 1 18:27:34 hostapd: wifi0vap2: STA 74:de:2b:9f:3e:e4 IEEE 802.11: disassociated Any ideas what I can try, to get the failover working?Solved5.4KViews0likes4CommentsXSM7224S to Cisco Redundancy/Failover
Hello, Im trying to figure out how to setup a redundancy/failover connection between XSM7224S and Cisco 3750X. This is what I have currently: Netgear Switch 1------------------------------ Netgear Switch 2 | | Cisco 3750X Switch 1 | Cisco 3750X Switch 2 | Cisco 3750X Switch 3------------------------ Cisco 3750X Switch 4 2 Netgear XSM7224S (Stacked). member 1 1 member 2 1 !stack-port 1/0/24 stack !stack-port 2/0/24 stack switch 1 priority 15 switch 2 priority 1 Netgear Switch 1 is connected to our main Cisco Core 3750 via 10GB Fiber Port: Netgear Config interface 1/0/2 no auto-negotiate no port lacpmode description '10G-Uplink-to-Core' mtu 9198 vlan participation include x,x,x,x,x,x vlan tagging x,x,x,x,x,x mode dvlan-tunnel Cisco Switch interface TenGigabitEthernet3/1/1 description P-DC1-ETHSW10G-02 Port 1/0/2 switchport trunk encapsulation dot1q switchport trunk allowed vlan x,x,x,x,x,x switchport mode trunk What Im looking for is to setup a redundancy type connection where if the 1st Netgear switch goes down, the secondary takes over, or if the 3rd Cisco switch goes down, the 4th one takes over. But I dont want to use both at the same time, in other words, I need something like a priority. If this link goes down, then this one takes over. Something like this: Netgear Switch 1------------------------------ Netgear Switch 2_______________ | | | Cisco 3750X Switch 1 | | Cisco 3750X Switch 2 | | Cisco 3750X Switch 3----------------- |----- Cisco 3750X Switch 4___________| Thank you very much for your support....2.7KViews0likes3CommentsFailover?
We have two of the ReadyNAS 516's on the same LAN. We are replacing an existing Windows 2008 server. We want to have the primary NAS for storage and the 2nd as a backup (really as a failover- and we know it will be manual). How can we quickly get the 2nd unit up as the primary in the case of a total failure of the primary? We have setup with ReadyNAS Replicate, but this looks like a backup and the restore process takes a while.Solved2.8KViews0likes2Comments