K. Egevang and P. Francis. The IP Network Address Translator (NAT). Internet Engineering Task Force, May 1994. RFC 1631. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Modular Components for Network Address Translation - Kohler, Morris, Poletto (2000) (Correct)
....Section 6 analyzes its performance. Section 7 discusess related work, and Section 8 concludes. 2 Network address translation Network address translation was originally designed to help ease the demand for IP addresses. For a set of machines on a local network, RFC 1631 style, or Basic , NAT [5] reserves both a large set of private IP addresses and a small set of public IP addresses. Each machine gets a permanent private IP address; local machines can communicate with one another using these addresses. However, they cannot directly communicate with the Internet at large, where the ....
....the translator assigns that machine a public IP address from the local machine 10.0.0.4 NAT gateway remote machine 18.26.4.44 s=10.0.0.4 d=18.26.4.44 s=18.26.4.44 d=10.0.0.4 s=64.55.139.202 d=18.26.4.44 s=18.26.4.44 d=64.55. 139.202 Figure 1 Basic NAT, as described in RFC 1631 [5]. The local machine has a private IP address. When it sends packets to an Internet host, the NAT gateway assigns it an address from a public address pool and rewrites the packets accordingly. Replies are rewritten to use the original private IP address. pool. It rewrites the IP packet to use this ....
[Article contains additional citation context not shown here]
K. Egevang and P. Francis. The IP Network Address Translator (NAT). RFC 1631, Internet Engineering Task Force, May 1994. ftp://ftp.ietf.org/rfc/rfc1631. txt.
Flexible Control of Parallelism in a Multiprocessor PC Router - Chen, Morris (2001) (8 citations) (Correct)
....hosts packets from Internet packets to internal hosts packets to Internet Figure 8: A Network Address Translator (NAT) configuration. 5. 4 NAT Performance Figure 8 shows a configuration fragment that, when inserted into the IP router configuration, implements a network address translator [9]. The router sends packets from inside hosts to external destinations to the upper right input port of the IPRewriter [15] The IPRewriter changes these packets source IP addresses to an externally visible address, rewrites the source TCP port numbers, and emits them out the lowerright output ....
K. Egevang and P. Francis. The IP network address translator (NAT). RFC 1631, Internet Engineering Task Force, May 1994. ftp://ftp.ietf.org/rfc/rfc1631.txt.
The Click Modular Router - Kohler (2000) (64 citations) (Correct)
....among other applications. This demonstrates how the Click framework and its design methodology can inspire novel and flexible solutions to real routing problems. Firewalls, load balancers, address port translators, and transparent proxies each act as network address translators, or NATs [15, 45, 46]. A network address translator modifies passing packets network addresses and, optionally, their port numbers, or even data to achieve some network level goal, such as allowing many machines to share a limited number of IP addresses. The network address translators we consider can examine ....
K. Egevang and P. Francis. The IP Network Address Translator (NAT). RFC 1631, Internet Engineering Task Force, May 1994. ftp://ftp. ietf.org/rfc/rfc1631.txt.
Probable Plaintext Cryptanalysis of the IP Security Protocols - Steven Bellovin (1997) (7 citations) (Correct)
....on the outside) 16 24 bits per address can be predicted. The use of CIDR block addressing [FLYV93] makes this even more likely. It would seem desirable, then, to use arbitrary addresses for machines behind the firewall, and rely on application gateways [CB94] or network address translators [FE94] to conceal this data. A note of caution is indicated here, though; addresses can leak in many ways, and it is hard to close all such channels. 4.2 Probable Plaintext in the TCP Header Because the TCP and UDP headers can follow either the replay counter or an IP header, we cannot analyze them in ....
P. Francis and K. Egevang. The IP network address translator (nat). Request for Comments (Informational) RFC 1631, Internet Engineering Task Force, May 1994.
Probable Plaintext Cryptanalysis of the IP Security Protocols - Steven Bellovin (1997) (7 citations) (Correct)
....machines on the outside) 16 24 bits per address can be predicted. The use of CIDR block addressing [16] makes this even more likely. It would seem desirable, then, to use arbitrary addresses for machines behind the firewall, and rely on application gateways [11] or network address translators [15] to conceal this data. A note of caution is indicated here, though; addresses can leak in many ways, and it is hard to close all such channels. 4.2. Probable Plaintext in the TCP Header Because the TCP and UDP headers can follow either the replay counter or an IP header, we cannot analyze them ....
P. Francis and K. Egevang. The IP network address translator (nat). Request for Comments (Informational) RFC 1631, Internet Engineering Task Force, May 1994.
The Impact of False Sharing on Shared Congestion - Management Srinivasa Aditya (2001) (Correct)
No context found.
K. Egevang and P. Francis. The IP Network Address Translator (NAT). Internet Engineering Task Force, May 1994. RFC 1631.
True Anonymity without Mixes - Molina-Jimenez, Marshall (2001) (Correct)
No context found.
K. Egevang and P. Francis. The IP network address translator (NAT). RFC 1631, The Internet Engineering Task Force, May 1994. available at: http://www.rfc-editor.org/.
The Impact of False Sharing on Shared Congestion Management - Akella, Balakrishnan (2001) (8 citations) (Correct)
No context found.
K. Egevang and P. Francis. The IP Network Address Translator (NAT). Internet Engineering Task Force, May 1994. RFC 1631.
Modular Components for Network Address Translation - Eddie Kohler Robert (2000) (Correct)
No context found.
K. Egevang and P. Francis. The IP Network Address Translator (NAT). RFC 1631, Internet Engineering Task Force, May 1994. ftp://ftp.ietf.org/rfc/rfc1631.txt.
Traffic Aware Policy-based Internet Routing - Lorensen (2003) (Correct)
No context found.
K. Egevang and P. Francis. The IP network address translator (NAT). RFC 1631, Internet Engineering Task Force, May 1994.
Towards Virtual Networks for Virtual Machine Grid Computing - Sundararaj, Dinda (2004) (8 citations) (Correct)
No context found.
EGEVANG, K., AND FRANCIS, P. The ip network address translator (nat). Tech. Rep. RFC 1631, Internet Engineering Task Force, May 1994.
Towards Virtual Networks for Virtual Machine Grid Computing - Sundararaj, Dinda (2003) (8 citations) (Correct)
No context found.
EGEVANG, K., AND FRANCIS, P. The ip network address translator (nat). Tech. Rep. RFC 1631, Internet Engineering Task Force, May 1994.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC