Update README.md

This commit is contained in:
2026-06-07 11:35:36 +01:00
parent 5a9c4cbd44
commit 2c94c4fd7a

View File

@@ -8,7 +8,7 @@ Though secure, this imposes the obvious limitation of only being able to access
While maintaining security, and exposing my network as little as possible, I desired a reliable and minimalistic way to access these resources when away from home.
For this task, WireGuard's cryptography, asymmetric key-paring and minimal overhead provided the perfect solution.
For this task, WireGuard's cryptography, asymmetric key-pairing and minimal overhead provided the perfect solution.
## Architecture
@@ -49,11 +49,11 @@ For this task, WireGuard's cryptography, asymmetric key-paring and minimal overh
- Support for Dynamic home IP addresses via [BashDDNS](https://git.tobiastime.xyz/Tobias/BashDDNS), and specifying a domain name as the endpoint for the client
- Lightweight, with a dedicated virtual machine requiring less than 256MBs of RAM
- Lightweight, with a dedicated virtual machine requiring less than 256MB of RAM
- Secure through WireGuard's dual-key asymmetric [cryptography](https://www.wireguard.com/protocol/)
- Automated and unattended security updates keeping the underlying virtual machine patched
- Automated, unattended security updates keep the underlying virtual machine patched
## Notes for playbook and automated deployment
@@ -85,7 +85,7 @@ A typical client configuration is:
- Server Public Key, Allowed IPs (10.10.10.0/31, LAN IP range), Endpoint:51820, Persistent Keep Alive 25 seconds
Persistent keep alive will send a dummy packet every 25 seconds to maintain a connection, useful for when you are roaming with a mobile device that is subject to frequent IP change.
Persistent Keep Alive will send a dummy packet every 25 seconds to maintain a connection, useful for when you are roaming with a mobile device that is subject to frequent IP change.
## Extremely useful Linux tools in debugging