CN2579098Y - IPV9/IPV4NAT routing devices - Google Patents

Abstract

The utility model discloses an IPV9/IPV4 NAT router. IPV9/IPV4NAT router domain name gateway, file transfer gateway, and routing are connected to the interface of the application and transport layer, and then connected in series with the transport layer, protocol, and address translation manager, IPV9 protocol stack, static dynamic mapping, protocol translator, and IPV4 protocol The stack is connected to the address translation manager, the static and dynamic mapping, and the protocol translator are connected to the address pool, the IPV9 protocol stack and the IPV4 protocol stack are connected to the network interface, and the network interface, and the protocol translator is connected to the IPV9 protocol stack. The management interface connects with routing and address pools. The utility model transparently realizes the protocol address translation, realizes the normal communication between the IPv9 and IPv4 hosts in the internal network and the external Intemet; solves the communication problems between the IPv9 and IPv4 private networks and the Internet, and the communication problems between different protocols in the transition stage. It will play a role in promoting the smooth transition to the next generation network.

Description

IPV9/IPV4NAT Router

Technical field

The utility model relates to the technical field of computer network communication, in particular to an IPV9/IPV4NAT router.

Background technique

The IPV4 protocol was born in the 1970s and is a very successful Internet protocol. However, with the explosion or growth of the www network and the wide application of various services, the limitations and serious shortcomings of IPV4 are exposed: 1) IP addresses are about to be exhausted ; There are only ^2.32 or 4 billion addresses. In addition, the United States has an unreasonable classification of IP addresses. The crisis of IP address shortage in countries other than the United States is even more serious. 2) Due to the uneven development of the Internet, the address allocation of IPv4 is uneven. Continuous IPv4 addresses are physically discontinuous, which makes it impossible to use routing cascading, which directly leads to the rapid expansion of the routing table of Internet backbone routers, seriously affecting the performance of network connections. 3) The IPV4 protocol lacks security; 4) IPV4 lacks QOS support, which seriously hinders real-time multimedia applications; 5) Automatic address configuration is very troublesome and difficult to plug and play; 6) IPV4 and IPV6 are not independent intellectual property rights of my country, and the agreement is formulated by the United States , Network security control is in the hands of others.

In order to build my country's independent, safe and controllable IPV9 Internet network, the utility model proposes IPV9/IPV4 NAT routing method technology and device, and solves the smooth migration of the access from the IPV9 network to the IPV4 network and the Internet during the transition period.

Contents of Invention

The purpose of the utility model is to provide an IPV9/IPV4NAT router.

IPV9/IPV4NAT router domain name gateway, file transfer gateway, and routing are connected to the interface of the application and transport layer, and then connected in series with the transport layer, protocol, and address translation manager, IPV9 protocol stack, static dynamic mapping, protocol translator, and IPV4 protocol The stack is connected to the address translation manager, the static and dynamic mapping, and the protocol translator are connected to the address pool, the IPV9 protocol stack and the IPV4 protocol stack are connected to the network interface, and the network interface, and the protocol translator is connected to the IPV9 protocol stack. The management interface connects with routing and address pools.

The utility model has the advantages of:

1) The NAT router is located adjacent to the internal private network and the external Internet, transparently implements protocol address translation between the two ends of the communication, and realizes the normal communication between the internal network IPv9 and IPv4 hosts and the external Internet;

2) The introduction of NAT routers makes the IPv9 experimental network and IPv4 private network interconnected with the current Internet backbone network based on IPv4 protocol, which solves the communication problems between IPv9, IPV4 private network and Internet, and the communication between different protocols in the transition stage question. It will play a role in promoting a smooth transition to the next generation network;

3) Realize the two-way conversion of protocol, address and port of IPV9/IPV4 hybrid private network (or private network). Realize edge to realize border routing;

4) Realize the address conversion from the IPV4 private network to the public network. Make the IPV4 network securely protected. As an IP address to filter access to the firewall.

Description of drawings

Fig. 1 is a schematic block diagram of IPV9NAT-router architecture;

Figure 2 is a schematic block diagram of the system.

Detailed ways

