Details:
- Date | Sat Feb 4 10:11:56 CST 2023
- DietPi version | v8.13.2 (MichaIng/master)
- Image creator | DietPi Core Team
- Pre-image | from scratch
- Hardware | RPi 4 Model B (aarch64) (ID=4)
- Kernel version |
Linux DietPi 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux - Distro | bullseye (ID=6,RASPBIAN=0)
- Command |
curl -sSfLO https://www.privateinternetaccess.com/openvpn/openvpn-strong.zip - Exit code | 6
- Software title | DietPi-VPN
Steps to reproduce:
- Setup dietpi-vpn with PIA, enable auto start and killswitch
Expected behaviour:
- internet should still work
Actual behaviour:
- internet completely dies
Extra details:
I have 2 Dietpi’s in myhouse. My “main” one runs jackett, radarr, sonarr, deluge, sabnzbd, pihole, samba, unbound
My second one runs pihole and unbound
Main: hostname dietpi 192.168.86.100
Second: hostname dietpi2 192.168.86.200
After reading other posts about dietpi-vpn I set my piholes both to use cloudflare DNS instead of unbound for upstream DNS.
I’ve had Dietpi-vpn setup on my “main” forever but the killswitch never worked, the entire internet just stopped but I never had a problem so I just let it be. After complete reinstalls of Bullseye I reconfigured everything the way I like it. Then I got a DMCA notice and checked to see if the VPN was up, it was. I enabled the killswitch to check to see if it was fixed, and everything still is broken.
I went to my 2nd unit only running pihole and unbound and configured dietpi-vpn with the exact same settings and enabled the killswitch, and it still works without an issue. I feel like the VPN on my “main” isnt actually working even thought the WAN IP is listed as the VPN IP.
When the killswitch is enabled on the main I cannot even ping 8.8.8.8. When the killswitch is enabled on the secondary it pings fine.
Both units are configured in dietpi-config to use 1.1.1.1 and 1.0.0.1 for static DNS.
The “primary” is my DHCP server.
Please let me know what logs are relevant to seeing why the killswitch complete breaks my “main” but not the secondary.
Additional logs:
curl: (6) Could not resolve host: www.privateinternetaccess.com
Screenshot of the “Dietpi2” VPN config and being able to ping 8.8.8.8 with killswitch enabled
Output from “main” Dietpi after enabling killswitch and trying to ping 8.8.8.8
root@DietPi:~# dietpi-vpn
[ OK ] DietPi-VPN | systemctl enable dietpi-vpn
[ INFO ] DietPi-VPN | Checking for required APT packages: iptables
[ OK ] DietPi-VPN | chmod +x /var/lib/dietpi/dietpi-vpn/static_up.sh /var/lib/dietpi/dietpi-vpn/static_down.sh
[ OK ] DietPi-VPN | umask 0077
[ INFO ] DietPi-VPN | Generating OVPN file, please wait...
[ OK ] DietPi-VPN | cp -f /etc/openvpn/pia/us_east.ovpn /etc/openvpn/client.ovpn
[ OK ] DietPi-VPN | Desired setting in /etc/openvpn/client.ovpn was already set: proto udp
[ OK ] DietPi-VPN | sed -i /^[[:blank:]]*remote[[:blank:]]/s/[[:blank:]][0-9][0-9]*$/ 1197/ /etc/openvpn/client.ovpn
[ OK ] DietPi-VPN | umask 0022
[ OK ] DietPi-VPN | chmod 0600 /var/lib/dietpi/dietpi-vpn/settings_ovpn.conf /var/lib/dietpi/dietpi-vpn/settings_dietpi.conf /etc/openvpn/client.ovpn
[ OK ] DietPi-VPN | chown root:root /var/lib/dietpi/dietpi-vpn/settings_ovpn.conf /var/lib/dietpi/dietpi-vpn/settings_dietpi.conf /etc/openvpn/client.ovpn
[ OK ] DietPi-VPN | Setting in /etc/openvpn/client.ovpn adjusted: auth-user-pass /var/lib/dietpi/dietpi-vpn/settings_ovpn.conf
[ OK ] DietPi-VPN | Added setting script-security 2 to /etc/openvpn/client.ovpn after line auth sha256
[ OK ] DietPi-VPN | Added setting up /var/lib/dietpi/dietpi-vpn/static_up.sh to /etc/openvpn/client.ovpn after line script-security 2
[ OK ] DietPi-VPN | Added setting down /var/lib/dietpi/dietpi-vpn/static_down.sh to /etc/openvpn/client.ovpn after line up /var/lib/dietpi/dietpi-vpn/static_up.sh
[ OK ] DietPi-VPN | sed -i /^[[:blank:]]*route-up[[:blank:]]/d /etc/openvpn/client.ovpn
[ OK ] DietPi-VPN | sed -i /^[[:blank:]]*route-pre-down[[:blank:]]/d /etc/openvpn/client.ovpn
[ INFO ] DietPi-VPN | Checking for required APT packages: openvpn
[ OK ] DietPi-VPN | systemctl restart dietpi-vpn
[ OK ] DietPi-VPN | Connection established: us_east.ovpn
root@DietPi:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
One more quick note that I have been using dietpi-vpn on my main Dietpi and the VPN Status in the banner has never once showed anything other than Sent = 0MiB | Received = 0MiB. However after 15 minutes of testing yesterday on Dietpi2 and the killswitch enabled, I saw the Received = 45MiB.
