Is the OpenVPN plugin still on hold/cancelled for OMV6?
Did you read post #2 on this thread? I have used openvpn in docker and see little reason a plugin is needed.
Is there a reason why openvpn has been abandoned?
Because it was a painful plugin to maintain. Feel free to maintain it.
wireguard is 100x more complext to setup than open vp
As someone who has worked extensively on the openvpn plugin and the author of the wireguard plugin, you have this backwards.
bruteforce protection already built in
It's an app on Nextcloud and need to be installed and activated.
I also have it on NC since day 1, 😉
Thank you for the above explanation on fail2ban.
Need to read more on it.
Did you read post #2 on this thread? I have used openvpn in docker and see little reason a plugin is needed.
Because it was a painful plugin to maintain. Feel free to maintain it.
As someone who has worked extensively on the openvpn plugin and the author of the wireguard plugin, you have this backwards.
From a programmer perspective Wireguard may be more convenient, but as someone who has setup plenty of remote servers over the years, I am talking as user or admin person.
OpenVPN takes 10 minutes and we never ever got Wireguard to connect properly.
Maybe its our setup but I would have though its all very standard. We have a file server behind a firewall and want to use VPN for 2 tasks:
1) access files on the server from outside via VPN.
2) manage all maintenance tasks on all internal hosts remotely. That means access all configuration GUI screens (like OMV GUI and Docker, Portainer etc) and SSH into hosts remotely (via VPN).
The Firewall has port forwarding to the VPN server and OpenVPN has an option to allow traffic to other hosts as well. Thats one tick and all we need. In 10 minutes it works. Wireguard never worked when installed under Linux and windows clients.
Apart from the fact that Wireguard is more difficult to setup (and as I mentioned we never got it to work), is it a lot of work to convert Openvpn? It is so widely used and I can contribute resources if thats the issue.
Did you read post #2 on this thread? I have used openvpn in docker and see little reason a plugin is needed.
Because it was a painful plugin to maintain. Feel free to maintain it.
As someone who has worked extensively on the openvpn plugin and the author of the wireguard plugin, you have this backwards.
It does not work using OpenVPN inside Docker as it is such a basic access tool. If I want to log into the servers behind my firewall and maybe need to repair docker or any other component, I cannot have the access gate (OpenVPN) depend on Docker.
Docker is good for server applications not for network access apps.
Maybe its our setup but I would have though its all very standard. We have a file server behind a firewall and want to use VPN for 2 tasks:
1) access files on the server from outside via VPN.
2) manage all maintenance tasks on all internal hosts remotely. That means access all configuration GUI screens (like OMV GUI and Docker, Portainer etc) and SSH into hosts remotely (via VPN).
we never got it to work
Configuring wireguard on docker or on the host doesn't matter. I have tried many different configurations and they have always worked for me. But if you prefer the host here is a detailed howto to configure it. Ask me what you want, I will answer you with pleasure.
Thanks. I will look at it an give it a try.
Docker is good for server applications not for network access apps.
I disagree since I use docker for network access but evidently it doesn't work for you. For the people who do not want to use docker, we used to recommend OpenvpnAS. It is one package to install and then configure from its web interface. It is hard to justify maintaining a plugin that I don't use and when only one person needs it. The other option is configure openvpn on your router. pfsense, ipfire, and many commercial routers have an option to do this. chente and I have put a ton of time into the wireguard plugin but it isn't ready yet.
"I disagree since I use docker for network access"
So how do you access you servers remotely if Docker goes down?
So how do you access you servers remotely if Docker goes down?
multiple ssh ports on different servers with keys only (password auth disabled) running on a non-standard ports. docker has a daemon but I've never seen it crash and neither has my guacamole container I use for remote access. I'm not allowed to use vpn clients at work. I am allowed to use ssh and web browsers.
How do you access your servers if openvpn isn't working?
Docker is just another stack of risk added. The chance that something breaks in a Docker setup with containers etc etc is much much greater than running a simple Linux application that's been around for 30 years. OpenVPN like SSH or SMB. They will not go down. Docker is whole stack of complexity. Docker is great for running big, non critical applications.
I have OpenVPN on 3 physically separate servers (just to be sure). It's a simple Linux app and easily installed. Running multiple instances is easy to maintain.
In my whole life I have never seen a crashed docker container lol.
what would be the preferred selection?
For docker, https://hub.docker.com/r/haugene/transmission-openvpn is very good (100million+ pulls). I know it has transmission but don't use it if you don't need it. Otherwise, wait a bit for the wireguard plugin. I also suggested install openvpnas. No plugin needed for that. Or someone other than me can port the openvpn plugin.
Or someone other than me can port the openvpn plugin.
or try pivpn. very easy
thanks.
Does that run on Debian or needs Pi Os?
Don’t have an account yet? Register yourself now and be a part of our community!
