selfhosted
/
coder
mirror of https://github.com/coder/coder.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix(docs/networking/stun): convert svg diagrams to png

This commit is contained in:
Cian Johnston 2024-02-12 17:27:53 +00:00 committed by GitHub
parent 2fabc9499a
commit ec25fb8bbc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
9 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/images/networking/stun1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 85 KiB

1
docs/images/networking/stun1.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 6.7 KiB

BIN
docs/images/networking/stun2.1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 54 KiB

1
docs/images/networking/stun2.1.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
docs/images/networking/stun2.2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 49 KiB

1
docs/images/networking/stun2.2.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
docs/images/networking/stun3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 108 KiB

1
docs/images/networking/stun3.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 17 KiB

8
docs/networking/stun.md
View File

@ -66,7 +66,7 @@ In this example, both the client and agent are located on the network
direction, both client and agent are able to communicate directly with each direction, both client and agent are able to communicate directly with each
other's locally assigned IP address. other's locally assigned IP address.
![Diagram of a workspace agent and client in the same network](../images/networking/stun1.svg) ![Diagram of a workspace agent and client in the same network](../images/networking/stun1.png)
### 2. Direct connections with one layer of NAT ### 2. Direct connections with one layer of NAT
@ -75,12 +75,12 @@ to each other over the public Internet. Both client and agent connect to a
configured STUN server located on the public Internet to determine the public IP configured STUN server located on the public Internet to determine the public IP
address and port on which they can be reached. address and port on which they can be reached.
![Diagram of a workspace agent and client in separate networks](../images/networking/stun2.1.svg) ![Diagram of a workspace agent and client in separate networks](../images/networking/stun2.1.png)
They then exchange this information through Coder server, and can then They then exchange this information through Coder server, and can then
communicate directly with each other through their respective NATs. communicate directly with each other through their respective NATs.
![Diagram of a workspace agent and client in separate networks](../images/networking/stun2.2.svg) ![Diagram of a workspace agent and client in separate networks](../images/networking/stun2.2.png)
### 3. Direct connections with VPN and NAT hairpinning ### 3. Direct connections with VPN and NAT hairpinning
@ -121,4 +121,4 @@ addresses on the corporate network from which their traffic appears to
originate. Using these internal addresses is much more likely to result in a originate. Using these internal addresses is much more likely to result in a
successful direct connection. successful direct connection.
![Diagram of a workspace agent and client over VPN](../images/networking/stun3.svg) ![Diagram of a workspace agent and client over VPN](../images/networking/stun3.png)