If I’m not mistaken, the AllowedIPs on b was wrong, but should have been 10.8.196.0/2410.8.0.0/16 or 10.0.0.0/8 depending on the size of the VPN network, and/or LAN IP range if you need access through the VPN to other LAN services with are not connected to the VPN.
And the Endpoint at client config needs to be the public IP or domain, not the one within the VPN network.
Also be careful with disabling IPv6 at the server. All IPv6 requests of clients will then bypass the VPN: IPv6 leaks.
Oppss, alright, thought it didn’t matter as long as they don’t have my WAN ip.
Have re-set up it again! Thank goodness there is PiVPN makes it a lot easier was manually generating the key and copy it one by one for each of my devices.
Right now everything is perfect! Thank you very much!
to arrive at 10.0.0.0/24 which will give me access of 10.0.0.1 - 10.0.0.254.
/8 will be giving me this range “10.0.0.1 - 10.255.255.254”.
I could have sticked with the usual 192.168.1.x. Switched to the 10, purely for typing a few number lesser but will not need more than 254 iPs. in my setup.
Ah that explain why local ip don’t work. Wanted to rule out is a port forwarding issue previously.
Alright, will read up more on the IPv6 leak. As of now my connection of VPN is purely connecting back home. Afraid that I will break other stuff for now.
Ah, I think I mixed it up: 10.0.0.1 - 10.0.0.254 is your LAN IP range while 10.8.196.0/24 was your VPN internal IP range? And 10.0.0.11 was the LAN IP of your VPN server? Makes sense then, with Endpoint = 10.0.0.11:51820 for testing, I guess.
Okay, however, great that it works now using PiVPN .
Ah yes! Correct!
However I do realised something, sometimes when I connect to VPN.
I won’t be able to access internet, but Data Sent will be 1.0GiB+ within the first minute. Turn off and on, and it will work again. Will monitor and see how. Might be just a first boot issue.