Hello Dustii,
OpenVPN not routing traffic ?
That’s correct. Default it is configured as a End-to-End-VPN / Host-to-Host-VPN / Remote-Desktop-VPN.
You are able to manage your DietPi device, but nothing more.
One possible solution is using NAT: OpenVPN general usage
If you can read a little bit German: Configuaration issue OpenVPN (German)
Our you can have a look in DietPi VPN installation code:
G_EXEC mkdir -p /mnt/dietpi_userdata/adguardhome
G_EXEC cp -a AdGuardHome/. /mnt/dietpi_userdata/adguardhome/
G_EXEC rm -R AdGuardHome
fi
# Unbound: Switch port to 5335 if it was installed before, else it got just configured within its install step above
if (( ${aSOFTWARE_INSTALL_STATE[182]} == 2 )) && grep -q '^[[:blank:]]*port:[[:blank:]][[:blank:]]*53$' /etc/unbound/unbound.conf.d/dietpi.conf
then
G_DIETPI-NOTIFY 2 'Configuring Unbound to work for AdGuard Home'
grep '^[[:blank:]]*nameserver[[:blank:]]' /etc/resolv.conf | grep -qvE '[[:blank:]]127.0.0.1(:53)?$' || echo 'nameserver 9.9.9.9' >> /etc/resolv.conf # Failsafe
G_CONFIG_INJECT 'port:[[:blank:]]' ' port: 5335' /etc/unbound/unbound.conf.d/dietpi.conf
G_CONFIG_INJECT 'interface:[[:blank:]]' ' interface: 127.0.0.1' /etc/unbound/unbound.conf.d/dietpi.conf
G_EXEC systemctl restart unbound
fi
# User
Create_User -d /mnt/dietpi_userdata/adguardhome adguardhome
# Config
if [[ ! -f '/mnt/dietpi_userdata/adguardhome/AdGuardHome.yaml' ]]
then
and
cu
k-plan