From 76d0b11d280e66c96d1aa2b47bd8c41539e3ced7 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:32:26 -0600 Subject: [PATCH 01/14] vault backup: 2024-05-19 10:32:26 --- IT/RouterOS port forwarding.md | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 IT/RouterOS port forwarding.md diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md new file mode 100644 index 0000000..7020615 --- /dev/null +++ b/IT/RouterOS port forwarding.md @@ -0,0 +1,2 @@ +To port forward with rout +1. Navigate to IP > Firewall > Nat From 37b4ef60e767c8b765a89336163a02f9121f6348 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:33:26 -0600 Subject: [PATCH 02/14] vault backup: 2024-05-19 10:33:26 --- IT/RouterOS port forwarding.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index 7020615..fd084dc 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,2 +1,3 @@ -To port forward with rout -1. Navigate to IP > Firewall > Nat +To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward the port +1. Navigate to IP > Firewall > NAT, select Add New +2. From 0e2c7431b808c882db8e3afac858b03546585c3a Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:34:26 -0600 Subject: [PATCH 03/14] vault backup: 2024-05-19 10:34:26 --- IT/RouterOS port forwarding.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index fd084dc..c540552 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,3 +1,4 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward the port -1. Navigate to IP > Firewall > NAT, select Add New -2. +1. Navigate to IP > Firewall > NAT, select `Add New` +2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` +3. Set `Dst. Port` to ` From 31770e62dd24670626f7d66df52b3c8cec123360 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:35:26 -0600 Subject: [PATCH 04/14] vault backup: 2024-05-19 10:35:26 --- IT/RouterOS port forwarding.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index c540552..9f1995d 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,4 +1,7 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward the port 1. Navigate to IP > Firewall > NAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` -3. Set `Dst. Port` to ` +3. Set `Dst. Port` to the port you want to forward +4. Set `In. Interface List` to `WAN` +5. Set `Action` to `dst-nat` +6. Set `To Addresses` to the internal IP From e590bdfc31fc610f4b5b5dc35e4f1a247ded8a76 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:36:26 -0600 Subject: [PATCH 05/14] vault backup: 2024-05-19 10:36:26 --- IT/RouterOS port forwarding.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index 9f1995d..4650bce 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,7 +1,10 @@ -To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward the port +To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic +# Allow through th 1. Navigate to IP > Firewall > NAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` 3. Set `Dst. Port` to the port you want to forward 4. Set `In. Interface List` to `WAN` 5. Set `Action` to `dst-nat` -6. Set `To Addresses` to the internal IP +6. Set `To Addresses` to the internal IP you want the traffic to go to +7. (Optionally) add a comment explaining what you're doing + From 2f9af4c60cb072f8d97e1ca7f22a6ef098f9d618 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:37:26 -0600 Subject: [PATCH 06/14] vault backup: 2024-05-19 10:37:26 --- IT/RouterOS port forwarding.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index 4650bce..0af6870 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,5 +1,7 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic -# Allow through th +# Allow through the firewall +1. Set `Dst. Address` to the internal IP you want to forw +# Forward traffic 1. Navigate to IP > Firewall > NAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` 3. Set `Dst. Port` to the port you want to forward From 3cdb60324a66ea4640f83f6791c9b64ed52ebb19 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:38:26 -0600 Subject: [PATCH 07/14] vault backup: 2024-05-19 10:38:26 --- IT/RouterOS port forwarding.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index 0af6870..a274eef 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,6 +1,9 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic # Allow through the firewall -1. Set `Dst. Address` to the internal IP you want to forw +1. Set `Dst. Address` to the internal IP you want to allow traffic to +2. Set `Protocol` to `6 (tcp)` +3. Set `Dst. Port` to the port you want to allow traffic through +4. Set `In. Interface List` to `all` (I'm sure this isn't the corre) # Forward traffic 1. Navigate to IP > Firewall > NAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` From cf465146f65883995ce63d2f5e4e1332b85b0d58 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:39:26 -0600 Subject: [PATCH 08/14] vault backup: 2024-05-19 10:39:26 --- IT/RouterOS port forwarding.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index a274eef..f69753c 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,9 +1,12 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic # Allow through the firewall -1. Set `Dst. Address` to the internal IP you want to allow traffic to -2. Set `Protocol` to `6 (tcp)` -3. Set `Dst. Port` to the port you want to allow traffic through -4. Set `In. Interface List` to `all` (I'm sure this isn't the corre) +1. +2. Set `Dst. Address` to the internal IP you want to allow traffic to +3. Set `Protocol` to `6 (tcp)` +4. Set `Dst. Port` to the port you want to allow traffic through +5. Set `In. Interface List` to `all` (I'm sure this isn't the most correct option), but it works +6. Set `Action` to `accept` +7. (Optionally) add a comment expaianin # Forward traffic 1. Navigate to IP > Firewall > NAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` From 953ad123973be03d3481594b7e28d8acf2275a46 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:40:26 -0600 Subject: [PATCH 09/14] vault backup: 2024-05-19 10:40:26 --- IT/RouterOS port forwarding.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index f69753c..0c1e9e0 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,14 +1,15 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic # Allow through the firewall -1. -2. Set `Dst. Address` to the internal IP you want to allow traffic to -3. Set `Protocol` to `6 (tcp)` -4. Set `Dst. Port` to the port you want to allow traffic through -5. Set `In. Interface List` to `all` (I'm sure this isn't the most correct option), but it works -6. Set `Action` to `accept` -7. (Optionally) add a comment expaianin +1. Navigate to IP > Firewall from the sidebar, then go to the Filter Rules tab from the top +2. Select Add new +3. Set `Dst. Address` to the internal IP you want to allow traffic to +4. Set `Protocol` to `6 (tcp)` +5. Set `Dst. Port` to the port you want to allow traffic through +6. Set `In. Interface List` to `all` (I'm sure this isn't the most correct option), but it works +7. Set `Action` to `accept` +8. (Optionally) add a comment explaining what you're doing # Forward traffic -1. Navigate to IP > Firewall > NAT, select `Add New` +1. Navigate to IP > Firewall from the sidebar, then go to the FilteNAT, select `Add New` 2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` 3. Set `Dst. Port` to the port you want to forward 4. Set `In. Interface List` to `WAN` From 9cec159e822f2f8484eb1a0c3b45b3db4e7c8a73 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:41:27 -0600 Subject: [PATCH 10/14] vault backup: 2024-05-19 10:41:27 --- IT/RouterOS port forwarding.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/IT/RouterOS port forwarding.md b/IT/RouterOS port forwarding.md index 0c1e9e0..5eea73b 100644 --- a/IT/RouterOS port forwarding.md +++ b/IT/RouterOS port forwarding.md @@ -1,7 +1,7 @@ To port forward with RouterOS, you need allow the port through the firewall, *and* actually forward traffic # Allow through the firewall 1. Navigate to IP > Firewall from the sidebar, then go to the Filter Rules tab from the top -2. Select Add new +2. Select `Add New` to create a new rule 3. Set `Dst. Address` to the internal IP you want to allow traffic to 4. Set `Protocol` to `6 (tcp)` 5. Set `Dst. Port` to the port you want to allow traffic through @@ -9,11 +9,12 @@ To port forward with RouterOS, you need allow the port through the firewall, *an 7. Set `Action` to `accept` 8. (Optionally) add a comment explaining what you're doing # Forward traffic -1. Navigate to IP > Firewall from the sidebar, then go to the FilteNAT, select `Add New` -2. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` -3. Set `Dst. Port` to the port you want to forward -4. Set `In. Interface List` to `WAN` -5. Set `Action` to `dst-nat` -6. Set `To Addresses` to the internal IP you want the traffic to go to -7. (Optionally) add a comment explaining what you're doing +1. Navigate to IP > Firewall from the sidebar, then go to the NAT tab from the top +2. Select `Add New` to create a new rule +3. Set `Chain` to `dstnat`, set `Protocol` to `6 (tcp)` +4. Set `Dst. Port` to the port you want to forward +5. Set `In. Interface List` to `WAN` +6. Set `Action` to `dst-nat` +7. Set `To Addresses` to the internal IP you want the traffic to go to +8. (Optionally) add a comment explaining what you're doing From 61f4e01802946cf02b4c3ab5881d9a8e4e737eeb Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:55:06 -0600 Subject: [PATCH 11/14] vault backup: 2024-05-19 10:55:06 --- IT/Making nginx forward VPN and https traffic on tcp 443.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/IT/Making nginx forward VPN and https traffic on tcp 443.md b/IT/Making nginx forward VPN and https traffic on tcp 443.md index 9d7dd7d..35a8ea3 100644 --- a/IT/Making nginx forward VPN and https traffic on tcp 443.md +++ b/IT/Making nginx forward VPN and https traffic on tcp 443.md @@ -53,4 +53,7 @@ arc@apollo-vm:/etc/nginx$ sudo ip addr show enX0 The server now starts without issue. -After going through that headache, I now believe that we're back to square 1, and we have 2 IPs that both need to listen externally on 443. \ No newline at end of file +After going through that headache, I now believe that we're back to square 1, and we have 2 IPs that both need to listen externally on 443. + +# Outcome +I ended up spinning u \ No newline at end of file From 80cf75661a883d43b67ad7add54e272743fe87a0 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:56:06 -0600 Subject: [PATCH 12/14] vault backup: 2024-05-19 10:56:06 --- .../Making nginx forward VPN and https traffic on tcp 443.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename IT/{ => Troubleshooting}/Making nginx forward VPN and https traffic on tcp 443.md (98%) diff --git a/IT/Making nginx forward VPN and https traffic on tcp 443.md b/IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md similarity index 98% rename from IT/Making nginx forward VPN and https traffic on tcp 443.md rename to IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md index 35a8ea3..abf88d9 100644 --- a/IT/Making nginx forward VPN and https traffic on tcp 443.md +++ b/IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md @@ -56,4 +56,4 @@ The server now starts without issue. After going through that headache, I now believe that we're back to square 1, and we have 2 IPs that both need to listen externally on 443. # Outcome -I ended up spinning u \ No newline at end of file +I ended up spinning up a new openvpn server on TCP/3389 for RDP \ No newline at end of file From a735dfe1eb66c343ed45661d8d69af8b067c42e2 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:57:07 -0600 Subject: [PATCH 13/14] vault backup: 2024-05-19 10:57:07 --- .../sudo unable to resolve host after hostname change.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename IT/{ => Troubleshooting}/sudo unable to resolve host after hostname change.md (100%) diff --git a/IT/sudo unable to resolve host after hostname change.md b/IT/Troubleshooting/sudo unable to resolve host after hostname change.md similarity index 100% rename from IT/sudo unable to resolve host after hostname change.md rename to IT/Troubleshooting/sudo unable to resolve host after hostname change.md From 7e27c3cb88100b984c88079fa73657702dcb08fa Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:58:07 -0600 Subject: [PATCH 14/14] vault backup: 2024-05-19 10:58:07 --- IT/{ => Deployment docs}/Deploying Hydra.md | 0 IT/{ => Deployment docs}/Deploying PiVPN to a debian instance.md | 0 IT/{ => Deployment docs}/Deploying Syncthing.md | 0 .../Deploying pihole-docker to a brand new Debian instance.md | 0 4 files changed, 0 insertions(+), 0 deletions(-) rename IT/{ => Deployment docs}/Deploying Hydra.md (100%) rename IT/{ => Deployment docs}/Deploying PiVPN to a debian instance.md (100%) rename IT/{ => Deployment docs}/Deploying Syncthing.md (100%) rename IT/{ => Deployment docs}/Deploying pihole-docker to a brand new Debian instance.md (100%) diff --git a/IT/Deploying Hydra.md b/IT/Deployment docs/Deploying Hydra.md similarity index 100% rename from IT/Deploying Hydra.md rename to IT/Deployment docs/Deploying Hydra.md diff --git a/IT/Deploying PiVPN to a debian instance.md b/IT/Deployment docs/Deploying PiVPN to a debian instance.md similarity index 100% rename from IT/Deploying PiVPN to a debian instance.md rename to IT/Deployment docs/Deploying PiVPN to a debian instance.md diff --git a/IT/Deploying Syncthing.md b/IT/Deployment docs/Deploying Syncthing.md similarity index 100% rename from IT/Deploying Syncthing.md rename to IT/Deployment docs/Deploying Syncthing.md diff --git a/IT/Deploying pihole-docker to a brand new Debian instance.md b/IT/Deployment docs/Deploying pihole-docker to a brand new Debian instance.md similarity index 100% rename from IT/Deploying pihole-docker to a brand new Debian instance.md rename to IT/Deployment docs/Deploying pihole-docker to a brand new Debian instance.md