Added Tags to All Docs
This commit is contained in:
@@ -1,3 +1,10 @@
|
||||
---
|
||||
tags:
|
||||
- UniFi
|
||||
- Networking
|
||||
- Docker
|
||||
---
|
||||
|
||||
**Purpose**: The UniFi® Controller is a wireless network management software solution from Ubiquiti Networks™. It allows you to manage multiple wireless networks using a web browser.
|
||||
|
||||
```yaml title="docker-compose.yml"
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
tags:
|
||||
- UniFi
|
||||
- Networking
|
||||
---
|
||||
|
||||
**Purpose**:
|
||||
If you need to deploy Unifi Controller bare-metal into a virtual machine, you can do so with a few simple commands. You can feel free to reference the [original documentation](https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux) if additional clarity is needed.
|
||||
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
tags:
|
||||
- Docker
|
||||
- Macvlan
|
||||
- Networking
|
||||
---
|
||||
|
||||
**Purpose**:
|
||||
You may find that you only have one network adapter on a server / VM and need to have multiple virtual networks associated with it. For example, Home Assistant exists on the `192.168.3.0/24` network but it needs to also access devices on the `192.168.4.0/24` surveillance network. To facilitate this, we will make a MACVLAN Sub-Interface. This will make a virtual interface that is parented to the actual physical interface.
|
||||
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
tags:
|
||||
- Docker
|
||||
- Networking
|
||||
---
|
||||
|
||||
### Configure Docker Network
|
||||
We want to use a dedicated subnet / network specifically for containers, so they don't trample over the **SERVER** and **LAN** networks. If you are unsure of the name of the network adapter, in this case `eth0`, just type `ipaddr` in the terminal to list the network interfaces to locate it.
|
||||
```
|
||||
|
||||
@@ -1,3 +1,12 @@
|
||||
---
|
||||
tags:
|
||||
- Sophos
|
||||
- Firewall
|
||||
- Routing
|
||||
- LAN
|
||||
- Networking
|
||||
---
|
||||
|
||||
**Purpose**: You may have a Sophos XGS appliance and need more than one interface to act as additional LAN ports. You can achieve this with bridges.
|
||||
|
||||
!!! info "Assumptions"
|
||||
|
||||
@@ -1,3 +1,12 @@
|
||||
---
|
||||
tags:
|
||||
- Sophos
|
||||
- IPsec
|
||||
- VPN
|
||||
- Firewall
|
||||
- Routing
|
||||
---
|
||||
|
||||
**Purpose**: Generally speaking, when you have site-to-site VPN tunnels, you have to ensure that the *health* of the tunnel is operating as-expected. Sometimes VPN tunnels will report that they are online and connected, but in reality, no traffic is flowing to the remote side of the tunnel. In these instances, we can create a script that pings a device on the remote end, and if it does not respond in a timely manner, the script restart the VPN tunnel automatically.
|
||||
|
||||
!!! note "Assumptions"
|
||||
|
||||
@@ -1,3 +1,12 @@
|
||||
---
|
||||
tags:
|
||||
- Sophos
|
||||
- IPsec
|
||||
- VPN
|
||||
- Firewall
|
||||
- Routing
|
||||
---
|
||||
|
||||
**Purpose**: You may have two Sophos XGS appliances (or a mixed configuration) and need to set up a site-to-site VPN tunnel between two remote locations. You can achieve this with a simple passphrase-based IPSec VPN tunnel.
|
||||
|
||||
!!! info "Assumptions"
|
||||
|
||||
@@ -1,3 +1,12 @@
|
||||
---
|
||||
tags:
|
||||
- Sophos
|
||||
- RDP
|
||||
- SSL VPN
|
||||
- VPN
|
||||
- Firewall
|
||||
---
|
||||
|
||||
## Purpose
|
||||
This document exists to outline the generalized process to configuring remote access in a Sophos XGS Firewall to allow a VPN user to RDP into a workstation. *Setting up Remote SSL VPN Access is not covered in this document.*
|
||||
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
---
|
||||
tags:
|
||||
- Infrastructure
|
||||
- Networking
|
||||
- Index
|
||||
- Documentation
|
||||
---
|
||||
|
||||
# Networking
|
||||
## Purpose
|
||||
Network topology, addressing, firewalling, VPN, and network service dependencies.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
tags:
|
||||
- Sophos
|
||||
- iptables
|
||||
- Networking
|
||||
---
|
||||
|
||||
### IP Addresses
|
||||
Documented IP addresses of Hyper-V Failover Cluster VMs that exist behind the Sophos XG Firewall VM. All of these machines are funneled through the Sophos XG Firewall VM before they are allowed to communicate on the physical network with other devices.
|
||||
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
tags:
|
||||
- Containers
|
||||
- iptables
|
||||
- Networking
|
||||
---
|
||||
|
||||
### IP Addresses
|
||||
Documented IP addresses of containers.
|
||||
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
tags:
|
||||
- iptables
|
||||
- Networking
|
||||
- Docker
|
||||
---
|
||||
|
||||
## Overview
|
||||
All servers (physical and virtual) are documented within this specific page. They are written in a specific annotated manner in order to make them copy/paste ready for the Ansible AWX Operator server that interacts with devices in the homelab over `SSH` and `WinRM` protocols. This allows me to automate functions such as updates across the entire homelab declaratively versus individually.
|
||||
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
tags:
|
||||
- Linux
|
||||
- Networking
|
||||
---
|
||||
|
||||
**Purpose**: This is a scaffold document outlining the high level of changing an IP address of a server in either Debian or RHEL based operating systems.
|
||||
|
||||
=== "Ubuntu / Debian"
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
tags:
|
||||
- Tuya
|
||||
- Networking
|
||||
---
|
||||
|
||||
### pfSense DHCP Reservations for Tuya-Based Smart Devices
|
||||
| **Description** | **IP Address** | **MAC Address** | **Hostname** | **Device ID** | **Local Key** |
|
||||
| :--- | :--- | :--- | :--- | :--- | :--- |
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
---
|
||||
tags:
|
||||
- NetBird
|
||||
- VPN
|
||||
- Networking
|
||||
- Docker
|
||||
---
|
||||
|
||||
## Purpose
|
||||
Netbird is a free and open-source VPN server and client platform. The following document will illustrate how to deploy Netbird into a homelab or business environment.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user