WO2010102465A1 - 一种实现nat设备冗余备份的方法、装置和系统 - Google Patents

一种实现nat设备冗余备份的方法、装置和系统 Download PDF

Info

Publication number
WO2010102465A1
WO2010102465A1 PCT/CN2009/072004 CN2009072004W WO2010102465A1 WO 2010102465 A1 WO2010102465 A1 WO 2010102465A1 CN 2009072004 W CN2009072004 W CN 2009072004W WO 2010102465 A1 WO2010102465 A1 WO 2010102465A1
Authority
WO
WIPO (PCT)
Prior art keywords
ipv4
address
host
nat
nat device
Prior art date
Application number
PCT/CN2009/072004
Other languages
English (en)
French (fr)
Inventor
徐小虎
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP09841334A priority Critical patent/EP2408151A4/en
Publication of WO2010102465A1 publication Critical patent/WO2010102465A1/zh
Priority to US13/231,426 priority patent/US20120005299A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/251—Translation of Internet protocol [IP] addresses between different IP versions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, apparatus, and system for implementing redundancy backup of a NAT device. Background technique
  • IPv6 Internet Protocol version 6, Internet Protocol version 6
  • NAT-PT Network Address Translation-Protocol Translator, hereinafter referred to as a NAT device.
  • IPv4 Internet Protocol version 4, Internet Protocol Version 4
  • a host of IPv4 needs to be configured with a public IPv4 address pool (public IPv4 address pool) for translating internal IPv6 addresses into public IPv4 addresses.
  • the bit prefix (refix /96) is used to map the IPv4 address in the IPv4 network to an IPv6 address.
  • the address is called IPv4 mapped IPv6 address 0.
  • the 96-bit prefix is advertised on the IPv6 network side, and the destination address prefix is 96-bit prefix.
  • the IPv6 packet is attracted.
  • the inventor of the present invention has found that: in the current solution, whether the host adopting IPv6 accesses the IPv4 host or the IPv4 host accesses the IPv6 host on the NAT-PT does not implement the redundancy backup of the NAT device.
  • a single point of failure is prone to occur during actual use.
  • a session is originally transited through the NAT device 1. If the NAT device 1 fails, the session needs to be transferred from the NAT device 2.
  • the address mapping table of the NAT device 2 and the address mapping table of the NAT device 1 have different information, As a result, the original session will be interrupted and the connection needs to be re-initiated. That is to say, in the prior art, even if multiple NAT devices are used, the backup between multiple NAT devices cannot be implemented. Share. Summary of the invention
  • An embodiment of the present invention provides a method for implementing a network address translation NAT device redundancy backup, including:
  • Preconfiguring a fourth version of the internet protocol address pool IPv4 addres s poo 1 and a prefix pr ef i x64 for mapping the I Pv4 address to the sixth version of the Internet Protocol I Pv 6 address on at least two NAT devices; Determining a primary NAT device and a standby NAT device in the two NAT devices; the primary NAT device advertises the route corresponding to the Prefix64 in the IPv6 network, and advertises the route corresponding to the IPv4 addres s poo l on the IPv4 network ;
  • the standby NAT device processes a data packet between the source host and the destination host, where the source host and the destination host are respectively located in different IP networks.
  • Another embodiment of the present invention provides an apparatus for implementing a network address translation NAT device redundancy backup, including: a storage module, a routing information publishing module, and a data packet processing module;
  • the storage module is configured to store a configured fourth version Internet Protocol address pool IPv4 addres s pool and a prefix pref ix64 for mapping an IPv4 address to a sixth version Internet Protocol IPv6 address;
  • the route corresponding to the Pref ix64 is advertised on the IPv6 network, and the route corresponding to the IPv4 addres s pool is advertised on the IPv4 network;
  • the data packet processing module is configured to process a data packet between the source host and the destination host, where the source host and the destination host are respectively located in different IP networks.
  • a further embodiment of the present invention provides a system for implementing a network address translation NAT device redundancy backup, comprising: a first device and a second device, configuring a fourth version of the Internet protocol on the first device and the second device Address pool IPv4 addres s pool and prefix prefi X 64 for IPv4 address mapping to the sixth edition Internet Protocol IPV 6 address;
  • the primary NAT device is configured to advertise a route corresponding to the Prefix64 in an IPv6 network, and advertise a route corresponding to the IPv4 addres s pool on an IPv4 network;
  • the standby NAT device is configured to process a data packet between the source host and the destination host when the primary NAT device fails; wherein the source host and the destination host are respectively located in different IP networks.
  • the technical solution provided in the embodiment of the present invention solves the problem that when a host of an IPv4 network accesses a host of an IPv6 network or a host of an IPv4 network accesses a host of an IPv6 network, redundancy backup is implemented between multiple NAT devices.
  • FIG. 1 is a simplified schematic diagram of a system for implementing redundancy backup of a NAT device in an embodiment of the present invention
  • FIG. 2 is a simplified schematic diagram of implementing redundancy backup and load balancing among multiple NAT devices according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for implementing redundancy backup of a NAT device according to an embodiment of the present invention
  • FIG. 4 is a simplified schematic diagram of an apparatus for implementing redundancy backup of a NAT device according to an embodiment of the present invention
  • a simplified schematic diagram of a device for implementing redundant backup of a NAT device
  • FIG. 6 is a flowchart of a method for implementing redundancy backup of a NAT device according to another embodiment of the present invention.
  • FIG. 1 is a simplified schematic diagram of a system for implementing redundancy backup of a NAT device in an embodiment of the present invention.
  • NAT device 102 and NAT device 104 configure the same IPv4 addres pool and a 96-bit prefix for mapping IPv4 addresses to IPv6 addresses.
  • the Keepalive protocol determines the Mas ter (active) NAT device and the S laver (standby) NAT device from the NAT device 102 and the NAT device 104.
  • VRRP Vi r tua l Router Redundancy Protocol
  • the virtual router redundancy protocol is used to determine the sth NAT device and the slaver NAT device.
  • the VRRP protocol usually uses a multicast scheme to exchange VRRP packets. It can also be modified, for example, when there is no NAT device 102 and NAT device 104. In the case of a directly connected network segment, VRRP packets can be exchanged in unicast mode. It is assumed here that the NAT device 102 is determined as the NAT device and the NAT device 104 is the Slaver NAT device. Then the NAT device 102 issues a 96-bit prefix on the IPv6 network and simultaneously publishes the IPv4 addres pool on the IPv4 network. The NAT device 104 does not advertise the routing information in the IPv6 and IPv4 networks. Alternatively, when the NAT device 104 issues the routing information, the COST value is set to be large enough that the NAT device 102 is selected for forwarding when the packet is normally routed. .
  • the NAT device 102 and the NAT device 104 perform synchronization of the NAT address translation table.
  • the protocol may be implemented, for example, HTTP (Hypertext Transfer Protocol) or a proprietary protocol.
  • HTTP Hypertext Transfer Protocol
  • it can be synchronized in real time or periodically.
  • Host 112 an IPv6 network
  • the host 114 is located in an IPv4 network
  • the host 112 initiates a host session 114
  • the host 112 sends an IPv6 data packet
  • the destination address of the packet is an IPv4-mapping IPv6 addresses, i.e.
  • IPv 4 (Host 114)
  • IPv6 IPv6
  • the NAT device 102 converts the protocol into an IPv4 data packet through the NAT device 102.
  • the destination address of the IPv4 data packet is IPv4 (host 114), and the source address is an IPv4 address allocated by the NAT device 102 from the IPv4 addres pool.
  • the IPv4 address is referred to as IPv4 (host 112); the IPv4 packet is forwarded by the NAT device 102 to the IPv4 network, and an address translation entry is generated in the address translation table, for example:
  • IPv6 (Host 112) -> IPv4 (Host 112)
  • the above address translation entry is synchronized to the address translation table of the NAT device 104.
  • IPv4 data packet finally arrives at the host 114.
  • host 114 sends to host 112
  • An IPv4 data packet the destination address of the IPv4 data packet is IPv4 (host 112), and the source address is IPv4 (host 114), and the IPv4 data packet arrives along the IPv4 pref ix route in the IPv4 addres pool sent by the NAT device 102.
  • the NAT device 102 performs protocol conversion by the NAT device 102 to generate an IPv6 data packet.
  • the destination address of the IPv6 data packet is IPv6 (host 112), and the destination address is obtained according to the address translation entry, and the source address is 96 bits.
  • the prefix + IPv4 (host 114) the packet eventually arrives at host 112.
  • the NAT device 104 When the Mas ter NAT device and the S laver NAT device switch occur, that is, when the NAT device 104 becomes the Mas ter NAT device, if the routing information is not advertised when the NAT device 104 acts as the Slaver NAT device, the routing information is advertised at this time. If the NAT device 104 acts as a S laver NAT device, the NAT device 104 issues routing information but sets the COST value large enough, then the COST value is changed at this time. The NAT device 102 becomes a S laver NAT device, and the previously released routing information is revoked. If the NAT device 102 fails or the network connection is disconnected, its published routing information becomes invalid for other routing devices.
  • the routing information advertised by the NAT device 104 is the current best route, and the data packet communicated between the host 102 and the host 104 will be translated and forwarded by the NAT device 104, because the NAT device 104 and The address translation table has been synchronized between the NAT devices 102. Therefore, the session that has been established between the host 102 and the host 104 before the primary NAT device and the standby NAT device are switched can be translated and transferred by the NAT device 104 without appearing. Interrupted.
  • the switch between the Mas ter NAT device and the S laver NAT device refer to the VRRP protocol, and no further details are provided here.
  • FIG. 1 The embodiment shown in FIG. 1 above is described by taking the example that the host 112 first sends an IPv6 data packet to the host 114.
  • the host 114 may also first send an IPv4 data packet to the host 112.
  • the host 114 learns the IPv4 of the host 112 through the DNS (Doma in Name Service). Address, and generate an address translation entry in the NAT102 address translation table, for example: 3 ⁇ 4 port:
  • the above address translation entry is also synchronized to the address translation table of the NAT device 104.
  • the 96-bit prefix used for mapping the IPv4 address to the IPv6 address may use the 96-bit prefix, or the pref ix64-bit prefix, or other length prefix, that is,
  • the foregoing embodiment is described by taking a 96-bit prefix (denoted as pref ix/96) as an example, but is not limited to a 96-bit prefix.
  • the following embodiments are described by a pref ix64 prefix, and may also be applied to a pref ix96 prefix.
  • the Keepalive protocol may be automatically elected by the Keepalive protocol, or may be manually configured.
  • the above address translation table That is, the address mapping table, the two express one meaning. For the term unified, the address mapping table is uniformly used to describe the embodiment.
  • Another embodiment of the present invention is: when the primary NAT device and the standby NAT device switch, that is, when the NAT device 104 becomes the primary NAT device, the cold backup and the hot backup between the NAT 102 and the NAT 104 are processed. method.
  • the core idea of the cold backup is: For the source host, the IP address of the destination host on the network where the source host resides remains unchanged.
  • the core idea of the hot backup is: (1) For the source host, the destination host is at the source. The IP address of the network where the host is located remains unchanged; and (2) For the destination host, the IP address of the source host in the network where the destination host resides remains unchanged; where the source host and the destination host are in different IP networks.
  • the source host in Figure 1 is the host 112, in the IPv6 network; then the destination host is the host 114, in the IPv4 network.
  • the following describes the cold backup and hot backup in the following two scenarios: (1) a method of cold backup and hot backup when the host 112 of the I Pv 6 network accesses the host 114 of the I Pv4 network;
  • NA102 and NAT104 are configured with different IPv4 addres s pools, using the same perf ix prefix. Because the same perf ix prefix is used, for the source host, ie host 112, the destination host remains in the IP address of the network where the source host resides. Change, that is, its destination address does not change before and after NAT102 and NAT104 switchover, both pref ix64 plus the IPv4 address of the destination host, so there is no need to perform address mapping synchronization for NAT102 and NAT104; IPv4 due to NAT102 and NAT104 The addres s pool configuration is different. After the source address of the host 112 is translated by the NAT 102, the IPv4 address is different.
  • the host 112 of the IPv6 network sends the IPV6 data packet to the NAT 102, and after the address translation is performed by the NAT 102, the source address IPv6 address of the IPv6 data packet is converted into an IPV4 address (an IP4 address is assigned to the host 114 from the IPv4 addres pool), and according to The synthesized IPv6 address of the destination host is removed from its pref ix64, the generated IPv4 address, and the data packet is sent to the destination host 114 in the IPv4 network.
  • the primary NAT device (assumed to be NAT 102) and the standby NAT device (assumed to be NAT 104) are selected from the two NAT devices of a backup group by manual configuration or automatic election protocol.
  • the primary NAT device and the standby NAT device are in IPv6.
  • the routes corresponding to the prefix 64 are advertised in the network, and the routes corresponding to the respective IPv4 address pools are advertised in the IPv4 network.
  • the routes advertised by the active and standby NAT devices on the IPv6 network are all for the same prefix64.
  • the primary NAT 102 device can be used to distinguish between the primary and backup advertised Prefix64 routes to ensure that the data packet passes the primary NAT 102 under normal conditions.
  • the granularity of the route advertised by the primary NAT 102 is relatively small, and the granularity of the route advertised by the standby NAT 104 is relatively coarse; for example, the primary NAT 102 issues two routes 10.1.1.0/25 and 10.1.1.128/25, and the standby NAT 104 issues 10.1. .1.0/24—Route.
  • the primary NAT device can also issue the above route, and reserve
  • NAT only advertises its own IPv4 address pool corresponding route on the IPv4 network, and does not issue the above prefix64 route. Only when the primary NAT fails, the standby NAT becomes the new primary NAT device. The prefix64 route is issued. Using the methods described in (1) and (2), it is guaranteed that the data packet is always relayed and translated by the primary NAT device.
  • the hot backup method for the host 112 of the IP P4 network to access the host 114 of the IP v4 network is: NA102 and NAT 104 are configured with the same IPv4 addres s pool, using the same perf ix64; therefore, for the source host, ie, the host 112, The destination host does not change the IP address of the network where the source host resides, that is, its destination address does not change before and after NAT102 and NAT104 switchover; to ensure that the NAT4 and NAT104 are assigned the same IPv4 address for the same IPv6 host (NAT102 and NAT104 are configured.
  • IPv4 addres s pool The same IPv4 addres s pool, but the source host 112 may also have different IPv4 addresses in the IPv4 addres pool pool of NAT 102 and NAT 104 in the network where the destination host 114 is located. Therefore, addresses of NAT 102 and NAT 104 need to be performed. Map synchronization.
  • the host 112 of the IPv6 network sends the IPV6 data packet to the NAT 102.
  • the NAT 102 performs address translation, the source address IPv6 address of the IPv6 data packet is translated into the source IPV4 address (the IP4 address is assigned to the host 114 from the IPv4 addres s poo l).
  • the synthesized IPv6 address of the destination host the pre fi x 64 is removed, the destination IPv4 address is generated, and the translated data packet is sent to the destination host 114 in the IPv4 network.
  • the primary NAT device (assumed to be NAT 102) and the standby NAT device (assumed to be NAT 104), the primary NAT device and the standby NAT device are selected among the two NAT devices of one backup group.
  • the route corresponding to the prefix 64 is advertised in the IPv6 network, and the route corresponding to the IPv4 address pool is advertised in the IPv4 network.
  • the routes advertised by the primary and backup devices on the IPv6 network and the IPv4 network are respectively directed to the same prefix 64 and The same IPv4 address pool, in order to ensure that the data packets between the IP6 and the IPv4 network are always translated and transferred by the primary NAT device, the route can be advertised in two ways to ensure that the data packet is in normal condition.
  • translation and transfer through the primary NAT 102 In the case of translation and transfer through the primary NAT 102:
  • the granularity of the route advertised by the primary NAT 102 is relatively small, and the granularity of the route advertised by the standby NAT 104 is relatively coarse; for example, the primary NAT 102 issues two routes 10.1.1.0/25 and 10.1.1.128/25, and the standby NAT 104 issues 10.1. .1.0/24—Route.
  • the primary NAT device may also advertise the above route, and the standby NAT does not advertise the above route. Only when the primary NAT fails, the standby NAT becomes the new primary NAT device. This eliminates the need to use the methods described in (1) and (2) to ensure that packets are always relayed and translated by the primary NAT device.
  • NA102 and NAT104 are configured with the same IPv4 addres s pool, using different perf ix prefixes; for the source host, that is, host 114, the destination address is NAT 102 to assign an IP v4 address through the IPv4 addres s pool; The IP address of the network where the source host resides is always the same. Therefore, address mapping information synchronization between NAT 102 and NAT 104 is required to ensure that the same IPv6 host translates to the same IPv4 address on both NATs.
  • the source host 114 has a different IPv6 address on the network where the destination host is located, that is, the source host's IPv4 address plus the perf ix prefix is different.
  • the host 114 of the IPv4 network sends the IPV4 data packet to the NAT 102.
  • the IPv4 address of the IPv4 data packet is translated into an IPV6 address and sent to the destination host 112 in the IPv6 network.
  • the NAT 104 is generated.
  • the data packets from the host 114 to the host 112 are transited and translated by the NAT 104. Since the address mapping information is synchronized, the Pv4 address corresponding to the host 112 is the same on both NATs, so the entire switching process is transparent to the host 112.
  • the primary NAT device (assumed to be NAT102) and the standby NAT device (assumed to be NAT104) are selected among the two NAT devices in one backup group, and the primary NAT device and the standby NAT device are in IPv4.
  • the routes corresponding to the IPv4 address pool are advertised in the network, and the routes corresponding to the respective prefix64 are advertised in the IPv6 network.
  • the routes advertised by the primary and backup devices on the IPv4 network are for the same IPv4 address pool, in order to ensure the IP4.
  • the data packet between the IPv6 network and the IPv6 network is always translated and transited by the primary NAT device.
  • the route corresponding to the IPv4 address pool can be advertised in two ways to ensure that the data packet is translated and translated by the primary NAT 102 under normal conditions. :
  • the granularity of the route advertised by the primary NAT 102 is relatively small, and the granularity of the route advertised by the standby NAT 104 is relatively coarse; for example, the primary NAT 102 issues two routes 10.1.1.0/25 and 10.1.1.128/25, and the standby NAT 104 issues 10.1. .1.0/24—Route.
  • the primary NAT device can also advertise the above route, and the standby NAT only advertises its own prefix64 corresponding route, and does not advertise the route corresponding to the IPv4 address pool. Only when the primary NAT fails, the standby NAT The above IPv4 address pool corresponding route is issued only when it becomes a new primary NAT device. This eliminates the need to use the methods described in (1) and (2) to ensure that the data packet is always transited and translated by the primary NAT device.
  • the technical solution provided in the embodiment of the present invention when the host of the IPv4 network accesses the host of the IPv6 network or when the host of the IPv4 network accesses the host of the IPv6 network, implements cold backup and multiple NAT devices through multiple NAT devices.
  • the load sharing between the two devices solves the problem that the NAT device cannot access each other when the single device fails. This improves the reliability of the NAT device networking.
  • the hot backup method when the host 114 of the IPv4 network accesses the host 112 of the IPv6 network is: NA102 and NAT104 are configured with the same IPv4 addres s pool, using the same perf ix64; for the source host, that is, the host 114, that is, its destination address Assign an IP v4 address to the NAT102 through the IPv4 addres s pool; ensure that the destination host maintains the IP address of the network where the source host resides.
  • the address mapping information synchronization between NAT 102 and NAT 104 is required to ensure that the same IPv6 host translates to the same IPv4 address on both NATs; by using the same perf ix64, for the destination host 112, the source host 114 is The IPv6 address of the network where the destination host is located is the same. That is, the IPv4 address of the source host is the same as the IPv6 address synthesized by adding perf ix64.
  • the source host 114 of the IPv4 network sends the IPV4 data packet to the NAT 102 through the IPv4 address of the destination host in the network where the source host is located.
  • the IPv4 address of the IPv4 data packet is translated into an IPV6 address and sent to the IPv6 network.
  • the NATs are the same, and the composite IPv6 address of the host 114 is the same, so the entire handover process session does not interrupt after the NAT handover.
  • the data packet of the host 114 of the IPv4 network is forwarded and translated by the NAT 104, and the data packet is sent to the host. 112.
  • the primary NAT device (assumed to be NAT 102) and the standby NAT device (assumed to be NAT 104) are selected from the two NAT devices of a backup group by manual configuration or automatic election protocol.
  • the primary NAT device and the standby NAT device are in IPv6.
  • the route corresponding to the prefix 64 is advertised in the network, and the route corresponding to the IPv4 address pool is advertised in the IPv4 network.
  • the routes advertised by the primary and backup devices on the IPv6 network and the IPv4 network are respectively the same prefix 64 and the same.
  • IPv4 address pool in order to ensure that the data packets between the IP6 and the IPv4 network are always translated and transited by the primary NAT device, the route can be advertised in two ways to ensure that the data packet is translated by the primary NAT 102 under normal conditions. And transit:
  • the granularity of the route advertised by the primary NAT 102 is relatively small, and the granularity of the route advertised by the standby NAT 104 is relatively coarse; for example, the primary NAT 102 issues two routes 10.1.1.0/25 and 10.1.1.128/25, and the standby NAT 104 issues 10.1. .1.0/24—Route.
  • the primary NAT device can also issue the above route, and prepare The above route is not issued by NAT.
  • the above route is advertised only when the primary NAT fails and the standby NAT becomes the new primary NAT device. This eliminates the need to use the methods described in (1) and (2) to ensure that packets are always relayed and translated by the primary NAT device.
  • FIG. 2 is a simplified schematic diagram of a system for implementing redundancy backup and load balancing between multiple NAT devices in one embodiment of the present invention.
  • two instances are configured on both the NAT device 202 and the NAT device 204: Example 1 and Example 2.
  • Instances 1 and 2 run the Keep 1 i ve protocol to determine the Maser NAT devices corresponding to instance 1 and instance 2, for example.
  • the Mas ter NAT devices corresponding to different instances are preferably different to better implement load sharing.
  • the NAT device 202 is the Mask NAT device of the instance 1 and the S laver NAT device of the instance 2
  • the NAT device 204 is an instance.
  • 96-bit prefix 1, 96-bit prefix 2, IPv4 addres s pool 1, and IPv4 addres are configured on both NAT devices 202 and 204. s pool 2.
  • the NAT device 202 issues a 96-bit prefix 1 on the IPv6 network and IPv4 addres s pool 1 on the IPv4 network, while the NAT device 204 issues a 96-bit prefix 2 on the IPv6 network and IPv4 addres s poo l 2 on the IPv4 network.
  • the specific implementation details are the same as those in the embodiment shown in FIG. 1, and details are not described herein again.
  • IPv6 IPv4 address of the host 222 into an IPv6 address by using a 96-bit prefix 1.
  • the destination address of the IPv6 packet is a 96-bit prefix. 1 + ⁇ 4 (host 222), the source address is IPv6 (host 212).
  • the NAT device 202 issues a 96-bit prefix 1 to the IPv6 network and simultaneously issues an IPv4 addres pool 1 to the IPv4 network.
  • the IPv6 data packet sent by the host 212 to the host 222 is forwarded to the NAT device 202 along the IPv6 route that reaches the 96-bit prefix 1, and the IPv6 data packet is converted by the NAT device 202 into an IPv4 data packet, and the IPv4 data is translated into an IPv4 data packet.
  • the destination address of the packet is IPv4 (host 222), and the source address is an IPv4 address assigned by the NAT device 202 from the IPv4 addres pool 1 and may be referred to as IPv4 (host 212); the IPv4 packet is forwarded to the IPv4 by the NAT device 202.
  • the network at the same time, generates an address translation entry in the address translation table, as shown in the following example:
  • IPv6 (Host 212) -> IPv4 (Host 212)
  • This address translation entry is synchronized to the address translation table of the NAT device 204.
  • the above IPv4 packet finally arrives at the host 222.
  • the host 222 sends an IPv4 packet to the host 212, the destination address of the IPv4 packet is IPv4 (host 212), the source address is IPv4 (host 222), and the IPv4 packet is sent along the IP pool 1 of the NAT device 202.
  • the IPv4 pref ixl route arrives at the NAT device 202, and is converted by the NAT device 202 to generate an IPv6 data packet.
  • the destination address of the IPv6 data packet is IPv6 (host 212), and the source address is 96-bit prefix + IPv4 (host 222) ), the IPv6 packet finally arrives at the host 212.
  • the host 214 While the host 214 is communicating with the host 224, the host 214 sends an IP v 6 packet to the host 224, and converts the IPv4 address of the host 224 into an IPv6 address using a 96-bit prefix 2, the destination address of the IPv6 packet being p96 bits.
  • the prefix 2+IPv4 (host 224), the source address is IPv6 (host 214).
  • the NAT device 204 issues a 96-bit prefix 2 to the IPv6 network and simultaneously issues an IP pool 2 to an IPv4 network.
  • IPv6 data packet sent by the host 214 to the host 224 is forwarded to the NAT device 204 along the IPv6 route that reaches the 96-bit prefix 2, and is translated by the NAT device 204 into an IPv4 data packet, and the destination address of the IPv4 data packet.
  • IPv4 host 224
  • source address An IPv4 address assigned to the NAT device 204 from the IPv4 addres pool 2 may be referred to as IPv4 (Host 214), which is forwarded by the NAT device 204 to the IPv4 network and generates an address translation table in the address translation table. Item, as shown in the following example:
  • IPv6 (host 214) -> IPv4 (host 214)
  • This address translation entry is synchronized to the address translation table of the NAT device 202.
  • IPv4 packet finally arrives at host 224.
  • host 224 sends an IPv4 packet to host 214, the destination address of the IPv4 packet is IPv4 (host 214), the source address is IPv4 (host 224), and the IPv4 packet is sent along NAT device 204.
  • the IPv4 pref ix2 route arrives at the NAT device 204, and is converted by the NAT device 204 to generate an IPv6 data packet.
  • the destination address of the IPv6 data packet is IPv6 (host 214), and the source address is 96-bit prefix 2+IPv4 (host 224), the packet finally arrives at host 214.
  • load balancing between multiple NAT devices can be implemented while supporting redundant backup.
  • FIG. 2 uses two NAT devices as an example, and more NAT devices can be used for networking to implement redundancy backup and load sharing among multiple NAT devices.
  • the principle and the specific implementation are the same as those in the embodiment shown in FIG. 2, and details are not described herein again.
  • an IPv4 network accesses a host of an IPv6 network to a host, it can also implement redundancy backup and load balancing between multiple NATs.
  • redundancy backup and load balancing between multiple NATs.
  • Two groups are configured on the primary NAT 202 and NAT4, that is, the group corresponds to different IPv4 addres s pools, respectively: 3 ⁇ 4 port 10.
  • 1. 1. 0/24 corresponds to groupl, 20. 1. 1. 0/24 corresponds Group2, through VRRP or manual configuration, NAT202 is used as the primary of group-1, group-2 is reserved, NAT204 is used as the standby of group-1, and the primary of group-2.
  • NAT 202 is used as the primary role of group1.
  • the IPv4 addres s Pool corresponding to group 1 is assigned an IPv4 address for the AAAA record in the DNS (that is, the IPv6 address of the destination IPv6 host), and the mapping is performed. The relationship is logged to the NAT mapping table.
  • the NAT can choose to allocate the corresponding IPv4 address from different IPv4 addres pool according to the AAAA record. Such as, for example, based on the parity of a particular bit of an AAAA record (ie, an IPv6 address).
  • pref ix64 must be used for different groups to synthesize IPv6 addresses.
  • groupl uses pref ix64-A
  • group2 uses pref ix64-B, so that the same session's round-trip datagrams pass the same NAT.
  • FIG. 3 is a flowchart of a method for implementing redundancy backup of a NAT device in an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • IPv4 addres s pool and a 96-bit prefix for IPv4 address mapping to an IPv6 address on at least two NAT devices.
  • the primary NAT device issues a 96-bit prefix on the IPv6 network, and publishes IPv4 addres s poo l on the IPv4 network;
  • the primary NAT device processes the data packet from the host.
  • the primary NAT device After receiving the data packet from the host, the primary NAT device performs translation between the IPv6 address and the IPv4 address, and forwards the translated data packet;
  • the primary NAT device generates an address translation entry, where the address translation entry is used to record an IPv6 address corresponding to the host and an IPv4 address from the IPv4 addres s pool.
  • the primary NAT device synchronizes the address translation entry to the address translation table of the standby NAT device.
  • the 304 shown in FIG. 3 runs the Keep ive protocol on at least two NAT devices, determines one primary NAT device from at least two NAT devices, and the standby NAT device. Preparation, including:
  • Each instance runs the Keep 1 ive protocol, and determines the corresponding primary NAT from at least two NAT devices. Devices, as well as alternate NAT devices. For example, when determining a primary NAT device for each instance, try to implement different load balancing for different instances of the primary NAT device.
  • the 308 primary NAT device shown in FIG. 3 processes the data packet from the host, and includes: the primary NAT device processes the data packet from the host, and the prefix in the destination address of the data packet corresponds to the primary NAT device.
  • the step 312 shown in FIG. 3 synchronizes the address translation entry to the address translation table of the standby NAT device, and includes: synchronizing the address translation entry to the address translation table of the standby NAT device of the corresponding instance,
  • the address translation table is the address mapping table described below.
  • the address mapping table described below.
  • the 96-bit prefix used for mapping the IPv4 address to the IPv6 address is one of the prefi X prefixes, and the embodiment may also use the prefix pref ix64 or other length prefix.
  • Implementing an IPv4 address to synthesize an IPv6 address; and the IPv4 addres s pool and the prefix configured on the at least two NAT devices may be the same or different; in step 304, determining one of the at least two NAT devices
  • the primary NAT device and the standby NAT device can be selected by running the Keep 1 i ve protocol, or by running the automatic election protocol or manual configuration on the at least two NAT devices.
  • the apparatus includes: a storage module 402, a routing information issuing module 404, a data packet processing module 406, an address translation table entry generating module 408, and a synchronization module 410.
  • the storage module 402 is configured to store the configured IPv4 addres s pool and a 96-bit prefix for IPv4 address mapping to an IPv6 address.
  • the routing information issuing module 404 is configured to advertise the 96-bit prefix on the IPv6 network, and publish the IPv4 network on the IPv4 network.
  • the packet processing module 406 is configured to process the data packet from the host according to the IPv4 addres s pool and the 96-bit prefix; the address translation table entry generating module 408 is configured to process the data processing module 406 from the host. After the data packet, an address translation entry is generated, and the address is translated. The translation entry is used to record the IPv6 address corresponding to the host and the IPv4 address temporarily allocated from the IPv4 addres pool; the storage module 402 is further configured to store the address translation entry generated by the address translation entry generation module 408; 410 is configured to synchronize the address translation table entry to an address translation table of the standby NAT device.
  • the example shown in Fig. 4 is only an example, and each of the above modules can also be integrated, for example, integrating a plurality of modules into one unit.
  • FIG. 4 a simplified schematic diagram of an apparatus for implementing redundancy backup of a NAT device in another embodiment of the present invention may also be described by using the modules in FIG. 4, as follows:
  • Another device for implementing network address translation redundancy backup of a NAT device includes: a storage module, a routing information publishing module, and a data packet processing module;
  • the storage module is configured to store a configured fourth version Internet Protocol address pool IPv4 addres s pool and a prefix pref ix64 for mapping an IPv4 address to a sixth version Internet Protocol IPv6 address;
  • the route corresponding to the Pref ix64 is advertised on the IPv6 network, and the route corresponding to the IPv4 addres s pool is advertised on the IPv4 network;
  • the data packet processing module is configured to process a data packet between a source host and a destination host, where the source host and the destination host are respectively located in different IP networks.
  • the device further includes: the address mapping translation entry generation module described below is the address translation entry generation module in FIG.
  • An address mapping entry generating module configured to generate an address mapping entry after the data packet processing module processes the data packet from the source host, where the address mapping entry is IPv6 from the IPv4 addres pool a mapping relationship between the IPv4 address assigned by the host and the IPv6 address of the IPv6 host;
  • the storage module is further configured to pre-store an address mapping entry generated by the address mapping entry generation module;
  • the synchronization module is configured to synchronize the address mapping entry to an address mapping table of the standby NAT device.
  • the storage module is specifically configured to: store pre-configuration on the at least two NAT devices Different of the IPv4 addres s pool and the same pref ix64; or different pref ix64 pre-configured on the at least two NAT devices and the same IPv4 addres s pool; or
  • IPv4 addres s pool and the same pref ix64 pre-configured on the at least two NAT devices.
  • the device provided in the embodiment of the present invention implements hot and cold redundancy backup between multiple NAT devices when the host of the IPv4 network accesses the host of the IPv6 network or when the host of the IPv4 network accesses the host of the IPv6 network.
  • the problem that the NAT device cannot access each other when there is a single point of failure in the NAT device improves the reliability of the NAT device networking.
  • FIG. 5 is a simplified schematic diagram of an apparatus for implementing redundant backup of a NAT device in another embodiment of the present invention.
  • the apparatus includes: a storage module 502, a routing information issuing module 504, a data packet processing module 506, an address translation table entry generating module 508, and a synchronization module 510.
  • the storage module 502 is configured to store the configured IPv4 addres s pool and a 96-bit prefix for IPv4 address mapping to an IPv6 address.
  • the routing information issuing module 504 is configured to advertise the 96-bit prefix on the IPv6 network, and publish the IPv6 network on the IPv4 network.
  • the packet processing module 506 is configured to process the data packet according to the foregoing IPv4 addres s pool and the 96-bit prefix, where the data packet destination address prefix is a 96-bit prefix issued by the routing information issuing module 504; and the address translation entry generating module 508 is configured to generate, after the data packet processing module 506 processes the data packet from the host, an address translation entry, where the address translation entry is used to record an IPv6 address corresponding to the host and an IPv4 address temporarily allocated from the IPv4 addres pool.
  • the storage module 502 is further configured to store an address translation entry generated by the address translation entry generation module 506.
  • the synchronization module 510 is configured to synchronize the address translation entry to the address translation table of the second device, where the second device is An example of a Slaver NAT device; the storage module 502 is further configured to store from Synchronization information of the second device, the second device is the second NAT device of the second instance.
  • the second device is An example of a Slaver NAT device
  • the storage module 502 is further configured to store from Synchronization information of the second device, the second device is the second NAT device of the second instance.
  • the device provided in the embodiment of the present invention is implemented between multiple NAT devices when the host of the IPv4 network accesses the host of the IPv6 network or when the host of the IP v4 network accesses the host of the I Pv 6 network.
  • the load sharing improves the reliability of the NAT device networking.
  • the embodiment of the present invention further implements a system for performing network address translation NAT device redundancy backup, the system comprising: a first device and a second device, where the first device and the first device The second device is configured with the same fourth version Internet Protocol address pool IPv4 addres s pool and pref ix64 for IPv4 address mapping to the sixth version Internet Protocol IPv6 address; determining one primary use from the first device and the second device NAT device, and standby NAT device;
  • the primary NAT device is configured to advertise the route corresponding to the Pref ix64 on the IPv6 network, and advertise the route corresponding to the IPv4 addres s pool on the IPv4 network.
  • the standby NAT device is configured to process a data packet between the source host and the destination host when the primary NAT device fails; wherein the source host and the destination host are respectively located in different IP networks.
  • the primary NAT device of the primary NAT device is further configured to generate an address mapping entry, and synchronize the address mapping entry to an address mapping table of the standby NAT device, where the address mapping entry is a secondary address
  • the mapping between the IPv4 address assigned to the IPv6 host and the IPv6 address of the IPv6 host in the IPv4 addres s pool.
  • a first instance and a second instance are configured on the first device, and the first instance and the second instance are also configured on the second device, where the first instance and the second instance are respectively determined Corresponding primary NAT device, and standby NAT device.
  • the pref ix64 issued by the primary NAT device corresponding to different instances in the system is different.
  • the system structure diagram of the primary NAT and the backup NAT device may be described in detail with reference to the embodiment of FIG. 2, and details are not described herein again.
  • Another embodiment of the present invention provides a method for implementing a network address translation NAT device redundancy backup, including:
  • IPv4 addres s pool Pre-configure a fourth version of the Internet Protocol address pool (IPv4 addres s pool) and a prefix pref ix64 for mapping the IPv4 address to the sixth version of the Internet Protocol IPv6 address on the at least two NAT devices.
  • the configuration on the at least two NAT devices is specifically as follows: configuring different IPv4 addres pools and the same pref ix64 on the at least two NAT devices; or
  • S602. Determine one primary NAT device and the backup NAT device from the at least two NAT devices.
  • the at least two instances are configured on the at least two NAT devices, and the at least two instances are respectively determined from the at least two NAT devices by using an automatic election protocol or manually configured.
  • the primary NAT device, and the standby NAT device; the primary NAT device corresponding to each instance is different.
  • the primary NAT device advertises the route corresponding to the Prefix64 in the IPv6 network, and advertises the route corresponding to the IPv4 addres s pool on the IPv4 network.
  • the method further includes: the primary NAT device generates an address mapping entry; the primary NAT device synchronizes the address mapping entry to an address mapping of the standby NAT device. table.
  • the address mapping entry is a mapping relationship between an IPv4 address assigned to an IPv6 host from the IPv4 addres pool and an IPv6 address of the IPv6 host.
  • the standby NAT device processes a data packet between the source host and the destination host.
  • the source host and the destination host are respectively located on different IP networks.
  • IPv4 addres pools and the same pref ix64 are configured on the at least two NAT devices, or different pref 1x64 and the same are configured on the at least two NAT devices.
  • the destination host is in the same IP address as the network where the source host is located; or the same IPv4 is configured on the at least two NAT devices.
  • the addres spoo l and the same pref ix64 the destination host is in the same IP address as the network where the source host is located; and the source host does not change the IP address in the network where the destination host is located.
  • the technical solution provided in the embodiment of the present invention can implement redundancy backup such as cold backup and hot backup between multiple NAT devices.
  • This embodiment can be applied to hosts in an IPv4 network to access hosts in an IPv6 network, and can also be applied.
  • a host in an IPv6 network accesses a host in an IPv4 network, thereby improving the reliability of the NAT device networking.
  • load balancing between multiple NAT devices can be implemented while redundant backup between multiple NAT devices is implemented.
  • the technical solution provided in the embodiment of the present invention can implement redundancy backup between multiple NAT devices, thereby improving the reliability of the NAT device networking.
  • load balancing between multiple NAT devices can be implemented while implementing redundancy backup between multiple NAT devices.
  • Some of the steps in the embodiment of the present invention may be implemented by using software, and the corresponding software program may be stored in a readable storage medium, such as an optical disk or a hard disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种实现 NAT设备冗余备份的方法、 装置和系统
