damn. the script starts after networking but it is likely networking up simply initializes networking and doesn't wait for it to be accessible.
Will have to modify script to make sure we have network access before mounting.
My fault apparently the file must be named /lib/systemd/system/mount-network-shares.service I also made a careless mistake in the script, mount is in /bin not in /sbin to fix my blunders sudo mv /lib/systemd/system/mount-network-shares /lib/systemd/system/mount-network-shares.service sudo sed -i 's/...
That data is most certainly encrypted. In-fact even most useless web-traffic is encrypted nowadays.
Sorry but if you want to spy on your sister you will have to do it the old fashioned way and read her diary
actually never mind the init.d script since the new raspian uses systemd might as well use it write to /lib/systemd/system/mount-network-shares.service [Unit] Description=mount network shares After=systemd-networkd-wait-online.service Requires=systemd-networkd-wait-online.service [Service] Type=simp...
My guess is that mount runs before network is up thus it is not accessible try placing the follwoing script in /etc/init.d/mount-samba #! /bin/sh ### BEGIN INIT INFO # Required-Start: $local_fs $syslog $remote_fs dbus # Default-Start: 3 4 5 # Default-Stop: # Short-Description: mount smb shares # Des...
Do as bls suggests, and test without vpn.
If that works than the problem is that traffic is coming in from the router and going out of the vpn creating a asynchronous chain.
If that's what's happening than we will need to mark packets and add a separate routing rule table
hmm there doesn't seem to be anything obviously wrong.
Lets see whats working and whats not.
From client (assuming windows) open cmd.exe
ping -n 2 192.168.4.1
ping -n 2 220.127.116.11
tracert -d 18.104.22.168