Hello, I’ve seen similar issues in the forum but not exactly what I’m experincing, so figured I’d post something.
I have a main Mikrotik and a peer Mikrotik using a road warrior setup. Both Mikrotiks are on 7.18.2
Main Mikrotik-A wireguard config:
[admin@Mikrotik-A] > /interface/wireguard/
name="wireguard1" mtu=1420 listen-port=13231 private-key="\"
public-key="\"
[admin@Mikrotik-A] > /interface/wireguard/peers/
0 ;;; Mikrotik-B
interface=wireguard1 name="peer1" public-key="" private-key="" endpoint-address="" endpoint-port=0
current-endpoint-address=\ current-endpoint-port=13231 allowed-address=172.200.0.10/32 preshared-key="" client-endpoint=""
responder=yes
Peer Mikrotik-B wireguard config:
[admin@Mikrotik-B] > interface/wireguard/
name="wireguard1" mtu=1420 listen-port=13231 private-key="\"
public-key="\"
[admin@BeaverDen] > interface/wireguard/peers
0 ;;; Mikrotik-A
interface=wireguard1 name="peer1" public-key="\" private-key="" endpoint-address=\
endpoint-port=13231 current-endpoint-address=\ current-endpoint-port=13231 allowed-address=0.0.0.0/0 preshared-key=""
persistent-keepalive=45s client-endpoint=""
This issue I’m having is when the peer mikrotik-B reboots, the wireguard connection will work briefly and I can see the handshake occur on Mikrotik-A. The connection will work for a few minutes and then stops responding.
I can see in the peer mikrotik-B log, its trying to send handshake attempts, but the main mikrotik-A stops responding. The only way I can get it start working again is to disable and re-enable the peer interface on Mikrotik-A.
Mikrotik-A will start responding to the handshakes and will work fine, until mikrotik-B reboots again.
Ideas?