- User Since
- Mar 12 2018, 8:50 AM (161 w, 6 d)
Oct 1 2020
Sep 10 2020
@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.
Sep 8 2020
Latest rolling has this fixed. Thanks Viacheslav.
Jul 15 2020
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
Jul 6 2020
Any chance this will be revived for 1.3 or 2.0 ?
Any amount of firewalling is not gonna stop brute forcing.
Nov 13 2019
Mar 29 2019
Feel free to add patches that needs testing.
I will report back my findings with my setup (as previously PMed about)
Mar 5 2019
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.
Feb 27 2019
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.
Feb 19 2019
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.
Feb 15 2019
@hagbard is the patch for the validator issue in latest rolling or do you have a .deb i can apply ? :)
Feb 14 2019
i tried doing complete reinstalls and i can now confirm this bug as well.
Feb 11 2019
Feb 8 2019
Will try to reinstall the baremetal router since it is the most inconsistant of the two routers. The virtual one works with other peers.
Feb 7 2019
@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.
Feb 5 2019
Feb 2 2019
Feb 1 2019
Forgot to add version for both routers, sorry.
Wierd, i cannot reproduce this on LTS 1.2.0 on both baremetal and virtual instances.
Jan 30 2019
fma@glos1ce1dk:~$ sh ver Version: VyOS 1.2.0 Built by: Sentrium S.L. Built on: Sun 27 Jan 2019 19:08 UTC Build ID: 795d6338-c1ce-4ebb-992f-d064f5af9309
Oct 27 2018
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 ?
Oct 26 2018
This is still not added to rc3 and rc4 same error
Oct 16 2018
Was this by any chance merged to RC3 or will it first arrive in RC4 ?
Oct 10 2018
Here is the pastebin since im still not allowed to post on the wiki
Oct 8 2018
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
Oct 5 2018
@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.
Oct 3 2018
Oct 2 2018
@hagbard thanks for the awesome implementation of wireguard to vyos.
Aug 28 2018
@c-po i have redacted the parts of the config i dont want leaked and i will just change the passphase :)