Editing Remote Access

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
[[Category:Management]][[Category:Security]]
[[Category:Management]][[Category:Security]]
{{Wikimedia-stub}}
{{Wikimedia-stub}}
There are two main scenarios which could be referred to as remote access; access from a remote external location into your network, and headless access to your homelab servers (e.g. if they're in the loft). For information on headless access see the [[Headless Access]] article.
There are two main scenarios which could be referred to as remote access; access from a remote external location into your network, and headless access to your homelab servers (e.g. if they're in the loft). For information on headless access see the [[Headless Access]] article.
== Introduction ==
== Introduction ==
For many people, remote access is not important as you predominantly use the lab from home in your free time, but for others remote access is critical. Some example use cases for remote access are described below.
For many people, remote access is not important as you predominantly use the lab from home in your free time, but for others remote access is critical. Some example use cases for remote access are described below.
== Use Cases ==
== Use Cases ==
The use cases for remote access to your homelab include:
The use cases for remote access to your homelab include:
Line 9: Line 12:
* The homelab as a cheap dev/test environment, because your employer is too mean to pay for a proper one! Many people use their homelabs for testing out work solutions and issues prior to implementing them on live systems.
* The homelab as a cheap dev/test environment, because your employer is too mean to pay for a proper one! Many people use their homelabs for testing out work solutions and issues prior to implementing them on live systems.
* Your homelab is actually hosted in a location other than your home, for example if your employer provides you with rack space, or you use a colocation environment
* Your homelab is actually hosted in a location other than your home, for example if your employer provides you with rack space, or you use a colocation environment
== Solutions ==
== Solutions ==
Solutions include, but are not limited to the following:
Solutions include, but are not limited to the following:
Line 28: Line 32:
|https://openvpn.net/
|https://openvpn.net/
|Comes available as a standard installable download for Linux, or a ready-to-use OVA licensed for two concurrent users!
|Comes available as a standard installable download for Linux, or a ready-to-use OVA licensed for two concurrent users!
|-
|Software
|[[WireGuard]]
|https://www.wireguard.com
|A very lightweight, yet powerful and fast, open source VPN. Clients available for Windows, Mac, Linux, iOS, Android, and many other systems. Can be a bit tricky to initially setup.
|-
|-
|HW Router
|HW Router
Please note that all contributions to Project Homelab may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Project Homelab:Copyrights for details). Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)

Template used on this page: