Remote Access: Difference between revisions
Jump to navigation
Jump to search
openhomelab>The vmonkey |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| 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 12: | Line 9: | ||
* 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 32: | Line 28: | ||
|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 | ||
Latest revision as of 04:16, 16 July 2021
This article is a stub. You can help The Open Homelab project by expanding it.
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[edit | edit source]
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[edit | edit source]
The use cases for remote access to your homelab include:
- You use your homelab as a gateway to provide remote access to your home network
- 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
Solutions[edit | edit source]
Solutions include, but are not limited to the following:
| Category | Product | Link | Notes |
|---|---|---|---|
| Software | Windows RDS | RDP Web Access | Built into Windows! Extra flexibility and security can be provided through RD Web Access. |
| Software | OpenVPN | https://openvpn.net/ | 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 | Draytek | https://www.draytek.com/ | If you want to do it in hardware, the Draytek home routers are the defacto standard for awesome routers which have built in VPN capabilities. Recommended models include Draytek Vigor 2925 (all variants),Y,Z |
| HW Router | Netgear | https://www.Netgear.com/ | Alternative hardware, the Netgear home routers are good routers which have built in VPN capabilities. A particular good one is the D6400 due to universal usage across ADSL/VDSL/Cable or any Ethernet service) Although, to note, a lot of the Netgear router use OpenVPN for the VPN Feature - it is limited to TAP type and not TUN - so Android and iOS support not supported. *This might change with new firmwares |