Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
userdoc:tt_wan_failover [2018/06/18 14:32] abelbeck [Example: 4G/LTE Modem Failover] |
userdoc:tt_wan_failover [2019/03/31 17:00] mknill [PPPoE on Failover Interface] |
||
---|---|---|---|
Line 48: | Line 48: | ||
The above network options define the " | The above network options define the " | ||
- | !!Tip ->!! Any changes to these External Failover Interface settings will require a system reboot to be applied. | + | !!Note ->!! Any changes to these External Failover Interface settings will require a system reboot to be applied. |
Line 113: | Line 113: | ||
===== PPPoE on Failover Interface ===== | ===== PPPoE on Failover Interface ===== | ||
- | AstLinux supports at most one instance of PPPoE internally, | + | AstLinux supports at most one instance of PPPoE internally, |
+ | If you need to PPPoE for the failover external interface, | ||
- | In this example, PPPoE is configured on the Failover interface using the interface '' | + | This can be achieved in two ways: |
- | PPPOEUSER=" | + | 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. |
- | | + | 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 (should be single) connected client via DHCP. This may be a better solution as an extra NAT is not added to the network path. |
- | PPPOEIF=" | + | |
- | EXT2IF=" | + | |
- | As an alternative, | ||
===== Example: 4G/LTE Modem Failover ===== | ===== Example: 4G/LTE Modem Failover ===== |