Feature Request: L2TP Peer Redundancy / Failover Support

[Danster]

Hi there,

Unless I’ve overlooked an existing feature, I wanted to ask whether there are any plans to implement L2TP peer redundancy or failover support in MPD5?

For example, my use case involves configuring multiple L2TP peers (e.g., a primary and secondary) within a single L2TP template. The idea would be that, should the primary peer become unreachable (detected via lack of hello packets or similar mechanism), the system automatically attempts to establish a connection with the backup peer.

This kind of failover functionality would greatly improve reliability in scenarios where high availability is important, and would be especially useful for providers or systems that rely on redundant L2TP gateways.

If such a feature is not currently planned, I’d be happy to provide more details on the use case or contribute in any way I can.

Thank you for all your work on MPD5 – it's a fantastic tool.

Cheers.

[Eugene Grosbein]

Such implementation is not planned at the moment. However, you can get it with some scripting and mpd5's telnet console: use "set iface down-script" for primary peer to issue "open" command for secondary peer over telnet.

[Danster]

Hi Eugene,

Thanks for the response. But, I am not following you 100%.

The below is dummy config just to create some context:

default:
        load complete_lac



#==========================================================================
#VLAN2485
#==========================================================================

        create link template L2485 pppoe
        set pppoe iface vtnet1
        set link no eap
        set link enable pap chap chap-msv1 chap-msv2 chap-md5
        set link enable multilink
        set link action forward L30 "@test$"
        set link enable incoming


#==========================================================================
#Actions
#==========================================================================

#-------@test---------------------#
        create link template L30 l2tp
        # Primary peer configuration
        set l2tp peer 10.56.14.1
        set l2tp secret HDSGciuyt675

        # Secondary peer configuration
        create link template L30 l2tp
        set l2tp peer 10.56.14.2
        set l2tp secret HDSGciuyt675
        set link disable incoming

I should have mentioned that I am running the complete_lac mode, apologies. Any way you could provide some insight on how / what the script would manipulate when the primary peer goes down?

Thanks.