databreach
databreach
If I understand correct, I need to do the following: 1. Ignore the [05-install-cni-plugins.sh](https://github.com/boostchicken/udm-utilities/blob/master/cni-plugins/05-install-cni-plugins.sh) script as `unifi-systemd` already includes the `CNI plugins`. 2. Trigger the [10-dns.sh](https://github.com/boostchicken/udm-utilities/blob/master/dns-common/on_boot.d/10-dns.sh) script with a `OneShot...
Thank you very much for the support so far. Unfortunately, I am unable to get it to work. As such, I have started from scratch and used your test files...
Upgrading to the beta firmware (1.10.0-12) did indeed fix it! I guess that I misread your README, thinking it was referring to
It is working as expected. For those who are interested to know how, here is how I do it. **Create CNI Macvlan** Instead of dedicating a macvlan to a single...
Hi @peacey, I upgraded to UniFi OS 1.12.22 and updated [wireguard-kmod](https://github.com/tusc/wireguard-kmod) to [wireguard-kmod-06-01-22](https://github.com/tusc/wireguard-kmod/releases/download/v06-01-22/wireguard-kmod-06-01-22.tar.Z). The wireguard tunnel is established and confirmed up and running by `wg`. However, web addresses (URL) are...
Hi @peacey, You are correct. [wireguard-kmod-06-01-22](https://github.com/tusc/wireguard-kmod/releases/download/v06-01-22/wireguard-kmod-06-01-22.tar.Z) is working fine on UniFi OS 1.12.22. It turned out the **Error 403** was caused by the wireguard configuration script of the VPN provider...
Perhaps the docker version will help. See #14.
It would be highly advantageous if you could devise a method to ensure seamless execution of "virtual-dsm" within an unprivileged LXC container, requiring no specific preconditions. The errors encountered when...
The initial script was a quick fix, altering the source code to enable "virtual-dsm" to operate within an unprivileged LXC container. However, a more refined solution has been developed, eliminating...
Thank you for merging the improved version, and I appreciate your keen observation. You're correct; the workaround for /dev/tap devices in `network.sh` was not included in this pull request. After...