8000 chore(docs): add requirements re ports and stun server to docs by johnstcn · Pull Request #12026 · coder/coder · GitHub
[go: up one dir, main page]

Skip to content

chore(docs): add requirements re ports and stun server to docs #12026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Feb 12, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestions from code review
Co-authored-by: Spike Curtis <spike@coder.com>
  • Loading branch information
johnstcn and spikecurtis authored Feb 12, 2024
commit 4b4d24616d82870fce324a53bc0e07127e07f49f
4 changes: 2 additions & 2 deletions docs/networking/stun.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
>
> [Network Address Translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation)
> is commonly used in private networks to allow multiple devices to share a
> single public IP address. The vast majority of ISPs today use at least one
> single public IP address. The vast majority of home and corporate internet connections use at least one
> level of NAT.

## Overview
Expand Down Expand Up @@ -43,7 +43,7 @@ At a high level, STUN works like this:
configured STUN servers. These STUN servers are generally located on the
public internet, and respond with the public IP address and port from which
the request came.
- **Port Mapping:** The client and agent then exchange this information through
- **Coordination:** The client and agent then exchange this information through
the Coder server. They will then construct packets that should be able to
successfully traverse their counterpart's NATs successfully.
- **NAT Traversal:** The client and agent then send these crafted packets to
Expand Down
0