Hello , somebody help me please, i use wireguard tunneling with proton service in my house, everythink is ok, but after uptade to v 7.14 everythink about wireguard is broke.
In the last step, when i need configure a wireguard peer, in this step have a issues, copy a private key and press aply,. after it, automatically the public key change, and this one is not the correct to connect, the wireguard tunnel still down, all them after inst v 7.14, everytihink without this is perfect.
Somebody tell me if you have a same issue, someboy help me to solve it.
I try to restore the version to the last v, but i can do it.
Thanks
Good day for everybody
“escuse me, my english is not good, i speak in spanish”
For me everything fell apart with 7.14 as well, mainly Mikrotik router ↔ Mikrotik router Wireguard VPN connections. Windows → Mikrotik router Wireguard VPN seemingly works.
This is what it looks like in the logs:
The private key that proton gives you to insert will create a different public key if you already have one generated by the router.
This is normal.
Much better is to hit the + symbol to generate your wireguard interface on the mikrotik and DONT hit apply.
First enter in the private key that Proton gives you in the appropriate slot and then hit apply.
In any case the public key generated, they already have its basically not used by you to send anywhere…
I have three WireGuard links on my RB750Gr3 and found yesterday that one of them is down with the same errors in the logs like yours @masterhrck.
It looks like after upgrade on this particular VPN link Public and Private keys have been replaced with different keys I don’t know about. They still looks like a keys but not mine. Either a bug or maybe MikroTik has “secret” code contributor inaptly trying to take control over MikroTik routers.
I have the same issue, something is broken with new version and wiredguard client, also many restrinctions for config more than one peer, for example only allow one peer for wiredguard interface, anyway wiredguard client does not works fine, i will downgrade
750GR 3 wireguard proton vpn works fine on version 7.14
What I’ve done:
1.Deleted and recreated the interface.
2.Peers /Private Key, the field must be empty.
Same here, after upgrade to version 7.14.1 both tunnels down. I hope this is resolved in the next version because the connection between two sites is down
Indeed, I see no issues with 7.14 or 7.14.1 (or prior)
There was an issue with some excees logging for endpoints without a specific address, but was fixed in 7.14.1 with *) wireguard - do not attempt to connect to peer without specified endpoint-address;
Up to 7.13.5 I ran dual stack connections via EOIP over WG without any problems using bridges on both sides. From 7.14 on, included 7.14.1, bridging doesn’t seem to work any more although WG/EOIP are established. Any idea about this?
Connections to the Wireguard VPN running on my Hex S suddenly stopped working a few days ago. Incoming clients seem to “establish” the connection from the client side (the Wireguard app shows up as “Active”, green circle), but in reality no traffic flows through and clients don’t have any connectivity.
I’m also getting all that spam in the logs about handshake not completing.
All of the clients had been working just fine for months, and I have never, ever touched their config since I first set them up (neither the peer config or the interface config).
Updating to the latest 7.15 beta 9 did NOT solve anything.
At least in my case, it turned out it was MY fault. IP addresses were configured in a way that they could clash for different peers.
By some kind of amazing coincidence, IPs had NEVER clashed for over a year of using Wireguard, so I was convinced nothing was wrong with my setup and that the issue was caused by the update. But no, I just happened to start getting IP clashes right after the RouterOS update by coincidence. I don’t know if anything in the update could have made it more likely for misconfigured IPs to clash more often, but I guess that still wouldn’t be something that needs fixing.
So at least in my case you can ignore the “bug report”.
I’ve upgraded from 7.12.x to 7.15.2 and this broke my wireguard connection with a raspberry and my vrf setup. For the VRF I’ve opened a ticket and I’m waiting for support. I’ll try to redo the wireguard config changing the key to see if it starts working again.
I also faced a bug after upgrading 7.13.x to 7.15.3.
Downgrading to 7.13.5 didn’t resolve it immediately. I noticed in the configuration that my peers all had the public key of my local router configured. After changing them back to the correct public keys my tunnels worked again.
So, now I knew about the configuration error I upgraded to 7.15.3 again and sureliy the public keys were incorrect again. The real bug here is that as soon as I changed them again to the correct values, they immediately changed back to the local public key of the local wireguard interface. I have not found a way to configure the correct public key on the peer on version 7.15.3.
After downgrading (again) to 7.13.5 I was able to change the public keys again, after which the tunnels came up. yay
