In T2943#76739, @runar wrote:

as a workaround you could add this to a post-boot script on the device.

@rherold Would this extend to usage such as VPN interfaces like wireguard interfaces ?
I know it is an edge use case but it is nice for lab testing with VPS´s in multiple datacenters.

Latest rolling has this fixed. Thanks Viacheslav.

PR created https://github.com/vyos/vyos-1x/pull/498

Did the changes on dependencies file here: https://github.com/Maltahl/vyos-1x/commit/27400e09b27d98b6ee34568fe25828cff1d14770

If someone could point me in the direction where wireguard config files are stored in VyOS i will be happy to test it out further.

I tested by just adding default debian buster repos and run

sudo apt install qrencode

Any chance this will be revived for 1.3 or 2.0 ?
Any amount of firewalling is not gonna stop brute forcing.

Feel free to add patches that needs testing.
I will report back my findings with my setup (as previously PMed about)

No dice sadly. I think we have to close this since i have a feeling it might be more than 1 issue.
I think the problem with the bond vif interface not sending recieving is a critial error but i do not know how to report it correctly.
The other issue i think is related is the static routes not being applied.

Ye it works fine. How else would it be able to work before with same routers, same ips, same config ? I can also access services no problem on the remote site (reverse proxy) but not services on the local network on the remote site.

Tried both and they solved the issue but same problem with the tunnel not going up is the same.
I tried regen keys on both ends. No dice.

@hagbard is the patch for the validator issue in latest rolling or do you have a .deb i can apply ? :)

i tried doing complete reinstalls and i can now confirm this bug as well.

In T1226#32490, @hagbard wrote:

All right, let me know if you need help.

Will try to reinstall the baremetal router since it is the most inconsistant of the two routers. The virtual one works with other peers.

In T1226#32251, @hagbard wrote:

@Maltahl That smells more like an issue with your key setup. The wg interface listens on any interface which is up and running. If the traffic inside the wg interface doesn't show anything, that means it can't decrypt the traffic with your private key.

@hagbard i have tried removing all firewall rules on both routers and checked that the wireguard module was running. i have also tried allowing all traffic and also allowed udp for the wireguard port when it arrived.

In T1226#32102, @hagbard wrote:

@Maltahl Let me know if you still need help, please. I put the task meanwhile on-hold.

In T1226#32033, @hagbard wrote:

@Maltahl Did you try the same with the rolling release? I don't see any issue with your config in particular, did you check that the wg traffic is actually getting to your router02?

In T1226#32008, @runar wrote:

Hi! I see that your tunnels does not resides inside the same subnet, one devise is '10.0.90.1/24' and the other one '10.0.100.1/24'.. please move one of then to ip .2 in the subnet belonging to the other router.

Forgot to add version for both routers, sorry.

Wierd, i cannot reproduce this on LTS 1.2.0 on both baremetal and virtual instances.

Thanks hagbard!
I was litterally pulling my hair out over the error cause i have seen wireguard work in all its glory.
If i want to apply the patch on my own are there any resources i should use or is it simply a dpkg install ?

This is still not added to rc3 and rc4 same error

Was this by any chance merged to RC3 or will it first arrive in RC4 ?

Here is the pastebin since im still not allowed to post on the wiki
https://pastebin.com/sZcJLyeB

I tried adding the wiki updates last saturday without any luck ( was not allowed to post updates )
Will post a pastebin with wiki text for review later today

@hagbard status so far is that i am nearly done with 3 types of setups with minor edits on existing wiki documentation for wireguard as it was not updated to match current commands :)
There is also some clearification on what each segment of the config is to avoid confusion newcomers that want to try it out.
I will add it after work today.

In T774#20257, @hagbard wrote:

Hang on a sec, have a look here:
https://github.com/vyos/vyos-documentation

@hagbard thanks for the awesome implementation of wireguard to vyos.

@c-po i have redacted the parts of the config i dont want leaked and i will just change the passphase :)

trying to setup DMVPN HUB using the wiki as reference on 1.2.0-rolling+201808272007