Michael, It appears the "DEFAULTROUTE=yes" is set to the pppoe.conf in our network script ... you don't want to be messing with that.
> Do I have any other options? Make the PPPoE as the primary link and the other as the EXT2IF link, add some major routing to EXT2IF link. Lonnie > On Oct 12, 2018, at 2:25 PM, Michael Knill > <michael.kn...@ipcsolutions.com.au> wrote: > > Hmm that's a pity. The scenario is that I have a site where I believe I am > having voice issues on the primary link (static IP), so I have installed > another WAN service from a known working provider (PPPoE). > So I want to send all traffic out the primary and send the voice traffic only > out the backup. I was hoping to do this with WAN Failover with a secondary > route configured and I really don't want to configure the modem into router > mode and rely on it to do NAT. > > Do I have any other options? > > Regards > Michael Knill > > On 13/10/18, 6:10 am, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote: > > Hi Michael, > >> However after doing this, it allocated ppp0 as the default route even though >> it was showing as EXT2IF and eth0 as EXTIF. > > Yes, I can see that happening. > > Possibly we need to edit that WiKi section. > > https://doc.astlinux-project.org/userdoc:tt_wan_failover#pppoe_on_failover_interface > > For PPPoE on a failover (EXT2IF) interface, can you configure your PPPoE > modem in "router" mode where the credentials are set in the modem ? Then the > AstLinux configuration would be just like a 4G/LTE modem in "router" mode. > In such a case you would set the "WAN Failover Configuration -> External > Failover Interface:" as "Static IP" to match the subnet defined by the PPPoE > modem in "router" mode. > > If the failover connection is over WireGuard the extra NAT of the PPPoE > modem in "router" mode should not be an issue. > > Lonnie > > > >> On Oct 12, 2018, at 2:24 AM, Michael Knill >> <michael.kn...@ipcsolutions.com.au> wrote: >> >> And the other question is what I set the WAN Failover Tab -> Connection >> Type: to? DHCP? >> >> Regards >> Michael Knill >> >> From: Michael Knill <michael.kn...@ipcsolutions.com.au> >> Reply-To: AstLinux List <astlinux-users@lists.sourceforge.net> >> Date: Friday, 12 October 2018 at 6:20 pm >> To: AstLinux List <astlinux-users@lists.sourceforge.net> >> Subject: [Astlinux-users] WAN Failover and PPPoE >> >> Hi Group >> >> As per the WAN Failover page, I tried to configure the backup interface for >> PPPoE as follows. Note primary WAN is static address on eth0: >> >> Network Tab -> Failover Interface -> eth2 >> >> user.conf >> PPPOEUSER="username" >> PPPOEPASS="password" >> PPPOEIF="eth2" >> EXT2IF="ppp0" >> >> However after doing this, it allocated ppp0 as the default route even though >> it was showing as EXT2IF and eth0 as EXTIF. >> WAN Failover would also not start with an error of ‘daemon.err wan-failover: >> ERROR Primary interface gateway not found, will restart on a network change.’ >> >> Any ideas? >> >> Regards >> Michael Knill >> _______________________________________________ >> Astlinux-users mailing list >> Astlinux-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pay...@krisk.org. > > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.