Hello,
recently, I've come across this test comparing OpenVPN vs. SSH
tunnelling:
http://blog.backslasher.net/ssh-openvpn-tunneling.html
so natutally, I guess it would be interesting to perform similar
test cases in a Kronosnet - OpenVPN duel so that the expectations
are set for "VPN on steroids" and perhaps the limitations are
identified if the results are too far from "on par".
(Just saying, not doing, I wouldn't go too far in tweaking
kronosnet for the best results possible, I'm afraid).
--
Jan (Poki)
All,
We are pleased to announce the second public release candidate of
kronosnet v1.0 - which we are calling v0.9
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features ability to use multiple
links between nodes, active/active and active/passive link failover
policies, automatic link recovery, FIPS compliant encryption (nss and/or
openssl), automatic PMTUd and in general better performances compared to
the old network protocol.
The source tarballs can be downloaded here:
https://www.kronosnet.org/releases/
Upstream resources and contacts:
https://kronosnet.org/https://github.com/kronosnet/kronosnet/https://ci.kronosnet.org/https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/usershttps://lists.kronosnet.org/mailman/listinfo/develhttps://lists.kronosnet.org/mailman/listinfo/commits
Known issues in this release:
* Knet will fail to work on Fedora 26 arm when built with clang. This is
a known issue with clang compiler that is fixed in more recent
versions of clang.
* Knet will fail to build with clang on rhel7 + epel version of clang.
This is a known issue with clang compiler that is fixed in more recent
versions of clang.
* Applications performing configuration changes might experience a long
waiting time when calling into the knet API. This is a known
interaction issue between the PMTUd thread inside knet and external
API locking.
https://trello.com/c/uPMjKRYy/847-fix-pmtud-locking-with-external-api
* Running the knet test suite with valgrind (make check-memcheck) will
fail with Debian Experimental glibc due to a known bug in valgrind.
* Running the knet test suite with valgrind on FreeBSD is no longer
supported. The valgrind version on FreeBSD is too old and generates
too many false positives. Also, please refer to build-aux/check.mk on
how to use valgrind in combination with knet. Some platforms requires
extra options to work properly.
Cheers,
The knet developer team
