Bug #14660
closed
Sticky Connections do not work properly when multiple connections have the same Gateway IP
0%
Description
I have set up a multi-WAN configuration that involves multiple PPPoE connections to my Internet service provider. Each of these connections is assigned a distinct IP address, but they all share the same outbound gateway.
The issue I'm facing is that sticky connections are maintaining the connections to the same gateway. However, they are alternating between different PPPoE accounts due to the identical gateway IP addresses they possess.
To resolve this, it would be beneficial for the sticky connections to recognize instances of duplicate gateways. Instead of routing based on the duplicated Gateway IP, they should route based on the PPPoE connections and corresponding gateways (such as WAN1, WAN2, WAN3, etc.).
Files
Updated by Jim Pingle 9 months ago
- Status changed from New to Rejected
That isn't a supported case. pf has no way to differentiate between two identical gateways in this case and there isn't anything we can do about that.
Updated by Lucas Tam 9 months ago
Jim Pingle wrote in #note-1:
That isn't a supported case. pf has no way to differentiate between two identical gateways in this case and there isn't anything we can do about that.
That's what I figured, but documentation should be clarified for PPPoE that multi-gateway issues still exists:
"One exception to this is a PPP type WAN such as PPPoE. PPP type WANs are capable of having the same gateway on multiple interfaces , but each gateway entry must be configured to use a different monitor IP address (See Gateway Settings)."
Or, load balancing and sticky connections labels should detect the gateways are the same and display a warning.