Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
userdoc:tt_wan_failover [2019/03/31 17:08] mknill [PPPoE on Failover Interface] |
userdoc:tt_wan_failover [2019/03/31 17:13] mknill [PPPoE on Failover Interface] |
||
|---|---|---|---|
| Line 117: | Line 117: | ||
| This can be achieved in two ways: | This can be achieved in two ways: | ||
| - | 1) 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. |
| - | + | | |
| - | 2) 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 ->!! 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 ===== | ===== Example: 4G/LTE Modem Failover ===== | ||