Hi to all

currently i have dozen of L2TP dialin interface, which i like to change for wireguard
ok
setting up wireguard is easy, but one thing what is important for me is missing

on L2TP i could "hook" script on UP/DOWN event, so i could generate traps, send emails, whatever i like on interface UP/DOWN
it is important feature because i need to know when the remote site is UP or DOWN
and yes, it could not have false positive, because events are triggered on UP/DOWN so they are always valid

how to achieve same/similar behavior with wireguard interfaces ?

Since WireGuard uses fixed ip addresses anyway, could you just set up a netwatch entry for the remote host and implement the functionality in up/down scripts?

Since WireGuard uses fixed ip addresses anyway, could you just set up a netwatch entry for the remote host and implement the functionality in up/down scripts?

hi @nescafe2002

yes, there is always a "scripting way" to make a things work
but i like to avoid this approach because, IF UP/DOWN events are generated by OS, so basically, you could never miss a short outages
and yes, i could PING, then simulate TRAP and send events, but ... there is always a chance to miss short/rapid disconnections, flapping

that is a reason why i asked in this forum, maybe i am overlooked some checkbox in Winbox, or some CLI ... but i am afraid that the WG protocol work this way, it is stateless

anyway , thank you for answer

Ok, afaik WireGuard is stateless, so no connect / disconnect occurs.

There is a last handshake property which you can use to detect activity, but since that would be based on a timeout - netwatch would be a better option.