Cosmetic fixes
This commit is contained in:
parent
aa3473e71f
commit
ddc3247db9
12
Readme.md
12
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 <appvm>'s <ntvm>
|
||||
* _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 <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
|
||||
|
||||
* _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 <appvm_ip> -p tcp --dport <target_port> -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.
|
||||
|
Loading…
Reference in New Issue
Block a user