Page MenuHomeFreeBSD

OpenVPN 2.4 preview
AbandonedPublic

Authored by mandree on Dec 15 2016, 11:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 8, 8:48 PM
Unknown Object (File)
Mon, Apr 8, 8:48 PM
Unknown Object (File)
Feb 11 2024, 12:37 PM
Unknown Object (File)
Jan 15 2024, 1:19 PM
Unknown Object (File)
Dec 26 2023, 6:00 AM
Unknown Object (File)
Nov 16 2023, 12:10 PM
Unknown Object (File)
Nov 16 2023, 8:04 AM
Unknown Object (File)
Nov 14 2023, 8:01 AM

Details

Reviewers
None

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

mandree retitled this revision from to OpenVPN 2.4 preview.
mandree updated this object.
mandree edited the test plan for this revision. (Show Details)
mandree set the repository for this revision to rP FreeBSD ports repository.

I tried it (by unpacking the tarball referenced in the message to the ports list as security/openvpn-test, then running

portmaster -o security/openvpn-test openvpn-2.3.14

on my laptop running FreeBSD/amd64 stable/11@r310109.

I then tried using the result to login to work (which is my usual use of openvpn); it worked.

There is a test that is part of the check-TESTS target that takes a long time when building in poudriere:

Testing cipher RC2-CBC... OK
Testing cipher RC2-CFB... OK
Testing cipher RC2-OFB... OK
Testing cipher none... OK
PASS: t_lpback.sh
The following test will take about two minutes.
If the addresses are in use, this test will retry up to two times.

It really takes about two minutes. Whatever this test is testing, does it work in a jail? Otherwise it's only wasting build time...

Using the same options as for the 2.3 version of the port, I have no problems running it on my server.

There is a test that is part of the check-TESTS target that takes a long time when building in poudriere:

Testing cipher RC2-CBC... OK
Testing cipher RC2-CFB... OK
Testing cipher RC2-OFB... OK
Testing cipher none... OK
PASS: t_lpback.sh
The following test will take about two minutes.
If the addresses are in use, this test will retry up to two times.

It really takes about two minutes. Whatever this test is testing, does it work in a jail? Otherwise it's only wasting build time...

Thanks. It is running a client-server test on the loopback interface and also runs smoke tests against timeouts, hence it's indeed mostly sitting there waiting for timers to expire, but I am not aware that the tests were said to be ineffective in jails. If that's something of concern, it should be taken to the upstream's openvpn-devel@ mailing list for discussion, it's not an artifact of FreeBSD packaging (there isn't a difference if you build in a jail vs. a live system as far as I can tell).

Using the same options as for the 2.3 version of the port, I have no problems running it on my server.

I'm testing the 2.4_rc2 upstream release and if successful, I shall be uploading a new set of diffs and tarball shortly.

updated to -rc2, with the old port status preserved in openvpn23 and openvpn23-polarssl ports that are marked deprecated and to expire 2017-03-31.

Complete tarball: https://people.freebsd.org/~mandree/openvpn-2.4_rc2-v1.tar.xz

[2nd upload, without unrelated putty-nogtk bits]

updated to -rc2, with the old port status preserved in openvpn23 and openvpn23-polarssl ports that are marked deprecated and to expire 2017-03-31.

Complete tarball: https://people.freebsd.org/~mandree/openvpn-2.4_rc2-v1.tar.xz

I've updated the TUNNELBLICK patch to work with 2.4, it was just a clash with the new code formatting. Looks good so far, runtime test is pending.

Thank you for your work! :)

overcome by events - openvpn 2.4 has been committed