IPV9/IPV4NAT router domain name gateway 1, file transfer gateway 2, and route 14 are connected to the application and transport layer interface 3, and then sequentially connected to the transport layer 4, protocol, address translation manager 5, IPV9 protocol stack 6, static dynamic mapping 7. The protocol translator 8 and the IPV4 protocol stack 9 are connected to the address translation manager 5 in parallel, the static dynamic mapping 7 and the protocol translator 8 are connected to the address pool 10 in parallel, and the IPV9 protocol stack 6 and the IPV4 protocol stack 9 are connected in parallel The network interface 12, the network interface 13, the protocol translator 8 are connected to the IPV9 protocol stack 6, and the user management interface 11 is connected to the router 14 and the address pool 10.

As shown in Figure 1, the figure

1) Domain name gateway (DNS-ALG): complete domain name query, address, protocol conversion, etc.

2) File transfer gateway (FTP-ALG): complete file transfer address, protocol conversion, etc.

3) Application and transport layer interface (SOCKET layer): realize the interface between the application layer and the TCP/UDP layer;

4) Transport layer (TCP/UDP layer): Complete the transport layer protocol conversion function,

5) Protocol and address translation manager (Ipv9/IPv4 Translation Manager): manage task allocation of modules 21 and 22, etc.;

6) IPV9 protocol stack: realize IP version 9 protocol functions;

7) Dynamic mapping: through the NA(P)T-PT Ipv9/IPv4 mapping table, implement the address dynamic mapping function;

8) Protocol translator: realize ICMP4 and ICMP9, IP4 and IP9 address and packet header conversion function between IPv4 and Ipv9 protocols;

9) IPV4 protocol stack; realize IP version 4 protocol functions;

10) Address pool: IPV4 and IPV9 addresses, maintain system IPv4 and IPV9 addresses, and realize dynamic and static address conversion;

11) User management interface: configure static and dynamic addresses and ports. Configure routing.

12), 13) Network interface layer (data link and physical layer).

14) Routing: Realize the border routing function.

As shown in Figure 2, the utility model application realizes that the network is divided into three areas: 1). 15, 16 form the public network area; 2). 21, 22, 23, 24 form the private network area private.com; 3) .17, 18, 19, and 20 form the external network area external.com.

The area where the public networks 15 and 16 are located is the global IPV4 address space, 15 is the root DNS server, and 16 is the IPV4 public network.

The address space of the private network (21, 22, 23, 24) adopts Ipv9 and IPV4 private addresses, so the address of the private network is still inaccessible to the public network (external network). 22 and 23 are IPV9 hosts. Host 22 address is to use IPV9 address 1015[6]100/32, domain name is 22.private.com, 24 is the DNS server of private.com domain, can interpret the IPV9 or IPV4 domain name host address of this domain.

17, 18, 19, and 20 are external.com. domain address spaces, which are configured as IPV4 hosts, and 18 and 19 are IPV4 hosts. The public network address used by host 18 is 171.68.10.1, and the domain name is 18.external.com. 20 is the DNS server of the external.com. domain, which can explain the IPV4 domain name host address of this domain.

17 and 21 are IPV9NAT routers, which integrate encapsulation/decapsulation, bidirectional NAT and DNS_ALG, FTP_ALOG functions. Provides IPV9 and IPV4 address pools. 20 and 24 are DNS servers in private domains, which implement static address mapping with IPV4 public network areas 15 and 16 through IPV9NAT_routers.

Communication operation principle process description:

The following describes in turn how to achieve communication between hosts in each domain, which involves encapsulation/decapsulation, NAT, DNS_ALG and other technologies.

A. The working process of the IPV9 host 22 initiating communication to the IPV4 host 18: the IPV9 network host 22 accesses the external network IPV4 host 18

1) The host 22 sends a UDP-based domain name query message to query 24 for the IP address corresponding to the domain name 18.External.com.

2) local domain name server 24 inquires to root domain name server 15 by 21, and the source address of inquiry message is 171.68.2.1 (this address is the IP of local domain name server 24), destination address is 11.1.1.1. 21NAT reports to IP and UDP The address of the header is converted. The source address becomes 131.108.1.8, and the destination address remains unchanged. DNS_ALG does not modify the packet payload.

3) The root DNS server 15 instructs 24 to query 20 . The public network address 171.68.1.1 of 20 is given in the response message. When the message passes through 21, 21NAT converts the destination addresses in the IP and UDP headers: from 131.108.1.8 to 171.68.2.1, and the source address 11.1.1.1 remains unchanged.

In addition, the NDS_ALG on 21 should replace the public IP address 171.68.1.1 of 20 given in the response message. DNS_ALG first asks NAT to assign a private address for 171.68.1.1, assuming 10.10.1.1. Then DNS_ALG replaces 171.68.1.1 in the DNS packet payload with 10.10.1.1.

4) In this way, the address of 20 known by 24 is 10.10.1.1. 24 queries 20 for the IP address of 18.External.com. The IP source address of the request packet is 171.68.2.1, and the destination address is 10.10.1.1. After the packet is converted by NAT of 21, the source address becomes 131.108.1.8, and the destination address becomes 171.68.1.1.

DNS_ALG does not modify the payload of DNS packets.

5) 20 responds to the query giving the IP address 171.68.10.1 of 18.External.com. When the response passes through 21, NAT converts the IP and UDP headers accordingly: the source address changes from 171.68.1.1 to 10.10.1.1, and the destination address changes from 131.108.1.8 to 171.68.2.1.

And DNS_ALG requests NAT to map an internal address for 171.68.10.1, assuming 10.11.1.2. DNS_ALG replaces the address of 18.External.com in the reply message with 10.11.1.2.

6) 24 replies to host 22. Gives 18.External.com an address of 10.11.1.2.

7) Host 22 initiates a session with host 18. The source address of the packet is 1015[6]100/32, and the destination address is 10.11.1.2. When passing through 21, NAT maps a public network address for the internal address 1015[6]100/32, assuming it is 131.108.1.17.

And convert the address of the header: the source address becomes 131.108.1.17, and the destination address becomes 171.68.10.1. At this time, the NAT establishes address mappings for the host 22 and the host 18 respectively. Communication is established between the hosts 22 and 18.

Table 1. Address mapping table during a connection the host internal address public address twenty two 1015[6]100/32 131.108.1.17 (Dynamic NAT) 18 10.11.1.2 (Dynamic NAT) 171.68.10.1 twenty four 171.68.2.1 131.108.1.8 (static NAT) 20 10.10.1.1 (Dynamic NAT) 171.68.1.1

B. The steps for the host 18 to initiate communication with the host 22: the external network 18 host accesses the internal network host 22

1) 18 queries the domain name server 20 for the IP address corresponding to 22.Private.com.

2) 20 turns to the root domain name server 15 to inquire. 15 replies and instructs 20 to query 24. The public network address 131.108.1.8 of 24 is given in the response message.

3) 20 queries 24 for the IP address of 22.Private.com. In the IP header of the request message, the destination address is 131.108.1.8 of the public network address of 24, and the source address is 171.68.10.1 of the public network address of 20. When passing through NAT router 21, NAT replaces the destination address with 171.68.2.1 according to the static mapping set for 24; at the same time, the public network address 171.68.1.1 with NAT 20 applies for a mapped internal address, assuming it is 10.10.1.1, and then replaces the reported The source address of the header is 10.10.1.1.

4) 24 responds to the query, giving 22's IP address 1015[6]100/32. When the response passes 21, NAT converts the IP header address: the source address changes from 171.68.2.1 to 131.108.1.8, and the destination address changes from 10.10.1.1 to 171.68.1.1. DNS_ALG requests NAT to map a public network address for the internal IPV9 address 1015[6]100/32, assuming it is 131.108.1.17, and DNS_ALG replaces the address 1015[6]100/32 of 22 in the response message with 131.108.1.17.

5) 20 replies to host 18. The IP translation address given 22 is 131.108.1.17.

6) The host 18 initiates communication to the host 22 . The source address of the IP packet is 171.68.10.1, and the destination address is 131.108.1.17. When the packet passes through 21, NAT applies for an internal mapping address for the external address 171.68.10.1, assuming it is 10.10.1.1. Then address translation: the source address becomes 10.10.1.1, and the destination address becomes 1015[6]100/32.

So far, address mappings have been established on 21 for hosts 22 and 18 respectively.

Claims (1)

1. IPV9/IPV4NAT router, it is characterized in that domain name gateway (1), file transfer gateway (2), route (14) be attempted by use go up with transport layer interface (3) after successively with transport layer (4), agreement, address translation manager (5) serial connection, IPV9 protocol stack (6), static dynamically mapping (7), protocol translator (8), IPV4 protocol stack (9) is attempted by on the address translation manager (5), static dynamically mapping (7), protocol translator (8) is attempted by on the address pool (10), IPV9 protocol stack (6), IPV4 protocol stack (9) is attempted by network interface (12), network interface (13), protocol translator (8) is joined with IPV9 protocol stack (6), and subscriber administration interface (11) joins with route (14) and address pool (10).