中文摘要
現今的網路位置已經嚴重的不足，學校，公司和企業都沒有足夠的IP 可以
使用，因此有些人提出NAT 系統來幫助解決此題。但能通過NAT 的應用程式非
常有限，而且將網路分成公眾和私人有違網路的基本分享原則。於是，IETF 提
出的IPv6，全新的協定，更健全的網路機制，最重要的是，更多的IP 位置能完
全的解決現今網路界所遇到的問題。但要讓人們從IPv4 轉換到IPv6 是非常不容
易的。大部份的使用者並不想改變現狀，所以最完美的做法是讓使用者感覺不到
轉換過程。於是，各種轉換的機制紛紛被提出.其中NAT-PT 是非常成熟且被廣泛
的實作於各種機器上的轉換器，而且使用者並不會察覺到轉換的過程。
但NAT-PT 並不能解決位置不足的問題，所以為了解決這個問題，IETF 提
出了NAPT-PT，將埠號的轉換加入NAT-PT，這樣一來就可以將一個IPv4 位置
給多個IPv6 位置使用，解決位置不足的問題。這個看似完整的機制卻無法用於
實際的網路，因為僅IPv6 到IPv4 的轉換可以使用，另一半則一直是無解的狀況。
本論文將NAPT-PT 製作的更完整，可達到雙向溝通，並實作於LINUX 作業系
統上。

3
Abstract
Nowadays, people have largely suffered the insufficient IP address, which can be
found in schools, companies, and enterprises; therefore, some people come up with
the NAT system to solve this problem. However, it is very limited for application to
pass through the NAT, and divides the Internet into public and private, which disobeys
the basic sharing principle. For this reason, IETF proposes the IPV6, the brand new
protocol, and the sound Internet system; above all, more IP addresses can completely
solve the difficulty we face in the field of the Internet. As we all know that it is
difficult to translate from the IPV4 to the IPV6 on Internet because most users don’t
want to change the status quo; hence, the perfect solution is to make users
unconscious for the transitional process. So more and more translation mechanisms
are proposed, and among them the NAT-PT, the translator, is very mature and
implemented by every kind of machine, especially, users cannot be unaware of the
process of transition.
NAT-PT still can’t overcome the problem of the inadequate addresses, so for the
purpose of solving this question, IETF proposes NAPT-PT, adding port translation to
NAT-PT, like that, one IPv4 address can map to multi-IPv6 addresses. But the
NAPT-PT in RFC 2766 only can translate packet from the IPv6 domain to the IPv4
domain, it is not usable for Internet. This thesis makes the manufacture of NAPT-PT
more complete, reaching the bi-directional communications and is implemented on
the LINUX.

Bibliography
[1] S. Deering, R. Hinden, “Internet Protocol, Version 6 (IPv6) Specification”, RFC2460, December 1998.
[2] Hagen and Silvia, “IPv6 essentials”, Oreilly, 2002.
[3] http://www.ipv6forum.com
[4] http://www.6bone.net
[5] http://www.ipv6.org.tw
[6] Stephen. A. Thomas, “IPng and the TCP/IP Protocols, Implementing the Next Generation Internet”, Wiley, 1996.
[7] Robert M.Hinden, “IP Next Generation Overview”, Communications of the ACM, Vol.39, No. 6, June 1996.
[8] K. Egevang and P. Francis, “The IP Network Address Translator”, RFC1631, May 1994.
[9] J. Bound, L. Toutain, F. Dupont, H. Afifi, and A. Durand, “Dual Stack Transition Mechanism (DSTM)”, draft-ietf-ngtrans-dstm-08.txt, July 2002.
[10] E. Nordmark, “Stateless IP/ICMP Translation Algorithm (SIIT)”, RFC2765, Februrary 2000.
[11] G. Tsirtsis and P. Srisuresh, “Network Address Translation-Protocol Translation (NAT-PT)”, RFC2766, February 2000.
[12] W. Stallings, “IPv6: the New Internet Protocol”, IEEE Communications Magazine, July 1996.
[13] H. Huang and J Ma, “IPv6 – Future Approval Networking”, WCC - ICCT 2000, 2000.
[14] T. Narten, “Neighbor Discovery and Stateless Autoconfiguration in IPv6”, IEEE Internet Computing, August 1999.
[15] P. Hallin and S. Satapati, “NAT-PT DNS ALG Solutions”, draft-hallin-natpt-dns-alg-solutions -01, July 2002.
[16] A. Durand, “IPv6 DNS transition issues”, draft-durand-ngtrans-dns-issues-00.txt, June 2002.
[17] W. Richard Stevens, “TCP/IP Illustrated”, Volume 1, Addison-Wesley, 1994.
[18] Ping-Tsai Tsai and Ying-Dar Lin, “Direct Routed Web Switch with State Migration, TCP Masquerade, and Cookie Name Rewrite”, Technical report of Department of computer and Information Science, NCTU, Taiwan, 2001.
[19] http://linas.org/linux/load.html
[20] Henrik Eriksson, Magnus Haglund, “NAPT-PT and Mobility Support in IPv6”, Lulea University of Technology Spring 2003
[21] “IXDP1200 Product Brief”, Intel Corporation, 2001.
[22] http://www.vitesse.com/products/families.cfm?family_id=5