@@ -66,7 +66,7 @@ In this example, both the client and agent are located on the network
66
66
direction, both client and agent are able to communicate directly with each
67
67
other's locally assigned IP address.
68
68
69
- ![ Diagram of a workspace agent and client in the same network] ( ../images/networking/stun1.png )
69
+ ![ Diagram of a workspace agent and client in the same network] ( ../../ images/networking/stun1.png )
70
70
71
71
### 2. Direct connections with one layer of NAT
72
72
@@ -75,12 +75,12 @@ to each other over the public Internet. Both client and agent connect to a
75
75
configured STUN server located on the public Internet to determine the public IP
76
76
address and port on which they can be reached.
77
77
78
- ![ Diagram of a workspace agent and client in separate networks] ( ../images/networking/stun2.1.png )
78
+ ![ Diagram of a workspace agent and client in separate networks] ( ../../ images/networking/stun2.1.png )
79
79
80
80
They then exchange this information through Coder server, and can then
81
81
communicate directly with each other through their respective NATs.
82
82
83
- ![ Diagram of a workspace agent and client in separate networks] ( ../images/networking/stun2.2.png )
83
+ ![ Diagram of a workspace agent and client in separate networks] ( ../../ images/networking/stun2.2.png )
84
84
85
85
### 3. Direct connections with VPN and NAT hairpinning
86
86
@@ -121,7 +121,7 @@ addresses on the corporate network from which their traffic appears to
121
121
originate. Using these internal addresses is much more likely to result in a
122
122
successful direct connection.
123
123
124
- ![ Diagram of a workspace agent and client over VPN] ( ../images/networking/stun3.png )
124
+ ![ Diagram of a workspace agent and client over VPN] ( ../../ images/networking/stun3.png )
125
125
126
126
## Hard NAT
127
127
0 commit comments