Have been following a members' posts about using the Pi as a Wifi Repeater and/or Bridge and also bridging via openvpn. A member of this forum (Ingo) has provided awesome step-by-step instructions with the use of systemd-networkd with the setup and the device has worked flawlessly with OpenVPN.
I'm hoping that I could get something similar as "How to bridge an access point with a remote network by openvpnOpenVPN?" post , but with Wireguard instead. With the reason being that openvpnOpenVPN is getting recognised these days and blocked / throttled.
I'm unfortunately very new to the raspberry pi and linux, so the step-by-step instructions seen previously (like the ones' provided by Ingo). Would be awesome to help in my learning process.
Wireguard is still considered experimental by the owner of the code (this is mainly noted to be due to awaiting 3rd party audits and reviews), but considering that this is being implemented by quite a few VPN providers after conducting their own reviews and audits. I'm hoping that it is able to serve in the setup with systemd-networkd on Raspbian with an RPi.
Hopefully I can get some help with this.
Update with info from comments:
What I'm trying to do is similar How to bridge an access point with a remote network by openvpn?. But to use wireguard instead of openvpn and the side I am trying to set-up is the client side.
Further to elaborate, I'd like to use the RPi wherever I go and it would connect to my home server (through the wireguard connection) and allow anything connected to the client RPi (through the Wifi Access Point or Ethernet port) to connect back to my home server.
Further Update with additional details added from comments and discussions: As Ephemeral raised, this setup does not provide end-to-end security, the tunnel will only be secure from the server to the RPi client and any extra measures and risks should be taken for clients connecting to the RPi WAP.
In summary, I'm looking for the RPi to provide a secure tunnel through to the Wireguard server at home (or any other remote location). And thus allowing anything that connects to the RPi through a WAP (setup on the RPi) and/or through the wired ethernet port will have access to the server and it's services remotely.
Links for reference info:
