Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=6
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’ - Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 0 - Kernel version |
uname --all
Linux raspi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux - Architecture |
dpkg --print-architecture
arm64 - SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
RPi4 - Power supply used | (EG: 5V 1A RAVpower)
Official - SD card used | (EG: SanDisk ultra)
N/A
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
Wireguard - Was the software title installed freshly or updated/migrated?
Old install, but the issue has existed ever since the first install - Can this issue be replicated on a fresh installation of DietPi?
Haven’t checked
← If you sent a “dietpi-bugreport”, please paste the ID here → - Bug report ID |
echo $G_HW_UUID
Steps to reproduce
- Change
/etc/wireguard/wg0.conf’sPostUporPostDowntotouch /tmp/a, or to/etc/wireguard/postup.sh, in which the script would contain said touch command - Restart WireGuard server
Expected behaviour
- /tmp/a gets created, or in the case of a script, it is not executed
Actual behaviour
- /tmp/a does not get created, and the commands in /etc/wireguard/postup.sh don’t get ran
Extra details
- I am using wireguard-ui through docker compose/portainer to manage my config, but that’s it. Trying to manually edit the configuration also results in the same issues.
- In normal circumstances, the commands wouldn’t be a touch, but rather iptables, but in this case for the sake of simplicity I opted for a touch.