Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_wan_failover [2019/03/31 17:08]
mknill [PPPoE on Failover Interface]
+++ userdoc:tt_wan_failover [2019/10/13 20:55]
abelbeck
@@ Line 94: / Line 94: @@
   esac
+  exit 0
+===== Action Exit Script (optional) =====
+Conditionally test when a Secondary -> Primary WAN link change occurs, by executing a script.
+If this script has an exit value of 0 the link change occurs, else with any other exit value the failover remains on the Secondary WAN.
+The script must be found at ''/mnt/kd/wan-failover-exit.script'' and be made executable...
+  chmod 755 /mnt/kd/wan-failover-exit.script
+Example: ''/mnt/kd/wan-failover-exit.script''
+  #!/bin/sh
+  ##
+  ## wan-failover-exit action script
+  ##
+  ## Automatically called before any Secondary -> Primary WAN link change
+  ## and the Primary WAN link is reachable.
+  ##
+  ## If this script has an exit value of 0 the link change occurs.
+  ## Else with any other exit value, the failover remains on the Secondary WAN.
+  ##
+  ## Note: Do not 'sleep' in this script, exit promptly.
+  ##
+  state="$1"
+  primary_if="$2"
+  primary_gw="$3"
+  secondary_if="$4"
+  secondary_gw="$5"
+  secondary_gw_ipv6="$6"
+  ## Sanity check, 'state' must be set properly
+  if [ "$state" != "SECONDARY_EXIT" ]; then
+    exit 0
+  fi
+  . /etc/rc.conf
+  ##
+  ## Allow Secondary -> Primary WAN link change ?
+  ##
+  ## Custom user.conf variable, if "yes" failover will not return to the Primary WAN link
+  if [ "$CUSTOM_WAN_FAILOVER_STICKY" = "yes" ]; then
+    exit 1
+  fi
+  ## Check Asterisk active calls, remain on the Secondary WAN link until no active calls
+  active_calls="$(asterisk -rx 'core show channels' | sed -n -r -e 's/^([0-9]+) +active +call.*$/\1/p')"
+  if [ -n "$active_calls" ] && [ $active_calls -gt 0 ]; then
+    exit 1
+  fi
   exit 0
@@ Line 117: / Line 173: @@
 This can be achieved in two ways:
-) Terminating the WAN connection with a PPPoE capable router. In this scenario both Astlinux and the router will perform NAT which can be problematic for some traffic types such as voice. If voice traffic is being tunnelled through a VPN however, this should not be an issue.
+  *   Terminating the WAN connection with a PPPoE capable router. In this scenario both Astlinux and the router will perform NAT which can be problematic for some traffic types such as voice. If voice traffic is being tunnelled through a VPN however, this should not be an issue.
+  *   Terminating the WAN connection with a PPPoE capable modem configured into half bridge mode. In this scenario, the modem authenticates via PPPoE but bridges the Public IP Address to the Astlinux failover external interface via DHCP. This may be a better solution as an extra NAT is not added to the network path.
-) Terminating the WAN connection with a PPPoE capable modem configured into half bridge mode. In this scenario, the modem authenticates via PPPoE but bridges the Public IP Address to the Astlinux failover external interface via DHCP. This may be a better solution as an extra NAT is not added to the network path.
+!!Note ->!! If you are using half bridge mode, unless you have a static IP Address from your ISP the modem will not update the IP when it is changed until the next dhcp renewal. Due to this, most half-bridge modems use extremely short dhcp lease times which is not optimal. It is better to avoid dynamic IP's altogether and set the Astlinux failover external interface statically to the Public IP, with the DHCP client disabled in the modem.
-!!Note ->!! Unless you have a static IP Address from your ISP the modem will not update the IP when it is changed until the next dhcp renewal. Due to this, most half-bridge modems use extremely short dhcp lease times which is not optimal. It is better to avoid dynamic IP's altogether and set the Astlinux failover external interface with the public IP, with the DHCP client disabled in the modem.
 ===== Example: 4G/LTE Modem Failover =====