本申请要求了 2009年 3月 13 日提交的、 申请号为 200910105800.9、 发 明名称为 "一种实现 NAT设备冗余备份的方法、 装置和系统" 的中国申请的 优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信领域， 尤其涉及一种实现 NAT设备冗余备份的方法、 装置 和系统。 背景技术
目前技术中 , 在 NAT-PT ( Network Address Translation-Protocol Translator, 网络地址翻译-协议转换器， 以下简称为 NAT设备） 中实现采用 IPv6 (Internet Protocol version 6,第六版互联网协议）的主机访问采用 IPv4 ( Internet Protocol version 4, 第四版互联网协议） 的主机， 需在 NAT设 备上配置一个 public IPv4 address pool (公共 IPv4地址池） ， 用于将内部 IPv6地址翻译成 public IPv4地址; 同时配置一个 96比特前缀 ( refix /96 ) , 用于将 IPv4网络中的 IPv4地址映射成 IPv6地址， 该地址称为 IPv4 mapped IPv6 address0 同时在 IPv6网络侧发布 96比特前缀，将目的地址的前缀为 96比特前 缀的 IPv6数据包吸引过来。
本发明的发明人发现： 在目前的方案中在 NAT-PT上无论是实现采用 IPv6 的主机访问采用 IPv4的主机还是实现采用 IPv4的主机访问采用 IPv6的主机， 均没有实现 NAT设备冗余备份， 在实际使用过程中容易出现单点故障。 假设一 个会话原来通过 NAT设备 1进行中转， 如果 NAT设备 1出现故障， 会话则需要从 NAT设备 2进行中转， 但是由于 NAT设备 2的地址映射表和 NAT设备 1的地址映射 表中的信息不同， 导致原来的会话将被迫中断， 需要重新发起连接。 也就是 说， 现有技术中， 即使采用多个 NAT设备， 也无法实现多个 NAT设备之间的备 份。 发明内容
本发明的目的是提供一种在多个 NAT设备之间实现冗余备份的方案， 以提 高 NAT设备组网的可靠性。
本发明的一个实施例提供了一种实现网络地址翻译 NAT设备冗余备份的 方法， 包括：
在至少两个 NAT设备上预先配置第四版互联网协议地址池 IPv4 addres s poo 1和用于将 I Pv4地址映射到第六版互联网协议 I Pv 6地址的前缀 pr ef i x64； 从所述至少两个 NAT设备中确定一个主用 NAT设备， 以及备用 NAT设备； 所述主用 NAT设备在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网 络发布所述 IPv4 addres s poo l对应的路由；
当所述主用 NAT设备出现故障，所述备用 NAT设备对源主机和目的主机之 间的数据包进行处理， 其中所述源主机和所述目的主机分别位于不同的 IP网 络。
本发明的另一个实施例提供了一种实现网络地址翻译 NAT设备冗余备份 的装置， 包括： 存储模块、 路由信息发布模块和数据包处理模块；
所述存储模块， 用于存储配置的第四版互联网协议地址池 IPv4 addres s pool和用于将 IPv4地址映射到第六版互联网协议 IPv6地址的前缀 pref ix64; 所述路由信息发布模块， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络发布所述 IPv4 addres s pool对应的路由；
所述数据包处理模块， 用于对源主机和目的主机之间的数据包进行处理， 其中所述源主机和所述目的主机分别位于不同的 I P网络。
本发明的再一实施例提供了一种实现网络地址翻译 NAT设备冗余备份 的系统， 包括： 第一装置和第二装置， 在所述第一装置和第二装置上配置第 四版互联网协议地址池 IPv4 addres s pool和用于 IPv4地址映射到第六版互联 网协议 I P V 6地址的前缀 p r e f i X 64； 所述主用 NAT设备， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并 在 IPv4网络发布所述 IPv4 addres s pool对应的路由；
所述备用 NAT设备， 用于当所述主用 NAT设备出现故障， 对源主机和目的 主机之间的数据包进行处理； 其中所述源主机和所述目的主机分别位于不同 的 IP网络。
本发明实施例中提供的技术方案， 在 IPv4网络的主机访问 IPv6网络的主 机时或者， 在 IPv4网络的主机访问 IPv6网络的主机时， 通过多个 NAT设备之间 实现冗余备份， 解决了在 NAT设备出现单点故障时无法在网络间互相访问的问 题， 从而提高了 NAT设备组网的可靠性。 附图说明
图 1为本发明一个实施例中实现 NAT设备冗余备份的系统简化示意图； 图 2为本发明一个实施例中在多个 NAT设备之间实现冗余备份和负载均衡 的简化示意图；
图 3为本发明一个实施例中实现 NAT设备冗余备份的方法流程图； 图 4为本发明一个实施例中实现 NAT设备冗余备份的装置的简化示意图； 图 5为本发明另一个实施例中实现 NAT设备冗余备份的装置的简化示意 图；
图 6为本发明另一个实施例中实现 NAT设备冗余备份的方法流程图。
具体实施方式
下面结合附图和具体实施例展开详细说明。 但需要注意， 下面的这些实 施例， 仅为帮助理解技术方案所举的例子， 并不用于限定本发明。
图 1是本发明一个实施例中实现 NAT设备冗余备份的系统简化示意图。 如 图 1所示， NAT设备 102和 NAT设备 104配置相同的 IPv4 addres s pool和用于 IPv4 地址映射到 IPv6地址的 96比特前缀。 NAT设备 102和 NAT设备 104之间运行 Keepl ive (保活）协议， 从 NAT设备 102和 NAT设备 104中确定 Mas ter (主用） NAT设备和 S laver (备用） NAT设备，举例来说，可以采用 VRRP ( Vi r tua l Router Redundancy Protocol ,虚拟路由器冗余协议）来确定 Ma s ter NAT设备和 S laver NAT设备， 目前 VRRP协议通常采用组播方案交换 VRRP报文； 也可以进行改动， 例如当 NAT设备 102和 NAT设备 104之间没有直连网段的情况下， 可以采用单播 方式交换 VRRP报文。 这里假设确定 NAT设备 102作为 NAT设备， NAT设备 104作为 S laver NAT设备， 那么 NAT设备 102在 IPv6网络发布 96比特前缀， 同时在 IPv4 网络发布 IPv4 addres s pool。 而 NAT设备 104不在 IPv6和 IPv4网络内发布上述 路由信息， 或者， NAT设备 104发布上述路由信息时将 COST值设置的足够大， 使得在正常情况下， 数据包路由时会选择 NAT设备 102进行转发。
NAT设备 102与 NAT设备 104之间进行 NAT地址翻译表的同步， 举例来说， 可 以采用协议实现， 例如 HTTP ( Hyper text Transfer Protocol , 超文本传输协 议） ， 也可以采用私有的协议。 举例来说， 可以实时同步， 也可以定期进行 同步。 主机 112 , 位于 IPv6网络， 主机 114则位于 IPv4网络， 主机 112发起主机 114的会话，主机 112发送 IPv6数据包，该数据包的目的地址为 IPv4映射型 IPv6 地址， 即主机 I I 4的 IPv4地址（以下表述为 IPv4 (主机 114 ) )加上 96比特前 缀， 源地址为主机 112的 IPv6地址（以下表述为 IPv6 (主机 112 ) ) , 该 IPv6 数据包沿着 96比特前缀的 IPv6路由转发到 NAT设备 102 , 经过 NAT设备 102进行 协议转化， 翻译为 IPv4数据包， 该 IPv4数据包的目的地址为 IPv4 (主机 114) , 源地址为 NAT设备 102从 IPv4 addres s pool中分配的一个 IPv4地址， 该 IPv4地 址称做 IPv4 (主机 112) ; 该 IPv4数据包被 NAT设备 102转发到 IPv4网络， 并在地 址翻译表中生成一个地址翻译表项， 例如：
Ins ide IPv6 -> Out s ide IPv4
IPv6 (主机 112) -> IPv4 (主机 112)
上述地址翻译表项被同步到 NAT设备 104的地址翻译表。
上述 IPv4数据包最后到达主机 114。 作为响应， 主机 114向主机 112发送 IPv4数据包， 该 IPv4数据包的目的地址为 IPv4 (主机 112)，源地址为 IPv4 (主机 114) , 该 IPv4数据包沿着 NAT设备 102发送的 IPv4 addres s pool中的 IPv4 pref ix的路由到达 NAT设备 102 , 经过 NAT设备 102进行协议转化， 生成 IPv6数 据包， 该 IPv6数据包的目的地址为 IPv6 (主机 112) , 该目的地址是根据上述地 址翻译表项得到的， 源地址则为 96比特前缀 +IPv4 (主机 114) , 数据包最终到 达主机 112。
当发生 Mas ter NAT设备和 S laver NAT设备切换， 也就是， 当 NAT设备 104 变为 Mas ter NAT设备时， 若在 NAT设备 104作为 S laver NAT设备时未发布路由 信息， 则此时发布路由信息； 若在 NAT设备 104作为 S laver NAT设备时, NAT 设备 104发布了路由信息但将 COST值设置的足够大， 则此时更改 COST值。 而 NAT设备 102变为 S laver NAT设备， 撤消之前发布的路由信息。 如果 NAT设备 102发生故障或者网络连接断开， 则其已发布的路由信息， 对其他路由设备 而言变为无效路由。 这样， 对其他路由设备而言， NAT设备 104发布的路由信 息是当前的最佳路由， 主机 102与主机 104之间进行通信的数据包将通过 NAT 设备 104进行翻译和转发， 由于 NAT设备 104与 NAT设备 102之间已经实现地址 翻译表的同步， 所以， 主机 102与主机 104在主用 NAT设备和备用 NAT设备切换 前已经建立的会话就可以通过 NAT设备 104进行翻译和中转， 而不会出现中 断。 Mas ter NAT设备和 S laver NAT设备发生切换的条件， 可以参考 VRRP协议， 此处不再赘述。
上述图 1所示的实施例是以主机 112先向主机 114发送 IPv6数据包为例进 行说明的。
在本发明的另一个实施例中， 主机 114也可以先向主机 112发送 IPv4数据 包， 在这种情形下， 则通过 DNS ( Doma in Name Servi ce, 域名服务） ， 主机 114获知主机 112的 IPv4地址， 并在 NAT102的地址翻译表中生成一个地址翻译 表项， 例: ¾口：
Ins ide IPv6 -> Out s ide IPv4 IPv6 (主机 112) -> IPv4 (主机 112)
上述地址翻译表项也会同步到 NAT设备 104的地址翻译表。
其中， 需要说明的是： 其一、 上述实施例中， 用于 IPv4地址映射到 IPv6 地址的 96比特前缀，可以使用该 96比特前缀，也可以选择 pref ix64比特前缀， 或者其他长度的前缀， 即上述实施例以 96比特前缀 (表示为 pref ix/96)为例 进行说明， 但不限于 96比特前缀， 下面的实施例以 pref ix64前缀进行说明， 也可以应用于 pref ix96前缀的情况； 其二、 从 NAT设备 102和 NAT设备 104中确 定主用 NAT设备和备用 NAT设备时， 可以通过 Keepl ive (保活）协议即自动选 举协议， 也可以通过手动配置进行选择； 其三、 上述地址翻译表即为地址映 射表， 这两种表达一个意思， 为了术语统一， 下面统一用地址映射表来进行 实施例的描述。
本发明另一个实施例为： 在发生主用 NAT设备和备用 NAT设备切换时， 也 就是， 当 NAT设备 104变为主用 NAT设备时， NAT102和 NAT104之间的冷备份和热 备份的处理的方法。
其中， 冷备份的核心思想是： 针对源主机而言， 目的主机在源主机所在 网络的 IP地址始终保持不变； 热备份的核心思想是： （1 )针对源主机而言， 目的主机在源主机所在网络的 IP地址始终保持不变； 以及 （ 2 )针对目的主 机而言， 源主机在目的主机所在网络内的 IP地址保持始终保持不变； 其中源 主机和目的主机在不同的 IP网络中，例如：图 1中的源主机为主机 112 ,在 IPv6 网络中； 则目的主机为主机 114 , 在 IPv4网络中。
根据上述的核心思想， 下面具体描述下面两种场景下的冷备份和热备份： ( 1 )在 I Pv 6网络的主机 112访问 I Pv4网络的主机 114时的冷备份和热备份 的方法；
( 2 ) IPv4网络的主机 114访问 IPv6网络的主机 112时的冷备份和热备份的 方法。
针对场景 1： IPv6网络的主机 112访问 IPv4网络的主机 114时的冷备份的方 法为：
NA102和 NAT104配置不同的 IPv4 addres s pool , 使用相同的 perf ix前缀； 由于使用相同的 perf ix前缀， 所以针对源主机， 即主机 112而言， 目的主机 在源主机所在网络的 IP地址始终保持不变， 即其目的地址在发生 NAT102和 NAT104切换前后是不发生变化的， 均为 pref ix64加上该目的主机的 IPv4地 址， 因此不需要对 NAT102和 NAT104进行地址映射同步； 由于 NAT102和 NAT104 的 IPv4 addres s pool配置不同，主机 112的源地址经过 NAT102翻译后，其 IPv4 地址是不同的。
IPv6网络的主机 112将 IPV6数据包发送给 NAT102 , NAT102进行地址翻译 后， 将 IPv6数据包的源地址 IPv6地址转换为 IPV4地址（从 IPv4 addres s pool 中给主机 114分配一个 IP4地址） ， 并根据目的主机的合成的 IPv6地址， 去掉 其 pref ix64 , 生成的 IPv4地址， 将所述数据包发送给 IPv4网络中的目的主机 114。
其路由发布过程为：
通过手动配置方式或者自动选举协议,在一个备份组的两个 NAT设备当中 选择出主用 NAT设备 (假设为 NAT102)和备用 NAT设备 (假设为 NAT104), 主 用 NAT设备和备用 NAT设备在 IPv6网络内发布所述 prefix64对应的路由，同时 在 IPv4网络内发布所述各自的 IPv4 address pool对应的路由. 由于主用和备用 NAT设备在 IPv6网络中发布的路由都是针对同一个 prefix64的，为了保证 IP6 网络到达 IPv4网络内的数据包时经过主用的 NAT102设备， 可以通过下面两 种方式区分主用和备用发布的 Prefix64对应的路由， 以保证所述数据包在正 常情况下经过主用 NAT102进行翻译和中转：
( 1 )主用 NAT 102设置 cost足够小， 备用 NAT104设置 cost足够大；
( 2 )主用 NAT 102发布路由的粒度较细， 备用 NAT 104发布路由的粒 度较粗； 例如： 主用 NAT102发布 10.1.1.0/25和 10.1.1.128/25两条路由， 而备用 NAT104发布10.1.1.0/24—条路由。 在采用自动选举协议的情况下，也可以让主 NAT设备发布上述路由，备用
NAT只在 IPv4网络发布自己的 IPv4 address pool对应的路由，而不发布上述 prefix64路由 .只有当主用 NAT故障情况下,备用 NAT成为新的主用 NAT设备时 才发布上述 prefix64路由.这样就不需要采用（1)和 (2)中描述的方法就可以保证 数据包始终经过主 NAT设备中转和翻译.
针对 I Pv6网络的主机 112访问 I P v4网络的主机 114时的热备份的方法为： NA102和 NAT104配置相同的 IPv4 addres s pool , 使用相同的 perf ix64; 所以针对源主机， 即主机 112而言， 目的主机在源主机所在网络的 I P地址不 变， 即其目的地址在发生 NAT102和 NAT104切换前后是不发生变化； 为保证 NAT102和 NAT104针对同一个 IPv6主机分配的 IPv4地址相同 （ NAT102和 NAT104 虽然配置相同的 IPv4 addres s pool , 但是源主机 112在目的主机 114所在的 网络内通过 NAT102和 NAT104的 IPv4 addres s pool地址池中各自分配的 IPv4 地址也可能不相同） ， 因此需要对 NAT102和 NAT104进行地址映射同步。
IPv6网络的主机 112将 IPV6数据包发送给 NAT102 , NAT102进行地址翻译 后， 将 IPv6数据包的源地址 IPv6地址转换为源 IPV4地址（从 IPv4 addres s poo l中给主机 114分配一个 IP4地址） ， 并根据目的主机的合成的 IPv6地址， 去掉其 pref ix64 , 生成目的 IPv4地址， 将所述翻译之后的数据包发送给 IPv4 网络中的目的主机 114。
其路由发布过程为：
通过手动配置方式或者自动选举协议,在一个备份组的两个 NAT设备当中 选择出主用 NAT设备 (假设为 NAT 102)和备用 NAT设备 (假设为 NAT 104) , 主 用 NAT设备和备用 NAT设备在 IPv6网络内发布所述 prefix64对应的路由，同时 在 IPv4网络内发布所述 IPv4 address pool对应的路由.由于主用和备用设备在 IPv6网络以及 IPv4网络发布的路由分别都是针对相同的 prefix64以及相同的 IPv4 address pool, 为了保证 IP6与 IPv4网络之间的数据包始终经过主用 NAT 设备翻译和中转， 可以通过两种方式发布路由， 以保证所述数据包在正常情 况下经过主用 NAT 102进行翻译和中转：
( 1 )主用 NAT 102设置 cost足够小， 备用 NAT104设置 cost足够大；
( 2 )主用 NAT 102发布路由的粒度较细， 备用 NAT 104发布路由的粒 度较粗； 例如： 主用 NAT102发布 10.1.1.0/25和 10.1.1.128/25两条路由， 而备用 NAT104发布10.1.1.0/24—条路由。
在采用自动选举协议的情况下， 也可以让主 NAT设备发布上述路由，而备 用 NAT不发布上述路由.只有当主用 NAT故障情况下，备用 NAT成为新的主用 NAT设备时才发布上述路由.这样就不需要采用（1)和 (2)中描述的方法就可以 保证数据包始终经过主 NAT设备中转和翻译。
针对场景 2: IPv4网络的主机 114访问 IPv6网络的主机 112时的冷备份的 方法为：
NA102和 NAT104配置相同的 IPv4 addres s pool , 使用不同的 perf ix前缀； 针对源主机，即主机 114而言，即其目的地址为 NAT102通过 IPv4 addres s pool 分配一个 I P v4的地址； 要保证目的主机在源主机所在网络的 I P地址始终保持 不变， 因此需要 NAT102和 NAT104之间进行地址映射信息同步， 保证同一个 IPv6主机在两个 NAT上都翻译成同一个 IPv4地址。 通过使用不同的 perf ix前 缀， 针对目的主机 112 , 源主机 114在目的主机所在的网络的 IPv6地址是不同 的， 即源主机的 IPv4地址加 perf ix前缀后不相同。
IPv4网络的主机 114将 IPV4数据包发送给 NAT102 , NAT102进行地址翻译 后， 将 IPv4数据包的 IPv4地址转换为 IPV6地址发送给 IPv6网络中的目的主机 112 ; 当发生 NAT102到 NAT104切换时， 即 NAT104切换为主 NAT设备， 主机 114 到主机 112的数据包通过 NAT104的中转和翻译， 由于通过地址映射信息同步， 主机 112对应的 Pv4地址在两个 NAT上相同， 所以整个切换过程对于主机 112是 透明的， 但是由于 pr if ix64不同， 即主机 114的合成 IPv6地址发生改变， 原 来的会话发生中断， 主机 114重新发起连接请求， 使得 IPv4网络的主机 114的 数据包通过 NAT104中转和翻译后， 将数据包发送给主机 112。 其路由发布过程为：
通过手动配置方式或者自动选举协议,在一个备份组的两个 NAT设备当中 选择出主用 NAT设备 (假设为 NAT102)和备用 NAT设备 (假设为 NAT104), 主 用 NAT设备和备用 NAT设备在 IPv4网络内发布所述 IPv4 address pool对应的 路由，同时在 IPv6网络内发布所述各自的 prefix64对应的路由.由于主用和备用 设备在 IPv4网络发布的路由是针对相同的 IPv4 address pool, 为了保证 IP4与 IPv6网络之间的数据包始终经过主用 NAT设备翻译和中转， 可以通过两种方 式发布 IPv4 address pool对应的路由，以保证所述数据包在正常情况下经过主 用 NAT 102进行翻译和中转：
( 1 )主用 NAT 102设置 cost足够小， 备用 NAT104设置 cost足够大；
( 2 )主用 NAT 102发布路由的粒度较细， 备用 NAT 104发布路由的粒 度较粗； 例如： 主用 NAT102发布 10.1.1.0/25和 10.1.1.128/25两条路由， 而备用 NAT104发布10.1.1.0/24—条路由。
在采用自动选举协议情况下， 也可以让主 NAT设备发布上述路由，而备用 NAT只发布自己的 prefix64对应路由，而不发布上述 IPv4 address pool对应的路 由.只有当主用 NAT故障情况下，备用 NAT成为新的主用 NAT设备时才发布上 述 IPv4 address pool对应路由.这样就不需要采用（1)和 (2)中描述的方法就可以 保证数据包始终经过主 NAT设备中转和翻译。
本发明实施例中提供的技术方案， 在 IPv4网络的主机访问 IPv6网络的主 机时或者， 在 IPv4网络的主机访问 IPv6网络的主机时， 通过多个 NAT设备之间 实现冷备份及多个 NAT设备间的负载分担， 解决了在 NAT设备出现单点故障时 无法在网络间互相访问的问题， 从而提高了 NAT设备组网的可靠性。
IPv4网络的主机 114访问 IPv6网络的主机 112时的热备份的方法为： NA102和 NAT104配置相同的 IPv4 addres s pool , 使用相同的 perf ix64; 针对源主机，即主机 114而言，即其目的地址为 NAT102通过 IPv4 addres s pool 分配一个 I P v4的地址； 要保证目的主机在源主机所在网络的 I P地址始终保持 不变， 因此需要 NAT102和 NAT104之间进行地址映射信息同步， 保证同一个 IPv6主机在两个 NAT上都翻译成同一个 IPv4地址； 通过使用相同的 perf ix64 , 针对目的主机 112 , 源主机 114在目的主机所在的网络的 IPv6地址是相同的， 即源主机的 IPv4地址前面加上 perf ix64而合成的 IPv6地址相同。
IPv4网络的源主机 114通过目的主机在源主机所在网络内的 IPv4地址， 将 IPV4数据包发送给 NAT102 , NAT 102进行地址翻译后， 将 IPv4数据包的 IPv4地 址转换为 IPV6地址发送给 IPv6网络中的目的主机 112; 当发生 NAT102到 NAT104切换时， 即 NAT104切换为主 NAT设备， 主机 114到主机 112的数据包通 过 NAT104的中转和翻译， 由于通过地址映射同步，主机 112对应的 IPv4地址在 两个 NAT上相同， 且主机 114的合成 IPv6地址也是相同的， 所以整个切换过程 会话在 NAT切换之后不发生中断， IPv4网络的主机 114的数据包通过 NAT104 中转和翻译后， 将数据包发送给主机 112。
其路由发布过程为：
通过手动配置方式或者自动选举协议,在一个备份组的两个 NAT设备当中 选择出主用 NAT设备 (假设为 NAT102)和备用 NAT设备 (假设为 NAT104), 主 用 NAT设备和备用 NAT设备在 IPv6网络内发布所述 prefix64对应的路由，同时 在 IPv4网络内发布所述 IPv4 address pool对应的路由.由于主用和备用设备在 IPv6网络以及 IPv4网络发布的路由分别都是针对相同的 prefix64以及相同的 IPv4 address pool, 为了保证 IP6与 IPv4网络之间的数据包始终经过主用 NAT 设备翻译和中转， 可以通过两种方式发布路由， 以保证所述数据包在正常情 况下经过主用 NAT 102进行翻译和中转：
( 1 )主用 NAT 102设置 cost足够小， 备用 NAT104设置 cost足够大；
( 2 )主用 NAT 102发布路由的粒度较细， 备用 NAT 104发布路由的粒 度较粗； 例如： 主用 NAT102发布 10.1.1.0/25和 10.1.1.128/25两条路由, 而备用 NAT104发布 10.1.1.0/24—条路由。
在采用自动选举协议的情况下， 也可以让主 NAT设备发布上述路由，而备 用 NAT不发布上述路由。 只有当主用 NAT故障情况下，备用 NAT成为新的主用 NAT设备时才发布上述路由。 这样就不需要采用（1)和 (2)中描述的方法就可以 保证数据包始终经过主 NAT设备中转和翻译。
本发明实施例中提供的技术方案， 在 IPv4网络的主机访问 IPv6网络的主 机时或者， 在 IPv4网络的主机访问 IPv6网络的主机时， 通过多个 NAT设备之间 实现热备份， 保证了整个切换过程会话在 NAT切换之后不发生中断， 解决了在 NAT设备出现单点故障时无法在网络间互相访问的问题， 从而提高了 NAT设备 组网的可靠性。
图 2是本发明一个实施例中在多个 NAT设备之间实现冗余备份和负载均衡 的系统简化示意图。 如图 2所示， 在 NAT设备 202和 NAT设备 204上均配置两个实 例： 实例 1和实例 2。 为实例 1和实例 2配置不同的 ύ先级（ pr ior i ty ) , 实例 1 和实例 2分别运行 Keep 1 i ve协议， 分别确定实例 1和实例 2对应的 Ma s t er NAT设 备，举例来说， 不同实例对应的 Mas ter NAT设备最好不同， 以更好地实现负载 分担， 例如， NAT设备 202是实例 1的 Ma s ter NAT设备和实例 2的 S laver NAT设 备，而 NAT设备 204是实例 1的 S laver NAT设备和实例 2的 Mas ter NAT设备。 为实 例 1配置 IPv4 addres s pool 1和用于 IPv4地址映射到 IPv6地址的 96比特前缀 1 , 为实例 2配置 IPv4 addres s pool 2和用于 IPv4地址映射到 IPv6地址的 96比特 前缀 2; IPv4 addres s pool 2不同于 IPv4 addres s pool 1 , 96比特前缀 2不 同于 96比特前缀 1。 分别针对实例 1和实例 2 , 在 NAT设备 202和 NAT设备 204之间 实现冗余备份，在 NAT设备 202和 204上都配置 96比特前缀 1、 96比特前缀 2、 IPv4 addres s pool 1和 IPv4 addres s pool 2。 NAT设备 202在 IPv6网络发布 96比特 前缀 1 , 并在 IPv4网络发布 IPv4 addres s pool 1 , 而 NAT设备 204则在 IPv6网 络发布 96比特前缀 2 , 并在 IPv4网络发布 IPv4 addres s poo l 2。 具体实现细 节与图 1所示实施例相同， 此处不再赘述。 由于不同实例选择不同的 NAT设备 作为 Mas ter NAT设备， 对于来自不同主机的数据包， 则可以经过不同的 NAT设 备进行翻译和中转， 从而可以实现多个 NAT设备之间的负载均衡。 举例来说， 主机 212与主机 222进行通信时， 主机 212向主机 222发送 IPv6 数据包， 采用 96比特前缀 1将主机 222的 IPv4地址转化成 IPv6地址， 该 IPv6数 据包的目的地址是 96比特前缀 1 + ΙΡν4 (主机 222) , 源地址为 IPv6 (主机 212) 。 NAT设备 202作为实例 1的 Mas ter NAT设备， 发布 96比特前缀 1到 IPv6网络， 同 时发布 IPv4 addres s pool 1到 IPv4网络。 这样， 主机 212向主机 222发送的 IPv6 数据包就沿着到达 96比特前缀 1的 IPv6路由转发到 NAT设备 202 , 该 IPv6数据包 经过 NAT设备 202进行协议转化， 翻译为 IPv4数据包， 该 IPv4数据包的目的地 址为 IPv4 (主机 222) , 源地址为 NAT设备 202从 IPv4 addres s pool 1中分配的 一个 IPv4地址， 可以称作 IPv4 (主机 212) ; 该 IPv4数据包被 NAT设备 202转发到 IPv4网络， 同时在地址翻译表中生成一个地址翻译表项， 如下例所示：
Ins ide IPv6 -> Out s ide IPv4
IPv6 (主机 212) -> IPv4 (主机 212)
这个地址翻译表项被同步到 NAT设备 204的地址翻译表。
上述 IPv4数据包最后到达主机 222。 作为回应， 主机 222向主机 212发送 IPv4数据包， 该 IPv4数据包的目的地址为 IPv4 (主机 212)，源地址为 IPv4 (主机 222) , 该 IPv4数据包沿着 NAT设备 202发送的 IP pool 1中的 IPv4 pref ixl的路 由到达 NAT设备 202 , 经过 NAT设备 202进行协议转化， 生成 IPv6数据包， 该 IPv6 数据包的目的地址为 IPv6 (主机 212) , 源地址为 96比特前缀 +IPv4 (主机 222) , 该 IPv6数据包最终到达主机 212。
而主机 214与主机 224之间进行通信时， 主机 214向主机 224发送 I P v 6数据 包， 采用 96比特前缀 2将主机 224的 IPv4地址转化成 IPv6地址， 该 IPv6数据包 的目的地址为 p96比特前缀 2+IPv4 (主机 224) , 源地址为 IPv6 (主机 214) 。 NAT 设备 204作为实例 2的 Ma s ter NAT设备， 发布 96比特前缀 2到 IPv6网络， 同时发 布 IP pool 2到 IPv4网络。 这样， 主机 214向主机 224发送的 IPv6数据包就沿着 到达 96比特前缀 2的 IPv6路由转发到 NAT设备 204 , 经过 NAT设备 204进行协议转 化， 翻译为 IPv4数据包， 该 IPv4数据包的目的地址为 IPv4 (主机 224) , 源地址 为 NAT设备 204从 IPv4 addres s pool 2中分配的一个 IPv4地址， 可以称作 IPv4 (主机 214) , 该 IPv4数据包被 NAT设备 204转发到 IPv4 网络， 并在地址翻 译表中生成一个地址翻译表项， 如下例所示：
Ins ide IPv6 -> Out s ide IPv4
IPv6 (主机 214) -> IPv4 (主机 214)
这个地址翻译表项被同步到 NAT设备 202的地址翻译表。
上述 IPv4数据包最终到达主机 224。 作为响应， 主机 224向主机 214发送 IPv4数据包， 该 IPv4数据包的目的地址为 IPv4 (主机 214)，源地址为 IPv4 (主机 224) , 该 IPv4数据包沿着 NAT设备 204发送的 IP pool 2中的 IPv4 pref ix2的路 由到达 NAT设备 204 , 经过 NAT设备 204进行协议转化， 生成 IPv6数据包， 该 IPv6 数据包的目的地址为 IPv6 (主机 214) , 源地址为 96比特前缀 2+IPv4 (主机 224) , 数据包最终到达主机 214。
采用上述图 2所示实施例的方案， 在支持冗余备份的同时， 可以实现多个 NAT设备之间的负载均衡。
图 2所示的实施例采用两个 NAT设备作为示例， 也可以采用更多个 NAT设备 进行组网， 实现多个 NAT设备间的冗余备份和负载分担。 原理与具体实现与图 2所示实施例相同， 此处不再赘述。
同样， IPv4网络向主机访问 IPv6网络的主机时， 也可以实现多个 NAT之 间的冗余备份和负载均衡， 具体描述如下：
主用 NAT202和 NAT4上配置两个组 group, 即该 group分别对应不同的 IPv4 addres s pool ,比: ¾口10. 1. 1. 0/24对应 groupl, 20. 1. 1. 0/24对应 group2，通过 VRRP或手动配置方式，将其中 NAT202作为 group-1的主用， group-2的备用，将 NAT204作为 group - 1的备用， group - 2的主用。
如果 DNS应答消息经过 NAT202,那么 NAT202作为 groupl的主用，将从 group 1 对应的 IPv4 addres s Pool中为 DNS中的 AAAA记录（也就是目的 IPv6主机的 IPv6 地址）分配一个 IPv4地址，并将映射关系记录到 NAT映射表。 同理，如果经过 NAT204,将从 group2的 IPv4 addres s pool中分配地址； 或者为 NAT收到 DNS应 答消息之后，根据 AAAA记录的不同而选择从不同的 IPv4 addres s pool中分配 相应的 IPv4地址， 其实现方法可以多种，比如根据 AAAA记录（也就是 IPv6地址） 的某个特定比特位的奇偶来决定。 需要注意的是： 如果采用热备份方式，针对 不同的 group必须采用不同的 pref ix64来合成 IPv6地址。 比如 groupl采用 pref ix64-A, group2采用 pref ix64-B，这样保证同一个会话的来回数据报经过 相同的 NAT。 采用上述图 2所示实施例的方案， 在支持冗余备份的同时， 可以 实现多个 NAT设备之间的负载均衡。
图 3是本发明一个实施例中实现 NAT设备冗余备份的方法流程图， 如图 3 所示， 该方法包括：
302、 在至少两个 NAT设备上配置相同的 IPv4 addres s pool和用于 IPv4地 址映射到 IPv6地址的 96比特前缀；
304、 在上述至少两个 NAT设备上运行 Keep l ive协议， 从所述至少两个 NAT 设备中确定一个主用 NAT设备， 以及备用 NAT设备；
306、 主用 NAT设备在 IPv6网络发布 96比特前缀， 并在 IPv4网络发布 IPv4 addres s poo l ;
308、 主用 NAT设备处理来自主机的数据包；
举例来说， 主用 NAT设备接收到来自主机的数据包后， 进行 IPv6地址与 IPv4地址之间的翻译， 并转发翻译后的数据包；
310、 主用 NAT设备生成地址翻译表项， 该地址翻译表项用于记录上述主 机对应的 IPv6地址和从上述 IPv4 addres s pool中临日于分酉己的 IPv4地址；
312、 主用 NAT设备将上述地址翻译表项同步到上述备用 NAT设备的地址翻 译表。
具体实现细节请参考图 1所示的实施例， 此处不再赘述。
在本发明的另一个实施例中， 图 3所示的 304 在至少两个 NAT设备上运行 Keepl ive协议， 从至少两个 NAT设备中确定一个主用 NAT设备， 以及备用 NAT设 备， 包括：
在至少两个 NAT设备上均配置至少两个实例， 为不同的实例配置不同的 pr ior i ty, 每个实例分别运行 Keep 1 ive协议， 从至少两个 NAT设备中确定其对 应的主用 NAT设备， 以及备用 NAT设备。 举例来说， 为每个实例确定一个主用 NAT设备时， 尽量做到不同实例的主用 NAT设备不相同， 以实现负载分担。
对应地， 图 3所示的 308 主用 NAT设备处理来自主机的数据包， 包括： 主 用 NAT设备处理来自主机的数据包， 该数据包目的地址中的前缀对应该主用 NAT设备。 图 3所示的步骤 312主用 NAT设备将上述地址翻译表项同步到上述备 用 NAT设备的地址翻译表， 包括： 将上述地址翻译表项同步到对应的实例的备 用 NAT设备的地址翻译表， 且地址翻译表即为下面所述的地址映射表。 具体实 现细节请参考图 2所示的实施例， 此处不再赘述。
上述实施例需要说明的是： 步骤 302中， 用于 IPv4地址映射到 IPv6地址的 96比特前缀是 p r e f i X前缀中的其中一种前缀， 所述实施例也可以用前缀 pref ix64或其它长度的前缀实现 IPv4地址合成 IPv6地址； 以及在至少两个 NAT 设备上配置的 IPv4 addres s pool和前缀可以是相同的， 也可以是不相同的； 步骤 304中， 从所述至少两个 NAT设备中确定一个主用 NAT设备， 以及备用 NAT 设备， 选择时可以通过运行 Keep 1 i ve协议， 也可以通过运行自动选举协议或 手工配置方式在上述至少两个 NAT设备上进行选择。
图 4是本发明一个实施例中实现 NAT设备冗余备份的装置的简化示意图。 如图 4所示， 该装置包括： 存储模块 402、 路由信息发布模块 404、 数据包 处理模块 406、地址翻译表项生成模块 408和同步模块 410。其中，存储模块 402 用于存储配置的 IPv4 addres s pool和用于 IPv4地址映射到 IPv6地址的 96比特 前缀； 路由信息发布模块 404用于在 IPv6网络发布该 96比特前缀， 并在 IPv4网 络发布该 IPv4 addres s pool ; 数据包处理模块 406用于才艮据上述 IPv4 addres s pool和 96比特前缀处理来自主机的数据包； 地址翻译表项生成模块 408用于在 数据包处理模块 406处理来自主机的数据包后， 生成地址翻译表项， 该地址翻 译表项用于记录上述主机对应的 IPv6地址和从上述 IPv4 addres s pool中临时 分配的 IPv4地址； 上述存储模块 402还用于存储地址翻译表项生成模块 408生 成的地址翻译表项； 同步模块 410用于将上述地址翻译表项同步到备用 NAT设 备的地址翻译表。 图 4所示仅为示例， 上述各个模块也可以进行集成， 例如， 将多个模块集成为一个单元。
如图 4所示， 本发明另一个实施例中实现 NAT设备冗余备份的装置的简化 示意图也可以用图 4的各模块进行描述， 具体如下：
另一种实现网络地址翻译 NAT设备冗余备份的装置， 包括： 存储模块、 路 由信息发布模块和数据包处理模块；
所述存储模块， 用于存储配置的第四版互联网协议地址池 IPv4 addres s pool和用于将 IPv4地址映射到第六版互联网协议 IPv6地址的前缀 pref ix64; 所述路由信息发布模块， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络发布所述 IPv4 addres s pool对应的路由；
所述数据包处理模块， 用于对源主机和目的主机之间的数据包进行处理， 其中所述源主机和所述目的主机分别位于不同的 IP网络。
所述装置还包括： 下面所述的地址映射翻译表项生成模块即为图 4 中的 地址翻译表项生成模块。
地址映射表项生成模块， 用于在所述数据包处理模块处理来自源主机的 数据包后，生成地址映射表项，其中，所述地址映射表项为从所述 IPv4 addres s pool中为 IPv6主机分配的 IPv4地址与所述 IPv6主机的 IPv6地址之间的映射关 系；
所述存储模块， 还用于预先存储所述地址映射表项生成模块生成的地址 映射表项；
所述同步模块， 用于将所述地址映射表项同步到备用 NAT设备的地址映 射表。
其中所述存储模块具体用于： 在所述至少两个 NAT设备上存储预先配置 的不同的所述 IPv4 addres s pool和所述相同的 pref ix64; 或者， 在所述至少两个 NAT设备上预先配置的不同的 pref ix64 和所述相同的 IPv4 addres s pool ; 或者,
在所述至少两个 NAT设备上预先配置的相同的所述 IPv4 addres s pool 和所述相同的 pref ix64。
本发明实施例中提供的装置， 在 IPv4 网络的主机访问 IPv6 网络的主机 时或者， 在 IPv4网络的主机访问 IPv6网络的主机时， 通过多个 NAT设备之 间实现了冷热冗余备份， 解决了在 NAT设备出现单点故障时无法在网络间互 相访问的问题， 从而提高了 NAT设备组网的可靠性。
图 5是本发明另一个实施例中实现 NAT设备冗余备份的装置的简化示意 图。 如图 5所示， 该装置包括： 存储模块 502、 路由信息发布模块 504、 数据包 处理模块 506、地址翻译表项生成模块 508和同步模块 510。其中，存储模块 502 用于存储配置的 IPv4 addres s pool和用于 IPv4地址映射到 IPv6地址的 96比特 前缀； 路由信息发布模块 504用于在 IPv6网络发布该 96比特前缀， 并在 IPv4网 络发布该 IPv4 addres s pool ; 数据包处理模块 506用于根据上述 IPv4 addres s pool和 96比特前缀处理数据包， 该数据包目的地址前缀是路由信息发布模块 504发布的 96比特前缀； 地址翻译表项生成模块 508用于在数据包处理模块 506 处理来自主机的数据包后， 生成地址翻译表项， 该地址翻译表项用于记录上 述主机对应的 IPv6地址和从上述 IPv4 addres s pool中临时分配的 IPv4地址； 上述存储模块 502还用于存储地址翻译表项生成模块 506生成的地址翻译表 项； 同步模块 510用于将上述地址翻译表项同步到第二装置的地址翻译表， 该 第二装置是第一实例的 S laver NAT设备； 上述存储模块 502还用于存储来自第 二装置的同步信息， 第二装置是第二实例的 Ma s ter NAT设备。 具体实现细节 请参考图 2所示的实施例， 此处不再赘述。
本发明实施例中提供的装置， 在 IPv4网络的主机访问 IPv6网络的主机时 或者， 在 I P v4网络的主机访问 I Pv 6网络的主机时， 通过多个 NAT设备之间实现 了负载分担， 从而提高了 NAT设备组网的可靠性。
在实现上述装置的基石出上，本发明实施例还实现了一种网络地址翻译 NAT 设备冗余备份的系统， 所述系统包括： 第一装置和第二装置， 在所述第一装 置和第二装置上配置相同的第四版互联网协议地址池 IPv4 addres s pool 和 用于 IPv4地址映射到第六版互联网协议 IPv6地址的 pref ix64; 从所述第一 装置和第二装置中确定一个主用 NAT设备， 以及备用 NAT设备；
所述主用 NAT设备， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络发布所述 IPv4 addres s pool对应的路由。
所述备用 NAT设备， 用于当所述主用 NAT设备出现故障时， 对源主机和 目的主机之间的数据包进行处理； 其中所述源主机和所述目的主机分别位于 不同的 IP网络。
其中主用 NAT设备所述主用 NAT设备还用于， 生成地址映射表项， 并将 所述地址映射表项同步到所述备用 NAT设备的地址映射表， 所述地址映射表 项为从所述 IPv4 addres s pool中为 IPv6主机分配的 IPv4地址与所述 IPv6 主机的 IPv6地址之间的映射关系。
该系统中， 在所述第一装置上配置第一实例和第二实例， 在第二装置上 也配置所述第一实例和所述第二实例， 所述第一实例和第二实例分别确定对 应的主用 NAT设备， 以及备用 NAT设备。
其中， 该系统中不同实例对应的主用 NAT设备发布的 pref ix64不同。 具体的所述主用 NAT和备用 NAT设备的系统结构图可以参照图 2的实施 例详细描述， 此处不再赘述。
本发明另一实施例提供了一种实现网络地址翻译 NAT设备冗余备份的方 法， 包括：
S 600、 在至少两个 NAT设备上预先配置第四版互联网协议地址池 IPv4 addres s pool和用于 IPv4地址映射到第六版互联网协议 IPv6地址的前缀 pref ix64。 其中， 所述在至少两个 NAT设备上的配置情况具体如下： 在所述至少两 个 NAT设备上配置不同 IPv4 addres s pool和相同的 pref ix64; 或者，
在所述至少两个 NAT设备上配置不同的 pref ix64和相同的 IPv4 addres s pool ; 或者,
在所述至少两个 NAT设备上配置相同的 IPv4 addres s pool和相同的 pref ix64。
S602、 从所述至少两个 NAT设备中确定一个主用 NAT设备， 以及备用 NAT设 备。
当主用 NAT设备出现故障， 在所述至少两个 NAT设备上配置至少两个实例 所述至少两个实例分别通过自动选举协议或者通过手工配置方式， 从所述至 少两个 NAT设备中分别确定对应的主用 NAT设备， 以及备用 NAT设备； 所述每个 实例对应的主用 NAT设备不相同。
S604、 所述主用 NAT设备在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络发布所述 IPv4 addres s pool对应的路由。
其中， 在所述 S604步骤之后， 所述方法还包括： 所述主用 NAT设备生成地 址映射表项； 所述主用 NAT设备将所述地址映射表项同步到所述备用 NAT设备 的地址映射表。
所述地址映射表项为从所述 IPv4 addres s pool中为 IPv6主机分配的 IPv4 地址与所述 IPv6主机的 IPv6地址之间的映射关系。
S 606、 当所述主用 NAT设备出现故障， 所述备用 NAT设备对源主机和目的 主机之间的数据包进行处理； 其中所述源主机和所述目的主机分别位于不同 的 IP网络。
具体描述为： 在所述至少两个 NAT设备上配置不同的所述 IPv4 addres s pool和所述相同的 pref ix64时，或者在所述至少两个 NAT设备上配置不同的 pref 1x64和所述相同的 IPv4 addres s pool时，目的主机在所述源主机所在网 络的 IP 地址不变； 或者在所述至少两个 NAT 设备上配置相同的所述 IPv4 addres s poo l和所述相同的 pref ix64时，目的主机在所述源主机所在网络的 IP地址不变；并且，所述源主机在所述目的主机所在的网络内的 IP地址不变。
本发明实施例中提供的技术方案， 可以在多个 NAT设备之间实现冷备份、 热备份等冗余备份， 该实施例可以应用于 IPv4网络内的主机访问 IPv6网络内 的主机， 也可以应用于 IPv6网络内的主机访问 IPv4网络内的主机， 从而提高 NAT设备组网的可靠性。 本发明有的实施例中， 可以在实现多个 NAT设备间冗 余备份的同时， 还可以实现多个 NAT设备间的负载分担。
本发明实施例中提供的技术方案， 可以在多个 NAT设备之间实现冗余备 份， 从而提高 NAT设备组网的可靠性。 本发明有的实施例中， 可以在实现多个 NAT设备间冗余备份的同时， 实现多个 NAT设备间的负载分担。
本发明实施例中的部分步骤， 可以利用软件实现， 相应的软件程序可以 存储在可读取的存储介质中， 如光盘或硬盘等。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并不 局限于此， 任何熟悉该技术的人在本发明所揭露的技术范围内， 可轻易想到 的变化或替换， 都应涵盖在本发明的保护范围之内。

Claims

权 利 要 求 书
1、 一种实现网络地址翻译 NAT设备冗余备份的方法， 其特征在于， 包括： 在至少两个 NAT设备上预先配置第四版互联网协议地址池 IPv4 addres s poo 1和用于将 I Pv4地址映射到第六版互联网协议 I Pv 6地址的前缀 pr ef i x64； 从所述至少两个 NAT设备中确定一个主用 NAT设备， 以及备用 NAT设备； 所述主用 NAT设备在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络 发布所述 IPv4 addres s pool对应的路由；
当所述主用 NAT设备出现故障，所述备用 NAT设备对源主机和目的主机之间 的数据包进行处理， 其中所述源主机和所述目的主机分别位于不同的 IP网络。
2、 如权利要求 1所述的方法， 其特征在于， 所述当所述主用 NAT设备出现故 障之前还包括：
所述主用 NAT设备生成地址映射表项， 其中， 所述地址映射表项为从所述 IPv4 addres s pool中为 IPv6主机分酉己的 IPv4地址与所述 IPv6主机的 IPv6地址之 间的映射关系；
所述主用 NAT设备将所述地址映射表项同步到所述备用 NAT设备的地址映 射表。
3、 如权利要求 1所述的方法， 其特征在于， 所述至少两个 NAT设备上预先 配置第四版互联网协议地址池 IPv4 addres s poo l和用于 IPv4地址映射到第六 版互联网协议 IPv6地址的 pref ix64具体包括：
在所述至少两个 NAT设备上预先配置不同的所述 IPv4 addres s pool和相 同的所述 pref ix64 , 相应地， 当所述备用 NAT设备对源主机和目的主机之间的 数据包进行处理之前，目的主机在所述源主机所在网络的 IP地址不变； 或者， 在所述至少两个 NAT设备上预先配置不同的所述 pref ix64 和相同的所述 IPv4 addres s pool , 相应地， 当所述备用 NAT设备对源主机和目的主机之间的 数据包进行处理之前，目的主机在所述源主机所在网络的 IP地址不变； 或者， 在所述至少两个 NAT设备上预先配置相同的所述 IPv4 addres s pool和相 同的所述 pref ix64 , 相应地， 当所述备用 NAT设备对源主机和目的主机之间的 数据包进行处理之前，目的主机在所述源主机所在网络的 IP地址不变， 且所述 源主机在所述目的主机所在的网络内的 I P地址不变。
4、 如权利要求 1所述的方法， 其特征在于， 所述方法还包括：
在所述至少两个 NAT设备上配置至少两个实例，所述每个所述实例对应的所 述主用 NAT设备不相同。
5、 一种实现网络地址翻译 NAT设备冗余备份的装置， 其特征在于， 包括： 存储模块、 路由信息发布模块和数据包处理模块；
所述存储模块， 用于存储配置的第四版互联网协议地址池 IPv4 addres s pool和用于将 IPv4地址映射到第六版互联网协议 IPv6地址的前缀 pref ix64; 所述路由信息发布模块， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并在 IPv4网络发布所述 IPv4 addres s pool对应的路由；
所述数据包处理模块， 用于对源主机和目的主机之间的数据包进行处理， 其中所述源主机和所述目的主机分别位于不同的 I P网络。
6、 如权利要求 5所述的装置， 其特征在于， 所述装置还包括：
地址映射表项生成模块， 用于在所述数据包处理模块处理来自源主机的数 据包后， 生成地址映射表项， 其中， 所述地址映射表项为从所述 IPv4 addres s pool中为 IPv6主机分配的 IPv4地址与所述 IPv6主机的 IPv6地址之间的映射关 系；
所述存储模块， 还用于存储所述地址映射表项生成模块生成的地址映射表 项；
所述同步模块， 用于将所述地址映射表项同步到备用 NAT设备的地址映射 表。
7、 如权利要求 5所述的装置， 其特征在于， 所述存储模块具体用于： 在所述至少两个 NAT设备上存储预先配置的不同的所述 IPv4 addres s pool 和所述相同的 pref ix64; 或者，
在所述至少两个 NAT设备上存储预先配置的不同的 pref ix64和所述相同的 IPv4 addres s pool ; 或者,
在所述至少两个 NAT设备上存储预先配置的相同的所述 IPv4 addres s pool 和所述相同的 pref ix64。
8、 一种实现网络地址翻译 NAT设备冗余备份的系统， 其特征在于， 包括： 第一装置和第二装置， 在所述第一装置和第二装置上配置第四版互联网协议地 址池 IPv4 addres s pool和用于 IPv4地址映射到第六版互联网协议 IPv6地址 的前缀 pref ix64; 从所述第一装置和第二装置中确定一个主用 NAT设备， 以及 备用 NAT设备；
所述主用 NAT设备， 用于在 IPv6网络发布所述 Pref ix64对应的路由， 并 在 IPv4网络发布所述 IPv4 addres s pool对应的路由；
所述备用 NAT设备， 用于当所述主用 NAT设备出现故障时，对源主机和目的 主机之间的数据包进行处理； 其中所述源主机和所述目的主机分别位于不同的 IP网络。
9、 如权利要求 8所述的系统， 其特征在于， 所述主用 NAT设备还用于， 生 成地址映射表项， 并将所述地址映射表项同步到所述备用 NAT设备的地址映射 表， 所述地址映射表项为从所述 IPv4 addres s pool中为 IPv6主机分配的 IPv4 地址与所述 IPv6主机的 IPv6地址之间的映射关系。
PCT/CN2009/072004 2009-03-13 2009-05-26 一种实现nat设备冗余备份的方法、装置和系统 WO2010102465A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP09841334A EP2408151A4 (en) 2009-03-13 2009-05-26 METHOD, DEVICE AND SYSTEM FOR IMPLEMENTING REDUNDANCY BACKUP OF NAT DEVICES
US13/231,426 US20120005299A1 (en) 2009-03-13 2011-09-13 Method, apparatus, and system for implementing redundancy backup between nat devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910105800A CN101834831A (zh) 2009-03-13 2009-03-13 一种实现nat设备冗余备份的方法、装置和系统
CN200910105800.9 2009-03-13

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/231,426 Continuation US20120005299A1 (en) 2009-03-13 2011-09-13 Method, apparatus, and system for implementing redundancy backup between nat devices

Publications (1)

Publication Number Publication Date
WO2010102465A1 true WO2010102465A1 (zh) 2010-09-16

Family

ID=42718763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072004 WO2010102465A1 (zh) 2009-03-13 2009-05-26 一种实现nat设备冗余备份的方法、装置和系统

Country Status (5)

Country Link
US (1) US20120005299A1 (zh)
EP (1) EP2408151A4 (zh)
KR (1) KR20110125259A (zh)
CN (1) CN101834831A (zh)
WO (1) WO2010102465A1 (zh)

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9397979B2 (en) * 2009-04-22 2016-07-19 Hewlett Packard Enterprise Development Lp Router method and system
US10079917B2 (en) * 2010-04-26 2018-09-18 Nokia Technologies Oy Method and apparatus for synthesized address detection
CN103023797B (zh) * 2011-09-23 2016-06-15 百度在线网络技术（北京）有限公司 数据中心系统及装置和提供服务的方法
CN102315926B (zh) * 2011-10-11 2014-12-24 华为数字技术（成都）有限公司 一种主用设备选择方法、网关设备及网络系统
CN103139077B (zh) * 2011-11-28 2016-01-20 百度在线网络技术（北京）有限公司 扩展IPv6虚拟路由器的方法、系统及装置
CN102447703B (zh) * 2011-12-28 2018-06-19 中兴通讯股份有限公司 一种热备份方法和系统、cgn设备
JP5861772B2 (ja) * 2012-03-30 2016-02-16 日本電気株式会社 ネットワークアプライアンス冗長化システム、制御装置、ネットワークアプライアンス冗長化方法及びプログラム
US9407493B2 (en) 2012-04-19 2016-08-02 Futurewei Technologies, Inc. System and apparatus for router advertisement options for configuring networks to support multi-homed next hop routes
CN103379185B (zh) * 2012-04-26 2016-08-03 华为技术有限公司 一种网络地址转换的方法、设备和系统
CN103428229A (zh) * 2012-05-14 2013-12-04 百度在线网络技术（北京）有限公司 数据中心系统、装置及提供服务的方法
JP5445626B2 (ja) * 2012-06-25 2014-03-19 横河電機株式会社 ネットワーク管理システム
US9391951B2 (en) * 2013-08-29 2016-07-12 Alcatel Lucent Communication network with distributed network address translation functionality
CN105491175A (zh) * 2014-09-18 2016-04-13 中兴通讯股份有限公司 一种网络地址转换方法及装置
JP6471451B2 (ja) * 2014-10-16 2019-02-20 株式会社リコー 伝送システム、通信制御装置、通信制御方法、通信方法、プログラム
CN105791448B (zh) 2014-12-18 2019-10-25 华为技术有限公司 一种地址分配方法、cgn设备及cgn双主系统
EP3062490B1 (de) * 2015-02-27 2018-07-18 Siemens Aktiengesellschaft Verfahren zur Datenübermittlung innerhalb eines industriellen Automatisierungssystems und Kommunikationsgerät
CN107222514B (zh) * 2016-03-22 2020-01-14 阿里巴巴集团控股有限公司 一种负载方法和系统
US10382392B2 (en) * 2016-08-01 2019-08-13 Big Switch Networks, Inc. Systems and methods for network address translation
US10630800B2 (en) * 2016-08-09 2020-04-21 Facebook, Inc. Methods and systems for handling requests regarding zero-rating
CN106330542B (zh) * 2016-08-23 2020-01-31 哈尔滨海能达科技有限公司 异地备份交换机的访问方法、控制装置、系统及设备
US10142221B2 (en) * 2016-09-07 2018-11-27 T-Mobile Usa, Inc. Network address translation in networks using multiple NAT devices
CN106453664A (zh) * 2016-12-16 2017-02-22 广东睿哲科技股份有限公司 一种基于虚拟IPv4地址池的IPv4终端、IPv6服务互通业务负载均衡系统
US11012407B2 (en) * 2017-10-27 2021-05-18 Dell Products L.P. System and method of utilizing multiple networks
CN108200223B (zh) * 2017-12-28 2021-05-07 新华三技术有限公司 运营商级网络地址转换设备cgn备份方法和装置
CN109450841B (zh) * 2018-09-03 2020-12-04 中新网络信息安全股份有限公司 一种基于云+端设备按需联动模式的抗大规模DDoS攻击的防御方法
EP3641278A1 (de) * 2018-10-17 2020-04-22 Siemens Aktiengesellschaft Verfahren zur bereitstellung redundanter relay-, insbesondere routing funktion, system, computerprogramm und computerlesbares medium
CN109995890B (zh) * 2019-03-08 2022-04-22 平安科技（深圳）有限公司 一种管理网络地址转换nat网关的方法及服务器
CN111131547B (zh) * 2019-12-30 2022-04-19 浪潮云信息技术股份公司 一种nat网关主备切换时避免tcp连接中断的方法
US11616755B2 (en) * 2020-07-16 2023-03-28 Vmware, Inc. Facilitating distributed SNAT service
US11496439B1 (en) * 2021-03-23 2022-11-08 Amazon Technologies, Inc. Stateless high-capacity network address translation service
CN113691645B (zh) * 2021-08-17 2024-05-21 浪潮思科网络科技有限公司 一种基于m-lag环境实现nat的方法、设备、存储介质
CN113746954B (zh) * 2021-09-22 2023-06-13 烽火通信科技股份有限公司 一种nat地址块二次分配迅速回收的方法和装置
CN115348207B (zh) * 2022-07-21 2023-08-15 佛山职业技术学院 一种基于udp的主备nat设备流表同步方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6687222B1 (en) * 1999-07-02 2004-02-03 Cisco Technology, Inc. Backup service managers for providing reliable network services in a distributed environment
US20040165602A1 (en) * 2003-02-21 2004-08-26 Samsung Electronics Co., Ltd. Method and apparatus for interconnecting IPv4 and IPv6 networks
CN101136926A (zh) * 2007-10-12 2008-03-05 杭州华三通信技术有限公司 非对称路由情况下的报文转发方法及网络地址转换网关
CN101141494A (zh) * 2007-10-12 2008-03-12 杭州华三通信技术有限公司 一种解决负载分担情况下资源分配冲突的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7042876B1 (en) * 2000-09-12 2006-05-09 Cisco Technology, Inc. Stateful network address translation protocol implemented over a data network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6687222B1 (en) * 1999-07-02 2004-02-03 Cisco Technology, Inc. Backup service managers for providing reliable network services in a distributed environment
US20040165602A1 (en) * 2003-02-21 2004-08-26 Samsung Electronics Co., Ltd. Method and apparatus for interconnecting IPv4 and IPv6 networks
CN101136926A (zh) * 2007-10-12 2008-03-05 杭州华三通信技术有限公司 非对称路由情况下的报文转发方法及网络地址转换网关
CN101141494A (zh) * 2007-10-12 2008-03-12 杭州华三通信技术有限公司 一种解决负载分担情况下资源分配冲突的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2408151A4 *

Also Published As

Publication number Publication date
EP2408151A1 (en) 2012-01-18
EP2408151A4 (en) 2012-03-21
CN101834831A (zh) 2010-09-15
KR20110125259A (ko) 2011-11-18
US20120005299A1 (en) 2012-01-05

Similar Documents

Publication Publication Date Title
WO2010102465A1 (zh) 一种实现nat设备冗余备份的方法、装置和系统
US9912495B2 (en) Virtual layer 2 and mechanism to make it scalable
US10367730B2 (en) Layer two over multiple sites
US8879394B2 (en) Method and system of packet based identifier locator network protocol (ILNP) load balancing and routing
EP2580900B1 (en) Enhancing DS-Lite with private IPv4 reachability
US9634934B2 (en) Dynamic host configuration protocol relay in a multipod fabric
US20140115135A1 (en) Method and system of frame based identifier locator network protocol (ilnp) load balancing and routing
CN103227787B (zh) 一种基于ARP代理的4over6隧道自动建立方法
US20140032782A1 (en) Method and apparatus for route selection of host in multihoming site
WO2013159549A1 (zh) 一种建立和使用浮动网段的方法、装置和系统
US9548887B2 (en) Proactive creation of multicast state in an overlay transport network to achieve fast convergence on failover
JP2009206562A (ja) ＩＰｖ４−ＩＰｖ６トランスレータ装置およびダミーアドレス返答方法
JP2005086256A (ja) トンネルゲートウェイ装置
KR102211282B1 (ko) 데이터 라우팅 방법 및 이를 지원하는 스위치
JP2010157857A (ja) Ｖｐｎ接続装置、パケット制御方法、及びプログラム
JP6263926B2 (ja) 通信装置、ゲートウェイ、冗長システム、及び通信システム
CN117978760A (zh) 接入备份方法及设备
JP2023101924A (ja) 通信制御装置、通信制御システム、通信制御方法及びプログラム
WO2013181991A1 (zh) 报文处理方法、系统及路由设备
Hao et al. Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 Gateway
WO2016070631A1 (zh) 数据传输方法、装置和系统
JP2014204421A (ja) 通信制御装置、及び通信制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09841334

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 6749/CHENP/2011

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2009841334

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20117023066

Country of ref document: KR

Kind code of ref document: A