Issue is migrated from GitHub
I couldn't find any release targeted for OpenSuse and I couldn't build it from source.
Related issue #33
Author (GitHub user): @ayZagen
Created: 2024年06月07日T09:26:59Z - Updated: 2025年08月28日T19:56:33Z
GitHub issue: https://github.com/OpenVPN/openvpn3-linux/issues/264
2024年06月09日T17:26:33Z - @dsommers
(seems my comment here got lost ... so re-writing it)
OpenSUSE and SUSE distributions is currently not on our list of officially supported distributions in the project. The reason is that there has been very few requests for it and we don't have too much resources to available to do proper QA on even more distributions. The biggest demands has been in the Debian, Fedora, RHEL/CentOS and Ubuntu scopes. Since CentOS is no longer what it used to be, we are moving towards CentOS Stream - as it's close enough to Fedora/RHEL.
That said ... if there are OpenSUSE or SUSE package maintainers willing to look into packaging OpenVPN 3 Linux for that distribution, I will happily support and help them get that task done. But I, unfortunately, do not have the capacity to bring in that distro myself at the moment.
2025年02月16日T08:54:26Z - @sajonCC
Hi,
I will be very happy to see a package for OpenSUSES as well. However, with instruction given on this git, you can easily build it from source.
@ayZagen if you need help with building openvpn from source. Let me know. I can try to help you with it.
2025年05月09日T18:41:05Z - @jtourlamain
Some people created a build of this repo on the build service of OpenSuse (https://build.opensuse.org/search?search_text=openvpn3). The problem is that they work as smooth as on Fedora. The one from stacheldrahtje doesn't allow you to authorize (I think it has something to do with SELinux permission). The build from polyconvex allows you to authorize, but the split tunnel doesn't seem to work.
2025年05月12日T13:09:32Z - @dsommers
For split tunnel to work, it is required that you use systemd-resolved ... please check the output of openvpn3-admin init-config to get an idea of what the default configuration might be set up to use
2025年05月16日T21:51:22Z - @jtourlamain
Running sudo openvpn3-admin init-config gives:
- Detected settings will be saved to disk? No
* Checking for OpenVPN user and group accounts
Found: openvpn user - uid 455
Found: openvpn group - gid 454
* Checking OpenVPN 3 Linux state/configuration directory
Using directory: /var/lib/openvpn3
Directory found
* Logger Configuration
Configuration file: /var/lib/openvpn3/log-service.json
systemd-journald active state: active
:: Result :: Will use systemd journald for logging
!! Configuration UNCHANGED
* Network Configuration
Configuration file: /var/lib/openvpn3/netcfg.json
!! Could not connect to D-Bus
Found accessible /etc/resolv.conf
:: Result :: Will use /etc/resolv.conf
!! Configuration UNCHANGED
* Ensuring SELinux file labels are correct
- SELinux status: Enforcing mode
I ran the SELinux configs:
# semodule -i /etc/openvpn3/selinux/openvpn3.pp
# semanage boolean --m --on dbus_access_tuntap_device
It's also strange that I can import a config file like
openvpn3 config-import --config ~/myvpn.ovpn --name myvpn --persistent
but once restarted the openvpn3 configs-list is empty (on fedora the config is persisted)
2025年05月18日T19:41:55Z - @dsommers
* Network Configuration
Configuration file: /var/lib/openvpn3/netcfg.json
!! Could not connect to D-Bus
These lines indicates that it could not connect to the systemd-resolved service (aka org.freedesktop.resolve1).
Regarding SELinux - There are also 2 SELinux policies needed. I haven't looked at the openSUSE packaging, but all other distros uses /usr/share/selinux/packages as the destination for installation. There should be two policies here: openvpn3.pp.bz2 and openvpn3_service.pp.bz2 (both are compressed, semodule can handle these compressed policies out-of-the-box).
The first one just gives you an SELinux boolean you need to enable - dbus_access_tuntap_device (which you already did); this allows the D-Bus daemon/broker to pass file descriptors over D-Bus. The openvpn3-service-netcfg service is the process creating the tun/dco interfaces and configures them, and passes a file descriptor to the openvpn3-service-client so it can pass network traffic to the tun device or handle the data channel encryption keys for the DCO interfaces.
The second policy handles the process context transition and grants the openvpn3-service-netcfg and openvpn3-service-client the needed permissions to operate properly. In practice this policy confines these two processes into separate process contexts.
In regards to the openvpn3 config-import not working as expected is odd. Again, you can try to start this service manually and see if it behaves as expected ...
# /usr/libexec/openvpn3-linux/openvpn3-service-configmgr --log-level 6 --log-file stdout: --idle-exit 0 --state-dir /var/lib/openvpn3/configs
Also, what's the output of openvpn3-admin version --services?
2025年05月21日T14:19:02Z - @wfrisch
gdbuspp, the only openvpn3-linux dependency not yet packaged for openSUSE, is now on its way to our main repository.
https://build.opensuse.org/requests/1279060
As soon as the remaining bugs have been ironed out, it shouldn't be a problem to get openvpn3-linux itself into openSUSE Tumbleweed as well.
Thanks for all your efforts so far.
*Issue is migrated from GitHub*
------
I couldn't find any release targeted for OpenSuse and I couldn't build it from source.
Related issue [#33](https://github.com/OpenVPN/openvpn3-linux/issues/33)
------
Author (GitHub user): **[@ayZagen](https://github.com/ayZagen)**
Created: **2024年06月07日T09:26:59Z** - Updated: **2025年08月28日T19:56:33Z**
GitHub issue: https://github.com/OpenVPN/openvpn3-linux/issues/264
## COMMENTS
> **[2024年06月09日T17:26:33Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2156708253) - [@dsommers](https://github.com/dsommers)**
>
> (seems my comment here got lost ... so re-writing it)
>
> OpenSUSE and SUSE distributions is currently not on our list of officially supported distributions in the project. The reason is that there has been very few requests for it and we don't have too much resources to available to do proper QA on even more distributions. The biggest demands has been in the Debian, Fedora, RHEL/CentOS and Ubuntu scopes. Since CentOS is no longer what it used to be, we are moving towards CentOS Stream - as it's close enough to Fedora/RHEL.
>
> That said ... if there are OpenSUSE or SUSE package maintainers willing to look into packaging OpenVPN 3 Linux for that distribution, I will happily support and help them get that task done. But I, unfortunately, do not have the capacity to bring in that distro myself at the moment.
-----
> **[2025年02月16日T08:54:26Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2661327896) - [@sajonCC](https://github.com/sajonCC)**
>
> Hi,
>
> I will be very happy to see a package for OpenSUSES as well. However, with instruction given on this git, you can easily build it from source.
>
> @ayZagen if you need help with building openvpn from source. Let me know. I can try to help you with it.
-----
> **[2025年05月09日T18:41:05Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2867592581) - [@jtourlamain](https://github.com/jtourlamain)**
>
> Some people created a build of this repo on the build service of OpenSuse (https://build.opensuse.org/search?search_text=openvpn3). The problem is that they work as smooth as on Fedora. The one from stacheldrahtje doesn't allow you to authorize (I think it has something to do with SELinux permission). The build from polyconvex allows you to authorize, but the split tunnel doesn't seem to work.
-----
> **[2025年05月12日T13:09:32Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2872514456) - [@dsommers](https://github.com/dsommers)**
>
> For split tunnel to work, it is required that you use `systemd-resolved` ... please check the output of `openvpn3-admin init-config` to get an idea of what the default configuration might be set up to use
-----
> **[2025年05月16日T21:51:22Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2887736181) - [@jtourlamain](https://github.com/jtourlamain)**
>
> Running `sudo openvpn3-admin init-config` gives:
>
> ```
> - Detected settings will be saved to disk? No
>
> * Checking for OpenVPN user and group accounts
> Found: openvpn user - uid 455
> Found: openvpn group - gid 454
>
> * Checking OpenVPN 3 Linux state/configuration directory
> Using directory: /var/lib/openvpn3
> Directory found
>
> * Logger Configuration
> Configuration file: /var/lib/openvpn3/log-service.json
> systemd-journald active state: active
> :: Result :: Will use systemd journald for logging
> !! Configuration UNCHANGED
>
> * Network Configuration
> Configuration file: /var/lib/openvpn3/netcfg.json
> !! Could not connect to D-Bus
> Found accessible /etc/resolv.conf
> :: Result :: Will use /etc/resolv.conf
> !! Configuration UNCHANGED
>
> * Ensuring SELinux file labels are correct
> - SELinux status: Enforcing mode
> ```
>
> I ran the SELinux configs:
>
> ```
> # semodule -i /etc/openvpn3/selinux/openvpn3.pp
> # semanage boolean --m --on dbus_access_tuntap_device
> ```
>
> It's also strange that I can import a config file like
>
> ```
> openvpn3 config-import --config ~/myvpn.ovpn --name myvpn --persistent
> ```
> but once restarted the openvpn3 configs-list is empty (on fedora the config is persisted)
-----
> **[2025年05月18日T19:41:55Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2889173211) - [@dsommers](https://github.com/dsommers)**
>
> ```
> * Network Configuration
> Configuration file: /var/lib/openvpn3/netcfg.json
> !! Could not connect to D-Bus
> ```
> These lines indicates that it could not connect to the `systemd-resolved` service (aka `org.freedesktop.resolve1`).
>
> Regarding SELinux - There are also 2 SELinux policies needed. I haven't looked at the openSUSE packaging, but all other distros uses `/usr/share/selinux/packages` as the destination for installation. There should be two policies here: `openvpn3.pp.bz2` and `openvpn3_service.pp.bz2` (both are compressed, `semodule` can handle these compressed policies out-of-the-box).
>
> The first one just gives you an SELinux boolean you need to enable - `dbus_access_tuntap_device` (which you already did); this allows the D-Bus daemon/broker to pass file descriptors over D-Bus. The `openvpn3-service-netcfg` service is the process creating the tun/dco interfaces and configures them, and passes a file descriptor to the `openvpn3-service-client` so it can pass network traffic to the `tun` device or handle the data channel encryption keys for the DCO interfaces.
>
> The second policy handles the process context transition and grants the `openvpn3-service-netcfg` and `openvpn3-service-client` the needed permissions to operate properly. In practice this policy confines these two processes into separate process contexts.
>
>
> In regards to the `openvpn3 config-import` not working as expected is odd. Again, you can try to start this service manually and see if it behaves as expected ...
>
> # /usr/libexec/openvpn3-linux/openvpn3-service-configmgr --log-level 6 --log-file stdout: --idle-exit 0 --state-dir /var/lib/openvpn3/configs
>
> Also, what's the output of `openvpn3-admin version --services`?
-----
> **[2025年05月21日T14:19:02Z](https://github.com/OpenVPN/openvpn3-linux/issues/264#issuecomment-2898146298) - [@wfrisch](https://github.com/wfrisch)**
>
> `gdbuspp`, the only openvpn3-linux dependency not yet packaged for openSUSE, is now on its way to our main repository.
> https://build.opensuse.org/requests/1279060
>
> As soon as the remaining bugs have been ironed out, it shouldn't be a problem to get `openvpn3-linux` itself into openSUSE Tumbleweed as well.
>
> Thanks for all your efforts so far.