Formatting
This commit is contained in:
		
							parent
							
								
									ddc3247db9
								
							
						
					
					
						commit
						a546413200
					
				| @ -132,15 +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. | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user