Set name=DFNĪdd listen-port=XXXX mtu=1420 name=wireguard1 Does anyone experience this as well? Any ideas for a solution? I am thinking about writing a script that regularly loops over all peers and disables and enables them.Ĭode: Select all # apr/01/2022 20:57:57 by RouterOS 7.1.5 It seems like the public key of the client gets corrupted in the memory of the router and has to be read in again. I experienced this with several configurations of WG servers, so I am quite sure this is a WG-internal problem not related to firewall settings, routing tables or the like.ĭisabling and enabling the peer on the server instantly solves the problem and the client can reconnect. It is not client-specific, it happens with iOS, Android and also Windows clients. The problems shows up irregularly, sometimes after a few hours, sometimes after a few days, but not on all clients. Reconnecting from the client fails, the peer interface shows neither incoming nor outgoing traffic on the client I see a couple of kb outgoing traffic, but only few byte incoming every 20 seconds or so (accummulated values are usually 92, 124, 156, 188.).
Through all versions I experience the same problem: Some WG peers irregularly become disconnected and cannot reconnect, the tunnel just stops working and no traffic is going through it any more. I am running a WG server since 7.1beta6, now with 7.1.5.
