From ddc3247db96f431f11ef1c8470afb84310f40fc7 Mon Sep 17 00:00:00 2001 From: Giulio Date: Fri, 25 Jun 2021 16:17:12 +0200 Subject: [PATCH] Cosmetic fixes --- Readme.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/Readme.md b/Readme.md index 7b0f59d..138d21b 100644 --- a/Readme.md +++ b/Readme.md @@ -132,14 +132,15 @@ Of course `expire=` and `comment=` are optional fields. ### Proposal chart ###### The main distinction between internal and external port forwarding is: - * _Internal_ resolves only 's + * _Internal_ resolves only '<appvm>'s '<ntvm> * _External_ recursively resolves all upstream networking vm and sets forwarding rules on all of them ###### This should cover multiple scenarios: - * _Standard external forwarding_ when service needs to be exposed on a physical interface - * _Standard internal forwarding_ when service needs to be exposed to other connected to the same - * _VPN internal port forwarding_ when service needs to be exposed through a VPN + + * _Standard external forwarding_ when '<appvm> service needs to be exposed on a physical interface + * _Standard internal forwarding_ when '<appvm> service needs to be exposed to other '<appvm2/3/4> connected to the same '<netvm> + * _VPN internal port forwarding_ when '<appvm> service needs to be exposed through a VPN It is important to note that in the last case, it is just a standard case of internal forwarding. @@ -203,11 +204,12 @@ iptables -w -I INPUT 5 -d -p tcp --dport -m conntrack - ## Extra ### Useful Commands + ``` # +# ``` -``` ### Dev Environment Currently developing on VMWare Workstation on Windows due to issues in virtualizing on linux on my home hardware. QubesOS is virtualized behind NAT and can reach Windows Host via SSH.