Upgrading -> Wireguard bug?

RouterOS General
1

Sorry if this is redundant, but I wanted to post a possible bug regarding wireguard tunnels:

Upgrading Routeros 7.13.4. to 7.14.1: working Wireguard tunnels (eg to NordVPN) fail to TX (no change in config). 0 bytes send/received, error # increasing.

Downgraded → same problem

Upgraded again → problem still there.

Then changed the private/public keys in the interface as well as in the peers to WRONG keys and applied. Then entered the correct keys again, applied and voila: everything is working again!

Seems like a bug to me….

2

Read the 7.14 thread… http://forum.mikrotik.com/t/v7-14-3-stable-is-released/174007/1 or do forum search for like issue…
http://forum.mikrotik.com/t/too-many-wireguard-logs-from-version-7-14beta3/172509/1

Lots of problems with wg and logging etc…


/system/logging/set 0 topics=info,!wireguard action=memory

3

I have encountered this bug many times. It has driven me nuts over and over. The linked thread looks like a different issue to me. I don’t have an issue with too many logs, but as described in licht77’s post. TX goes up but RX stays at zero and no connection. I remove the client endpoint, apply, add it back, apply and things start to work. I’ve encountered this at least 5 times and now 100% sure of the mechanism. It applies when both ends have a client endpoint specified. Before someone says that maybe it’s not meant to work with my config, then it has to be a bug when it starts working. In one way or the other it’s a bug. I am on 7.20.1

4

mike kulls, its a nice story, but without evidence aka the config, its fiction :slight_smile:

/export file=anynameyouwish ( minus router serial number, any public WANIP information, keys, dhcp lease lists).