NAT Traversal: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
Das Thema wird gerade bearbeitet. |
|||
NAT (Network Address Translation) is widely used to connect private networks to the internet. The main idea is to map several private IP addresses to only one public IP address. Having in mind that P2P network clients should be able to communicate with each other one basic question comes into mind: how can internet hosts communicate with a host in a private network? |
|||
We will first have a look at NAT itself and problems it brings. Then, we show how to traverse NATs by either changing their configuration or by using other tricks. |
|||
== |
== NAT explained == |
||
== router configuration == |
|||
Text |
|||
=== Port forwarding=== |
|||
== Probleme mit Peer-to-Peer-Anwendungen == |
|||
=== UPnP === |
|||
== Möglichkeiten der Überwindung == |
|||
| ⚫ | |||
== STUN == |
== STUN == |
||
| Line 20: | Line 21: | ||
Text |
Text |
||
== NAT |
== NAT and Voice over IP == |
||
Revision as of 23:31, 9 February 2006
Overview
NAT (Network Address Translation) is widely used to connect private networks to the internet. The main idea is to map several private IP addresses to only one public IP address. Having in mind that P2P network clients should be able to communicate with each other one basic question comes into mind: how can internet hosts communicate with a host in a private network? We will first have a look at NAT itself and problems it brings. Then, we show how to traverse NATs by either changing their configuration or by using other tricks.
NAT explained
router configuration
Port forwarding
UPnP
STUN
TURN
Hole punching
Text