shehzman

> I think modifying config.xml state on CARP state changes is neither desirable nor wise. > > Cheers, Franco Is this not how you modify the WireGuard interface when the...

> And before I forget... > > > they will need 3 static IP addresses on the WAN side so they can setup CARP > > You can get by...

> Some community wireguard carp scripts have done this perhaps, but it's not good to modify configuration state and the core code supporting this does it differently for reasons mentioned....

> _Stopped_, not _disabled_. Runtime condition (CARP state) causes runtime modification of service (stop and start accordingly). > > To illustrate what I mean from the OP's script: > >...

> If you use CARP on WAN you will definitely have a static address even if hidden behind a NAT somewhere... I'm not sure why this confuses you the way...

> Ok no problem. For most purposes you don't need CARP on WAN really. This is mainly a workaround for suboptimal WAN access (like one DHCP account only) or when...