On Sat, 2025-08-02 at 11:57 +0200, Jan-Espen Oversand wrote: > Hi, > > I've been the maintainer (by proxy) of net-vpn/vtun. But, as there is > no > upstream maintenance since 2016, I am afraid it is going to get > increasingly difficult to maintain. The greatest risks to maintaining > it > as far as I can see is deprecations and removals of openssl-features > and > algorithms. Quite soon it is probably going to need use-flags on > openssl > to enable deprecated algorithms. Also it has started to fall out of > other distros and operating system ports. > > So, I basically had enough, and I imported the project into github, > and > over a few weeks rewrote the codebase in rust. I have moved most of > my > own tunnel-setups to this github-project. So basically I just wanted > to > ask whether there are any opinions on whether this project (vtun-ng) > could be a viable replacement for vtun? Probably no hurry right now, > but > could possibly be considered over the next few months? > > I've uploaded ebuilds to the GURU-repository at net-vpn/vtun-ng > > Github: https://github.com/leakingmemory/vtun-ng > > > Regards, > > Jan-Espen Oversand >
Hello. I am invested in that package. And I think I'll keep a pi around with an older openssl version just for that. For like many years. Have no reason to abandon vtun coz the encryption is already done by ssh. I use vtun to feed 8 tap connections into a bond connection to parallel compress distcc stuff. One tap tun means one core compression. 8 however means multicore compression. Its like my favorite toy. I doubt I will give it up. But, I will keep an eye on your port/fork. Good luck with it. axl
