Differences
This shows you the differences between two versions of the page.
| en:cgnat_description [2017/03/09 15:41] – created aalekseenko | en:cgnat_description [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | === CGNAT === | ||
| - | |||
| - | Network Address Translation and Port allows you to share a public IPv4 address for several subscribers and extend the use of the limited IPv4 address space. | ||
| - | |||
| - | === RFC === | ||
| - | |||
| - | Complies with industry standards, as specified in RFC 6888, RFC 4787. | ||
| - | |||
| - | === Full Cone === | ||
| - | |||
| - | Provides transparent operation of peer-to-peer protocols (torrents, games). | ||
| - | |||
| - | === Paired IP address pooling === | ||
| - | |||
| - | Subscriber sessions are tied to a single external IP address for the subscriber. | ||
| - | |||
| - | === Hairpinning === | ||
| - | |||
| - | Subscribers inside NAT interact with each other without address translation. | ||
| - | |||
| - | === Limits === | ||
| - | |||
| - | For each pool of IP addresses individually set a limit on the number of TCP and UDP connections for the user to allow the operator to allocate resources sparingly address space between corporate and private clients. | ||
| - | In the absence of activity, unused connections close, releasing ports. | ||
| - | |||
| - | === NAT flows export === | ||
| - | |||
| - | Network flows information are recorded in a text file or transferred to an external collector by the IPFIX protocol (Also known as NetFlow v10). | ||