OpenVPN not routing traffic ?

Dustii · 23 August 2016 16:48

Hi there !

Today I flashed the dietpi software on my raspberry pi sd card, after the initial setup (changing eth0 to a static ip) I installed the openvpn package through the dietpi launcher.

Everything seems to go well, after the reboot the openvpn service is running and I can retrieve the .opvn thanks to FTP.

So I checked out the software page (Openvpn) and I changed the remote line to remote my WAN-IPP 1194

The 3 ports that are named on the software page are opened and pointed towards the pi’s ip address.

When I load up the .ovpn on my phone for example it connects without a problem however it doesn’t seem that the traffic is being routed through openvpn connection. My phones WAN ip stays the same and I can’t ping/access any local shares/websites.

Does someone have an idea what could be wrong ?

k-plan · 23 August 2016 17:33

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:

github.com

Fourdee/DietPi/blob/master/dietpi/dietpi-software#L6166


      
          				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

github.com

Fourdee/DietPi/blob/master/dietpi/dietpi-software#L6240


      
          				Download_Install "$(curl -sSfL 'https://api.github.com/repos/airsonic-advanced/airsonic-advanced/releases' | mawk -F\" '/"browser_download_url": .*\/airsonic\.war"/{print $4}' | head -1)" /mnt/dietpi_userdata/airsonic/airsonic.war
          			fi
          
          			# User
          			Create_User -g dietpi -G audio -d /mnt/dietpi_userdata/airsonic airsonic
          
          			# Optimise memory limit
          			local memory_limit=$(( $RAM_PHYS / 5 ))
          			(( $memory_limit < 200 )) && memory_limit=200
          
          			# Service
          			cat << _EOF_ > /etc/systemd/system/airsonic.service
          [Unit]
          Description=Airsonic-Advanced (DietPi)
          Wants=network-online.target
          After=network-online.target remote-fs.target
          
          [Service]
          SyslogIdentifier=Airsonic
          User=airsonic
          WorkingDirectory=/mnt/dietpi_userdata/airsonic

cu
k-plan

Dustii · 23 August 2016 17:43

Thanks for the reply !

This seems kinda complicated hehe, and google translate doesn’t work that well on the german part hehe.