Multi WAN & L2TP
-
I have 2 independent internet connections coming into my PFsense box via a PPPoE connection.
I have a L2TP tunnel which gives me a /29 and currently I have selected both interfaces but it doesn't seem to fail over correctly.
What am I doing wrong to ensure I don't loose the L2TP VPN which is mainly for inbound traffic.
I am reading mixed ideas of how it should be configured.
-
@MattL88 when you say you "selected both interfaces" ... where do you mean exactly? Because if you're configuring a PPP client interface, I think selecting >1 interface there is for multilink PPP (MLPPP) which is a different animal. Not really the same as multi-WAN/failover. There isn't much documentation about using pfSense as an L2TP client. It's a pretty lousy RA protocol as they go, compared to IPSEC, WireGuard or OpenVPN. So if you've got other options somehow, I'd suggest switching. It might be possible to rig something using some advanced outbound NAT rules and binding the PPP client to an inside LAN interface, but I'm not really sure. Maybe someone else knows more...
-
@luckman212 said in Multi WAN & L2TP:
imal. Not really the same as multi-WAN/failover. There isn't much documentation about using pfSense as an L2TP client. It's a pretty lousy RA protocol as they go, compared to IPSEC, WireGuard or OpenVPN. So if you've got other options somehow, I'd suggest switching. It might be possible to rig something using some advanced outbound NAT rules and binding the PPP client to an inside LAN interface, but I'm not really sure. Maybe someone else knows more...

This is how I currently have it connected. I am beginning to think I should have 2 seperate connections on the 2 links rather than the way I've done it.
-
@MattL88 right, that's what I figured. What you're showing there is MLPPP, which again needs support on the far end (and is probably not supported by your provider). Click here to read more on that.
I'm sorry I can't offer a working configuration for a multi-WAN L2TP client with failover. Like I said, you're swimming in mostly uncharted waters here. I suggest trying to switch to a more modern and better documented protocol for your setup.
-
@luckman212 Thanks for that. I have a ticket logged with the service provider on this one to see what the offer.
Privacy Policy · Cookie Policy