In T1246 I noticed that while my fix makes the syntax correct enough that OpenVPN starts, it is actually missing the $variables inside the quotes as the patch changed double quotes to single quotes.
That means that instead of --push "dhcp-option DNS 1.1.1.1" or --push "route 192.168.0.0 255.255.255.0" it started with --push "dhcp-option " and --push "route "
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Jan 25 2020
Jan 25 2020
c-po moved T1975: OpenVPN tap devices won't come up automatically from Need Triage to Finished on the VyOS 1.3 Equuleus board.
Jan 24 2020
Jan 24 2020
Jan 22 2020
Jan 22 2020
Jan 20 2020
Jan 20 2020
Feb 27 2019
Feb 27 2019
Feb 23 2019
Feb 23 2019
Just tested the most recent nightly (1.2.0-rolling+201902222123) and it works! Thank you so much y'all.
Feb 22 2019
Feb 22 2019
@fromport http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-openvpn/vyatta-openvpn_0.2.60+vyos3+current2_all.deb or next rolling release (Feb 23rd).
Just tested the next day nightly build.
Feb 21 2019
Feb 21 2019
https://github.com/vyos/vyatta-openvpn/commit/9166dde7fd5ca7b313de585067b06af6a8b9c82a Should be in the next latest rolling, can you please test?
just compared 1.20-rc7, 1.2.0 official & the current rolling:
In T1259#33041, @varesa wrote:Hopefully a fix: https://github.com/varesa/vyatta-openvpn/commit/a0d7c07f1ff0b5fe7450d3a13c1365b8e3589725
After doing: sudo curl https://raw.githubusercontent.com/varesa/vyatta-openvpn/a0d7c07f1ff0b5fe7450d3a13c1365b8e3589725/lib/Vyatta/OpenVPN/Config.pm -o /opt/vyatta/share/perl5/Vyatta/OpenVPN/Config.pm commit with my above config succeeds.
Produced command seems to be:
Also managed to reproduce, some set-commands to help reproduction:
Oct 21 2018
Oct 21 2018
dmbaturin added a comment to T430: It's not possible to configure openvpn client ip address in server mode.
This issue appears to no longer be reproducible.
Oct 15 2018
Oct 15 2018
syncer moved T355: Outstanding CVEs - OpenVPN from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.0-rc1) board.
syncer edited projects for T355: Outstanding CVEs - OpenVPN, added: VyOS 1.2 Crux (VyOS 1.2.0-rc1), VyOS-1.2.0-GA; removed VyOS 1.2 Crux.
Oct 13 2018
Oct 13 2018
syncer edited projects for T430: It's not possible to configure openvpn client ip address in server mode, added: VyOS 1.2 Crux (VyOS 1.2.0-rc4); removed VyOS 1.2 Crux.
Jan 21 2018
Jan 21 2018
Dec 29 2017
Dec 29 2017
c-po moved T355: Outstanding CVEs - OpenVPN from In Progress to Finished on the VyOS 1.2 Crux board.
Dec 28 2017
Dec 28 2017
c-po moved T355: Outstanding CVEs - OpenVPN from Need Triage to In Progress on the VyOS 1.2 Crux board.
@UnicronNL lithium branch @ https://github.com/vyos/openvpn
Dec 21 2017
Dec 21 2017
syncer changed the visibility for T430: It's not possible to configure openvpn client ip address in server mode.
syncer triaged T430: It's not possible to configure openvpn client ip address in server mode as Low priority.
Oct 24 2017
Oct 24 2017
Oct 3 2017
Oct 3 2017
@dmbaturin @syncer Where can i find the lithium repo?
Aug 20 2017
Aug 20 2017
syncer edited projects for T355: Outstanding CVEs - OpenVPN, added: VyOS 1.2 Crux; removed VyOS 1.1.x (1.1.8).
Thanks,
will move this to 1.2 project instead
CVE-2014-8104 is fixed by this commit: https://github.com/vyos/openvpn/commit/eb42da67b9a971a1cec94e3c65350d2e5dccf096
@syncer The version of openvpn in 1.1.7 is 2.1.3. 2.1.3 is not affected by these CVEs. See https://www.cvedetails.com/vulnerability-list/vendor_id-3278/product_id-5768/version_id-176319/Openvpn-Openvpn-2.1.3.html
Aug 19 2017
Aug 19 2017
Jul 24 2017
Jul 24 2017