OPNsense Forum

Archive => 23.1 Legacy Series => Topic started by: sc0ttjm on March 15, 2023, 01:09:47 PM

Title: Multi-WAN GW Failover when using PPoE and 4g/LTE as WAN
Post by: sc0ttjm on March 15, 2023, 01:09:47 PM
The OPNsense Documentation is excellent around Gateway groups / Multi WAN and I was able to follow this in a test environment on my new DEC675 unit without any issues.
This test involves 2 DHCP WAN connections.
In the real world I'll be using a UK vDSL connection (PPPoE) as WAN and a Robustel 4G/LTE router as WAN2.
As soon as I change the WAN from DHCP to to use PPoE, the failover no longer works.
I can get internet connection using the PPoE configuration but what's strange is that when I look under System>Gateways>Single I see a new gateway called "WAN_GW" which is marked as active and is using IPv6 and I'm not using IPv6 anywhere.  I'm not sure if this is causing the issues as it seems to take priority over the actual WAN gateway that is also listed.
(//)
Has anybody managed to setup PPoE as part of a GW Failover group succesfully?
I'm using a brand new DEC675 appliance from Deciso and OPNsense Business Edition Version 22.10.2

Title: Re: Multi-WAN GW Failover when using PPoE and 4g/LTE as WAN
Post by: undistio on March 17, 2023, 03:57:01 AM
So, I have a similar setup. I suspect you haven't fully completed all the steps to set up a PPPoE connection.

First, to get PPPoE working:

After that, you can turn on gateway monitoring for the the automatically generated gateway and include it in a group.
Title: Re: Multi-WAN GW Failover when using PPoE and 4g/LTE as WAN
Post by: sc0ttjm on March 17, 2023, 11:55:06 AM
Thank you so much for this!
Yes it is now working exactly as expected.
I just wasn't setting up the PPoE connection first under "Interfaces>Point-to-Point>Devices", I was doing it from the "Interfaces>WAN>Generic configuration" section.
I was also getting confused whether it was working or not as I was running a speedtest so test teh connection and view my external IP so I knew which WAN connection was being used, but I didn't realise that the default GW Failover Pool Option was "Round Robin, Sticky Address" so of course when I refreshed the page it looked like it had not failed across as it will use the first connection in that session until it is no longer available.
Thanks again, I was struggling with this for a while so you saved me a lot of time.
BTW, the IPv6 Gateway still appears but doesn't make any difference to teh functionality so it wasn't related to the issues I saw after all, but I'm not sure why it is there.