CN117176559A - NAT 64-based cross-protocol stack network fault positioning method and system - Google Patents
NAT 64-based cross-protocol stack network fault positioning method and system Download PDFInfo
- Publication number
- CN117176559A CN117176559A CN202311439851.1A CN202311439851A CN117176559A CN 117176559 A CN117176559 A CN 117176559A CN 202311439851 A CN202311439851 A CN 202311439851A CN 117176559 A CN117176559 A CN 117176559A
- Authority
- CN
- China
- Prior art keywords
- network
- cross
- address
- diagnosis
- equipment
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000000977 initiatory effect Effects 0.000 claims abstract description 20
- 238000004891 communication Methods 0.000 claims abstract description 16
- 238000003745 diagnosis Methods 0.000 claims description 87
- 238000012545 processing Methods 0.000 claims description 22
- 230000004044 response Effects 0.000 claims description 22
- 239000003795 chemical substances by application Substances 0.000 claims description 11
- 238000006243 chemical reaction Methods 0.000 claims description 10
- 239000003999 initiator Substances 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 6
- 238000013507 mapping Methods 0.000 claims description 5
- 238000012986 modification Methods 0.000 abstract description 8
- 230000004048 modification Effects 0.000 abstract description 8
- 238000012360 testing method Methods 0.000 abstract description 8
- 230000009191 jumping Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- PCTMTFRHKVHKIS-BMFZQQSSSA-N (1s,3r,4e,6e,8e,10e,12e,14e,16e,18s,19r,20r,21s,25r,27r,30r,31r,33s,35r,37s,38r)-3-[(2r,3s,4s,5s,6r)-4-amino-3,5-dihydroxy-6-methyloxan-2-yl]oxy-19,25,27,30,31,33,35,37-octahydroxy-18,20,21-trimethyl-23-oxo-22,39-dioxabicyclo[33.3.1]nonatriaconta-4,6,8,10 Chemical compound C1C=C2C[C@@H](OS(O)(=O)=O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H]([C@H](C)CCCC(C)C)[C@@]1(C)CC2.O[C@H]1[C@@H](N)[C@H](O)[C@@H](C)O[C@H]1O[C@H]1/C=C/C=C/C=C/C=C/C=C/C=C/C=C/[C@H](C)[C@@H](O)[C@@H](C)[C@H](C)OC(=O)C[C@H](O)C[C@H](O)CC[C@@H](O)[C@H](O)C[C@H](O)C[C@](O)(C[C@H](O)[C@H]2C(O)=O)O[C@H]2C1 PCTMTFRHKVHKIS-BMFZQQSSSA-N 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 239000004576 sand Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Abstract
The invention discloses a network fault positioning method and system of a cross-protocol stack based on NAT64, wherein the system comprises an initiating device, a cross-network device and a destination device, the initiating device is in communication connection with the cross-network device through a first network, and the cross-network device is in communication connection with the destination device through a second network. The invention can realize the Ping route reachability test from IP end to end and the positioning of the first network and the second network traceroute path without any modification to windows, linux, network equipment and the like.
Description
Technical Field
The invention relates to the technical field of network communication, in particular to a network fault positioning method and system based on a NAT64 cross protocol stack.
Background
Internet protocol version 4 (Internet Protocol version 4) IPv4, the IPv4 protocol being the core of the internet and the most widely used version of the internet protocol. The IPv4 address can be written in any form representing a 32-bit integer value, but for ease of human reading and analysis it is typically written in dot-decimal form, i.e. four bytes are written separately in decimal notation, with dots separating the middle, for example 10.21.11.13.
IPv6 is an abbreviation of english "Internet Protocol Version 6" (internet protocol version 6), which is the next generation IP protocol designed by the Internet Engineering Task Force (IETF) to replace IPv4, and its number of addresses is said to be one address per sand worldwide. The biggest problem of IPv4 is that network address resources are insufficient, which severely restricts the application and development of the internet. The use of IPv6 not only solves the problem of the number of network address resources, but also solves the obstacle of connecting various access devices to the Internet. The address length of IPv6 is 128 bits, which is 4 times the address length of IPv 4. Then the IPv4 point decimal format is not applicable any more, hexadecimal representation is adopted, and the format is X: X: X: X: X: X, wherein each X represents 16 bits in an address, in hexadecimal, for example: ABCD:EF01:2345:6789:ABCD:EF01:2345:6789.
Disclosure of Invention
Therefore, the technical problem to be solved by the invention is to provide a method and a system for positioning network faults of a cross-protocol stack based on NAT64, which can realize Ping route reachability test and first network and second network traceroute path positioning from IP end to end without any modification to windows, linux, network equipment and the like.
In order to solve the technical problems, the invention provides the following technical scheme:
the network fault positioning method based on the NAT64 is used for positioning network faults of a complex network, wherein the complex network comprises a network crossing device, an initial device arranged in a first network and a destination device arranged in a second network, and the network crossing device is internally provided with an NAT64 unit; the method comprises the following steps: in the process of performing cross-protocol stack network fault positioning, when an ICMPv4 echo reply message is converted into an ICMPv6 echo reply message, a cross-network device embeds a source IPv4 address of the ICMPv4 echo reply message into a source IPv6 address of the ICMPv6 echo reply message.
The method comprises the following steps:
s1) the starting equipment performs fault diagnosis on a network path between the starting equipment and the cross-network equipment and records a diagnosis result, and when no network fault exists on the network path between the starting equipment and the cross-network equipment, the starting equipment sends diagnosis information generated according to a diagnosis command to the target equipment through the cross-network equipment;
s2) after receiving diagnostic information generated according to the diagnostic command and sent by the starting equipment, the cross-network equipment performs fault diagnosis on a network path between the cross-network equipment and the target equipment according to the diagnostic information and returns a diagnosis result to the starting equipment; in the cross-network device, the data processing unit matches the diagnosis information with the session table generated by the NAT64 unit, if the diagnosis information is not matched with the session table generated by the NAT64 unit, the diagnosis information is forwarded according to the routing table, otherwise, DNAT processing is carried out on the diagnosis information matched with the session table generated by the NAT64 unit, the target IP address in the diagnosis information is converted into an IP address matched with the IP routing table, and network faults between the cross-network device and the target device are diagnosed by utilizing the converted target IP address.
In the above method, in step S2), the cross-network device first determines the diagnostic information, if the target IP address in the diagnostic information is the interface address of the cross-network device, the cross-network device automatically responds and triggers the start device to stop sending the diagnostic information, otherwise, when ttl=1, the cross-network device sends a TTL timeout error message to the start device, and when TTL is greater than or equal to 2, the data processing unit matches the diagnostic information with the session table generated by the NAT64 unit.
In step S2), the diagnostic information is converted by the Socket proxy module according to the session table generated by the NAT64 unit.
In the above method, in step S2), after the diagnostic information is converted, the converted diagnostic information is sent to the destination device in a manner that the TTL value is gradually +1 with the converted IP address. When the converted IP address is the interface address of the cross-network equipment, different communication data streams are distinguished in an IP+port mode, when the converted IP address is the address in the NAT address pool, network fault diagnosis is carried out by using the IP address in the NAT address pool as a source IP address instead of the IP address of the interface of the cross-network equipment, and different communication data streams are distinguished in an IP < - - > IP mode.
In the above method, in step S2), after receiving the diagnosis result, the cross-network device converts the diagnosis result according to the reverse mapping mode of the session table generated by the NAT64 unit, and then sends the converted diagnosis result to the initiator device.
In the method, in step S1), when a network path between the initiating device and the cross-network device is diagnosed in an ICMP message manner and a network fault exists as a diagnosis result, the initiating device performs fault diagnosis on the network path between the initiating device and the cross-network device again in a UDP message manner; in step S2), when the ICMP message is used to perform fault diagnosis on the network path between the cross-network device and the destination device and the diagnosis result is that there is a network fault, the cross-network device performs fault diagnosis on the network path between the cross-network device and the destination device again in the UDP message.
A system for performing cross-protocol stack network fault location by using the cross-protocol stack network fault location method based on NAT64 is used for complex network fault location, wherein the complex network comprises a cross-network device, an initial device arranged in a first network and a destination device arranged in a second network; the system comprises:
the starting equipment is used for initiating network fault positioning diagnosis;
the cross-network equipment is used for carrying out communication protocol conversion; the cross-network equipment is internally provided with an NAT64 unit and a data processing unit, and the data processing unit is internally provided with a DNAT module and a Socket agent module; in the process of performing cross-protocol stack network fault positioning, when an ICMPv4 echo reply message is converted into an ICMPv6 echo reply message, a Socket agent module embeds a source IPv4 address of the ICMPv4 echo reply message into a source IPv6 address of the ICMPv6 echo reply message;
the starting device is in communication connection with the cross-network device through a first network, and the cross-network device is in communication connection with the destination device through a second network.
In the system, a reverse hash decoder is arranged in the starting equipment; when the ICMPv6 back display response message is converted into the ICMPv4 back display response message, the Socket agent module changes the source IPv6 address of the ICMPv6 back display response message into information with a Hash IPv4 address format, and the starting equipment decodes the information with the Hash IPv4 address format through the reverse Hash decoder to obtain the source IPv6 address of the ICMPv6 back display response message.
In the system, a trace route component is built in the system of the starting equipment.
The technical scheme of the invention has the following beneficial technical effects:
1. the method has the advantages that no modification is needed to be made to windows, linux, network equipment and the like, when the ICMPv6 source end is used for accessing the IPv4 application service, component optimization is performed on the NAT64 equipment, and the Ping route reachability test from the IP end to the end can be realized; trace route tracking of IP full paths can be implemented.
2. The method does not need to make any modification to windows, linux, network equipment and the like, can be used as an ICMPv4 source end to access the IPv6 application service, performs component optimization on the NAT46 equipment, and can realize the Ping route reachability test from IP end to end.
3. And the ICMPv6 protocol trace route transparent transfer conversion test request message is transmitted to the IPv4 target network on the premise that the initial equipment does not make any modification.
4. Only one reverse Hash decoder component is required to be installed on window, linux and network equipment, and when the reverse Hash decoder component can be used as an ICMPv4 source end to access IPv6 application service, component optimization is performed on the passing NAT46 equipment, so that the Ping route reachability test from IPv4 to IPv6 end to end can be realized. Trace route tracking from IPv4 to IPv6 end-to-end can be implemented.
5. The protocol exchange platform supports the conversion of UDP mode detection messages to support the Ping route reachability test of IPv4/IPv6 end-to-end of the cross-protocol stack and the cross-security product. Trace route tracking from IPv4/IPv6 end to end can be realized.
6. Supporting Ping route reachability test across protocol stack application proxy, translation data flow path IPv4/IPv6 end-to-end. Trace route tracking from IPv4/IPv6 end to end can be realized.
Drawings
FIG. 1 is a schematic diagram of the operation of a NAT-based network fault location system across protocol stacks;
FIG. 2 is a flow chart of the cross protocol stack network fault localization in the present invention;
FIG. 3 is a diagram showing the full-service path information after the trace route command is successfully executed;
fig. 4 is a diagram showing the full-service path information after the trace route command is not successfully executed.
Detailed Description
The invention is further described below with reference to examples.
As shown in fig. 1, in the present invention, a network fault location system based on a NAT64 is used for locating a fault of a complex network, where the complex network includes a network-crossing device, an initiating device disposed in a first network, and a destination device disposed in a second network; the system comprises an initiating device, a cross-network device and a destination device, wherein the initiating device is in communication connection with the cross-network device through a first network, and the cross-network device is in communication connection with the destination device through a second network. The system of the initial equipment is internally provided with a trace route component; the cross-network equipment is used for carrying out communication protocol conversion; the cross-network equipment is internally provided with an NAT64 unit and a data processing unit, and the data processing unit is internally provided with a DNAT module and a Socket agent module; in the process of performing cross-protocol stack network fault positioning, when an ICMPv4 echo reply message is converted into an ICMPv6 echo reply message, a Socket agent module embeds a source IPv4 address of the ICMPv4 echo reply message into a source IPv6 address of the ICMPv6 echo reply message.
In this embodiment, a reverse hash decoder is disposed in the initiator; when the ICMPv6 back display response message is converted into the ICMPv4 back display response message, the Socket agent module changes the source IPv6 address of the ICMPv6 back display response message into information with a Hash IPv4 address format, and the starting equipment decodes the information with the Hash IPv4 address format through the reverse Hash decoder to obtain the source IPv6 address of the ICMPv6 back display response message.
The invention uses the NAT 64-based network fault locating system of the network fault of the cross protocol stack to locate the network fault of the cross protocol stack, as shown in figure 2, comprising the following steps:
s1) the starting equipment performs fault diagnosis on a network path between the starting equipment and the cross-network equipment and records a diagnosis result, and when no network fault exists on the network path between the starting equipment and the cross-network equipment, the starting equipment sends diagnosis information generated according to a diagnosis command to the target equipment through the cross-network equipment;
s2) after receiving diagnostic information generated according to the diagnostic command and sent by the starting equipment, the cross-network equipment performs fault diagnosis on a network path between the cross-network equipment and the target equipment according to the diagnostic information and returns a diagnosis result to the starting equipment; in the cross-network device, the data processing unit matches the diagnosis information with the session table generated by the NAT64 unit, if the diagnosis information is not matched with the session table generated by the NAT64 unit, the diagnosis information is forwarded according to the routing table, otherwise, DNAT processing is carried out on the diagnosis information matched with the session table generated by the NAT64 unit, the target IP address in the diagnosis information is converted into an IP address matched with the IP routing table, and network faults between the cross-network device and the target device are diagnosed by utilizing the converted target IP address.
In step S2), the cross-network device judges the diagnostic information first, if the target IP address in the diagnostic information is the interface address of the cross-network device, the cross-network device automatically responds and triggers the start device to stop sending the diagnostic information, otherwise, when ttl=1, the cross-network device sends a TTL timeout error message to the start device, and when TTL is greater than or equal to 2, the data processing unit matches the diagnostic information with the session table generated by the NAT64 unit.
In step S2), in the cross-network device, the Socket proxy module converts the diagnostic information according to the session table generated by the NAT64 unit, and after converting the diagnostic information, the converted diagnostic information is sent to the destination device in a manner of gradually +1 according to the TTL value by using the converted IP address, and after receiving the diagnostic result, the cross-network device converts the diagnostic result in a reverse mapping manner according to the session table generated by the NAT64 unit, and then sends the converted diagnostic result to the initiator device.
Specifically, the cross-network device, upon receiving the diagnostic information sent by the initiator device, processes the diagnostic information according to the following procedures:
s101) receiving diagnosis information from the starting equipment, monitoring the diagnosis information, analyzing whether a target address in the diagnosis information is an IP address of the cross-network equipment, if so, jumping to the step S102) for continuous execution, otherwise, jumping to the step S103) for continuous execution;
s102) sending a Reply message with reachable route to the initial equipment according to the processing flow of the Internet communication protocol;
s103) judging whether the TTL value of the diagnosis information is 1, if so, jumping to the step S104) to continue execution, otherwise, jumping to the step S105) to continue execution;
s104) discarding the diagnosis information and replying a TTL overtime error message to the initial equipment;
s105) matching the diagnosis information with a session table generated by the NAT unit, if the diagnosis information is not matched, jumping to the step S106) to continue execution, otherwise, jumping to the step S109) to continue execution;
s106) forwarding the diagnosis information according to the routing table of the first network, and forwarding the diagnosis result normally, specifically, matching the IP address in the diagnosis information with the routing table of the first network to determine an interface, and forwarding the diagnosis information after the IP address in the diagnosis information is converted by the corresponding protocol conversion interface;
s107), the next hop router positioned in the second network returns a diagnosis result according to the diagnosis information processing flow;
s108) receiving the diagnosis result and monitoring the diagnosis result by the cross-network equipment, converting the received diagnosis result into a diagnosis result conforming to the first network communication protocol according to a session table reverse mapping mode generated by the NAT64 unit until the diagnosis is finished, forwarding the diagnosis result (such as TTL timeout message and echo message) to the starting equipment, and then jumping to the step S112) for continuous execution; when the first network is an IPv6 network and the second network is an IPv4 network, before forwarding the diagnosis result to the initiator device, a source IPv4 address of the diagnosis result may be embedded into the IPv6 address;
s109) performing DNAT processing on the diagnosis information, specifically performing IP conversion on a target address in the diagnosis information, for example, converting an IPv6 address of a target device in the diagnosis information into an IPv4 address, and then inquiring a routing table of a network where the target device is located according to the converted IP address to determine an interface;
s110) after determining an interface, processing diagnostic information according to a session table generated by the NAT64 unit, for example, converting an ICMPv6 echo request message into an ICMPv4 echo request message, then sequentially transmitting the converted diagnostic information (for example, the ICMPv4 echo request message) to a destination device in a mode of gradually increasing TTL values by taking the converted IP address as a source address, stopping transmitting the diagnostic information if a diagnostic result (for example, the ICMPv4 echo response message) is received, and then automatically stopping overtime by default TTL;
s111) the cross-network equipment forwards the received diagnosis result to the starting equipment, and the step 112) is skipped to continue to be executed;
s112) the initiating device presents the diagnostic result.
In view of that some network devices are in safety consideration and have forbidden to reply to an ICMP message or directly discard an ICMP message, all the devices along the way may not be detected by adopting the ICMP message, and in order to avoid the problem of diagnosis errors or failure caused by forbidden to reply to the ICMP message or discarding the ICMP message, the network fault location system based on the NAT64 in the invention can also realize network fault location through the following steps:
s21) when the network path between the starting equipment and the cross-network equipment is subjected to fault diagnosis in an ICMP message mode and the diagnosis result is that the network fault exists, the starting equipment carries out fault diagnosis on the network path between the starting equipment and the cross-network equipment again in a UDP message mode;
s22) when the fault diagnosis is carried out on the network path between the cross-network equipment and the target equipment in the ICMP message mode and the diagnosis result is that the network fault exists, the cross-network equipment carries out the fault diagnosis on the network path between the cross-network equipment and the target equipment again in the UDP message mode.
The method adopts a mode of carrying UDP messages to carry out network fault location of a cross protocol stack, and is characterized in that ICMP is a standard network fault location protocol, ICMP is also a protocol for detecting whether a target network IP exists or not, and is easy to be utilized by hackers, and common technicians discard ICMP from an external network along with popularization of a firewall, but the firewall defaults not to discard UDP, and only can discard UDP messages with special detailed limitation, so that UDP messages easily pass through the firewall, and more complete equipment information along the way can be obtained.
When the UDP message is used for carrying out network fault positioning across the protocol stack, when the initiating device inputs a traceroute command+IP, the initiating device initiates a UDP message, the port of the UDP message is set to be more than 30000 and the illegal value which is not generally used by the target device. When the message of the diagnosis result is a UDP message, the intermediate node (including a cross-network device, a router, a switch and the like) still returns an ICMP timeout message of the source IP address because of timeout of the message TTL, which is the same as the ICMP message. When the UDP message does not reach the target device, TTL is increased by 1, and the diagnosis is advanced. When the message reaches the destination device, the message returns an ICMP port unreachable message because the UDP port is more than 30000 when the message sends the processing result of the transmission layer, thereby realizing Trace route.
The present embodiment will be described by taking an example in which an initiator device is in an IPv6 network and a target device is in an IPv4 network.
In the first step, a trace route component built in the system of the initiating device is started through a system command of the initiating device, for example, a component based on ICMPv6 protocol is started through trace 2000:2000:1 under CMD of Windows system, and is used for tracking path information of target service 2000:2000:1. As can be seen from FIG. 3, 2000:2000:1 is the IPv6 address provided across network devices, while the actual target device IP address is 172.16.1.100.
Traceroute implementation mode based on ICMPv6 message: when the initial device inputs a traceroute command+ip, the initial device will send an ICMP echo request message, the first data packet, ttl=1, so that after the initial device receives the ICMP echo request message, the TTL is reduced by 1, that is, the ttl=0 is discarded when the first hop router is to forward the ICMP echo request message, then the first hop router returns an ICMPv6 timeout error message, after the initial device receives the ICMPv6 echo reply message, the initial device will determine whether the ICMPv6 echo reply message is received, if the ICMPv6 echo reply message is not received, the echo request message will be continuously sent, the TTL is increased by 1 to try, and after the server is reached, the server will send the ICMPv6 echo reply message.
Secondly, on the cross-network equipment, the system judges the received ICMPv6 echo request message, and if the target IPv6 address in the ICMPv6 echo request message is a local interface address, the system automatically replies an ICMPv6 echo response to trigger the server to stop transmitting the trace route echo request message. If the target IPv6 address is not the local system interface address and TTL=1, indicating that a TTL overtime error message needs to be sent by the cross-network equipment; when TTL is more than or equal to 2, the normal data packet processing flow is matched with a session table generated by the NAT64 unit.
And a third step of: for the ICMPv6 echo request message matched with the session table generated by the NAT64 unit, DNAT processing is firstly carried out, the target IP address of the ICMPv6 echo request message is modified into an IPv4 address so as to be matched with an IPv4 routing table, the next jump-out interface is determined, and the source IPv4 address is modified according to the session table generated by the NAT64 unit during the interface processing.
And fourthly, realizing the conversion between ICMPv6 and ICMPv4 of the data forwarding layer through a Socket agent module, and particularly performing transparent transmission and response conversion by a Socket agent program in the Socket agent module.
Specifically, the ICMPv6 echo request message is processed according to the table entry of the session table generated by the NAT64 unit, the ICMPv4 echo request message is converted, the converted IPv4 address is taken as the source IPV4 address, and the ICMPv4 echo request message is continuously sent to the converted destination IP address in a mode that TTL value is gradually +1.
The next hop IPv4 router returns the data packet to the cross-network equipment according to the ICMPv4 standard flow, the cross-network equipment generates the ICMPv6 data packet according to the reverse mapping mode of the session table generated by the NAT64 unit, until the IPv4 echo response message is processed.
In order to realize that ICMPv6 protocol trace route can be transmitted to an IPv4 target network without any modification on an initiating device, and the trace route function is continuously performed by using ICMPv4 protocol in a proxy mode, when a Socket proxy module of a cross-network device responds to the initiating device, a source IPv6 address of an ICMPv6 response data message needs to carry IPv4 address information, in the invention, the source IPv4 address of the ICMPv4 echo reply message is embedded into the IPv6 address, such as an IPv4 source IP address X.Y.Z.W, and at the moment, the IPv6 address can use FE80 in a format of X:Y:Z or X:Y:Z:W:W, so that the initiating device can identify the IPv4 address information reflected by the IPv6 address in a 'literal' manner.
When the initiating device is located in the IPv4 network and the destination device is located in the IPv6 network, the ICMPv4 protocol cannot be transmitted to the IPv6 network by embedding the IPv4 address into the IPv6 address, which is because the two mechanisms of the IPv4 address are denoted by 32 and the two mechanisms of the IPv6 address are denoted by 128 bits, so that the IPv4 address can be embedded into the IPv6 address, and conversely, the IPv6 address cannot be embedded into the IPv4 address, and therefore, the invention solves the technical problem of how to transmit the ICMPv4 protocol to the IPv6 network and feed back the relevant routing information by adopting the following method: the cross-network device changes the source IP address of the ICMPv4 echo reply message into Hash IPv4 address format information in a Hash (128-bit IPv 6) =32-bit IPv4 address mode, at the moment, the IPv4 address is only digital and has no actual IP address meaning, at the moment, the starting device can display the response IPv4 address, and because the address is the IPv4 address after the Hash, at the moment, the response IPv6 address can be reversely resolved through a reverse Hash decoder deployed on the starting device, and further the method is used for locating fault points.
And stopping sending the ICMP echo request message when receiving the ICMPv4 echo response message. The default TTL overtime automatic stop, the default TTL=30 of the window system and the default TTL=60 of the Linux system, the TTL overtime error message and the response back display message of the ICMPv6 are adopted on the cross-network equipment to influence the window or the Linux end to stop sending continuously, and the default TTL value is adopted to control stopping sending continuously of the response request.
As shown in FIG. 3, after the trace route command is successfully executed, there is no fault point on the service path, wherein 2403:DAC0:1:1 is an address of a neighboring originating device of the cross-network device, FE80:10:1:2:1 is an IPv6 address converted by the cross-network device next-hop IPv4 router 10.1.2.1, and FE80:172:16:1:100 is an IPv6 address converted by the destination device 176.16.1.100.
As shown in fig. 4, when a certain device fails, a request timeout is displayed in the full path information of the callback service, and as can be seen from the information shown in fig. 4, the device with the IPv4 address of 10.1.1.1 has a failure on the interface or path away from the originating device.
It is apparent that the above examples are given by way of illustration only and are not limiting of the embodiments. Other variations or modifications of the above teachings will be apparent to those of ordinary skill in the art. It is not necessary here nor is it exhaustive of all embodiments. While the obvious variations or modifications which are extended therefrom remain within the scope of the claims of this patent application.
Claims (10)
1. The network fault positioning method based on the NAT64 cross protocol stack is characterized by being used for positioning network faults of a complex network, wherein the complex network comprises a cross network device, an initial device arranged in a first network and a target device arranged in a second network, and the cross network device is internally provided with an NAT64 unit; the method comprises the following steps: in the process of performing cross-protocol stack network fault positioning, when an ICMPv4 echo reply message is converted into an ICMPv6 echo reply message, a cross-network device embeds a source IPv4 address of the ICMPv4 echo reply message into a source IPv6 address of the ICMPv6 echo reply message.
2. The method according to claim 1, characterized by the steps of:
s1) the starting equipment performs fault diagnosis on a network path between the starting equipment and the cross-network equipment and records a diagnosis result, and when no network fault exists on the network path between the starting equipment and the cross-network equipment, the starting equipment sends diagnosis information generated according to a diagnosis command to the target equipment through the cross-network equipment;
s2) after receiving diagnostic information generated according to the diagnostic command and sent by the starting equipment, the cross-network equipment performs fault diagnosis on a network path between the cross-network equipment and the target equipment according to the diagnostic information and returns a diagnosis result to the starting equipment; in the cross-network device, the data processing unit matches the diagnosis information with the session table generated by the NAT64 unit, if the diagnosis information is not matched with the session table generated by the NAT64 unit, the diagnosis information is forwarded according to the routing table, otherwise, DNAT processing is carried out on the diagnosis information matched with the session table generated by the NAT64 unit, the target IP address in the diagnosis information is converted into an IP address matched with the IP routing table, and network faults between the cross-network device and the target device are diagnosed by utilizing the converted target IP address.
3. The method according to claim 2, wherein in step S2), the cross-network device first determines the diagnostic information, if the target IP address in the diagnostic information is the interface address of the cross-network device, the cross-network device automatically responds and triggers the initiator device to stop sending the diagnostic information, otherwise, when ttl=1, the cross-network device sends a TTL timeout error message to the initiator device, and when TTL is greater than or equal to 2, the data processing unit matches the diagnostic information with the session table generated by the NAT64 unit.
4. The method according to claim 2, characterized in that in step S2) diagnostic information is translated in the cross-network device by a Socket proxy module according to a session table generated by the NAT64 unit.
5. The method according to claim 2, characterized in that in step S2) after the conversion of the diagnostic information, the converted diagnostic information is transmitted to the destination device in a manner that the TTL value is stepwise +1 in terms of the converted IP address.
6. The method according to claim 2, wherein in step S2), after receiving the diagnosis result, the cross-network device converts the diagnosis result in a reverse mapping manner of the session table generated by the NAT64 unit, and then transmits the converted diagnosis result to the originating device.
7. The method according to claim 2, wherein in step S1), when the network path between the originating device and the cross-network device is diagnosed in ICMP messaging and the diagnosis result is that there is a network failure, the originating device performs the fault diagnosis again in UDP messaging on the network path between the originating device and the cross-network device; in step S2), when the ICMP message is used to perform fault diagnosis on the network path between the cross-network device and the destination device and the diagnosis result is that there is a network fault, the cross-network device performs fault diagnosis on the network path between the cross-network device and the destination device again in the UDP message.
8. A system for cross-protocol stack network fault location using the NAT64 based cross-protocol stack network fault location method of claim 1 for complex network fault location, the complex network comprising a cross-network device, an initiating device disposed within a first network and a destination device disposed within a second network; the system comprises:
the starting equipment is used for initiating network fault positioning diagnosis;
the cross-network equipment is used for carrying out communication protocol conversion; the cross-network equipment is internally provided with an NAT64 unit and a data processing unit, and the data processing unit is internally provided with a DNAT module and a Socket agent module; in the process of performing cross-protocol stack network fault positioning, when an ICMPv4 echo reply message is converted into an ICMPv6 echo reply message, a Socket agent module embeds a source IPv4 address of the ICMPv4 echo reply message into a source IPv6 address of the ICMPv6 echo reply message;
the starting device is in communication connection with the cross-network device through a first network, and the cross-network device is in communication connection with the destination device through a second network.
9. The system of claim 8, wherein the starting device has a reverse hash decoder disposed therein; when the ICMPv6 back display response message is converted into the ICMPv4 back display response message, the Socket agent module changes the source IPv6 address of the ICMPv6 back display response message into information with a Hash IPv4 address format, and the starting equipment decodes the information with the Hash IPv4 address format through the reverse Hash decoder to obtain the source IPv6 address of the ICMPv6 back display response message.
10. The system of claim 8, wherein the initiator device has a trace route component built into the system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311439851.1A CN117176559B (en) | 2023-11-01 | 2023-11-01 | NAT 64-based cross-protocol stack network fault positioning method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311439851.1A CN117176559B (en) | 2023-11-01 | 2023-11-01 | NAT 64-based cross-protocol stack network fault positioning method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117176559A true CN117176559A (en) | 2023-12-05 |
| CN117176559B CN117176559B (en) | 2024-01-16 |
Family
ID=88945277
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311439851.1A Active CN117176559B (en) | 2023-11-01 | 2023-11-01 | NAT 64-based cross-protocol stack network fault positioning method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117176559B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101106495A (en) * | 2007-08-06 | 2008-01-16 | 哈尔滨工业大学 | Work process demonstration device and method for industrial Ethernet simplified IP protocol |
| CN103650424A (en) * | 2013-08-20 | 2014-03-19 | 华为技术有限公司 | Implementation method and server of home gateway service function |
| CN106713528A (en) * | 2017-03-15 | 2017-05-24 | 烽火通信科技股份有限公司 | Home gateway and method of IPv6 host to access network server |
| US20170250907A1 (en) * | 2016-02-29 | 2017-08-31 | Cisco Technology, Inc. | System and method for dataplane-signaled packet capture in ipv6 environment |
| CN107248941A (en) * | 2017-06-30 | 2017-10-13 | 华为技术有限公司 | A kind of method and apparatus in detection path |
| US20190289056A1 (en) * | 2018-03-16 | 2019-09-19 | Bridgewest Ventures LLC | Method and Apparatus for Cross Layer Network Diagnostics and Self-Healing Platform for Point-to-Multipoint Networks |
| CN112600725A (en) * | 2020-11-20 | 2021-04-02 | 四川迅游网络科技股份有限公司 | ICMP message acceleration method |
| CN113507394A (en) * | 2021-06-10 | 2021-10-15 | 广州虎牙科技有限公司 | Network performance detection method and device, electronic equipment and storage medium |
-
2023
- 2023-11-01 CN CN202311439851.1A patent/CN117176559B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101106495A (en) * | 2007-08-06 | 2008-01-16 | 哈尔滨工业大学 | Work process demonstration device and method for industrial Ethernet simplified IP protocol |
| CN103650424A (en) * | 2013-08-20 | 2014-03-19 | 华为技术有限公司 | Implementation method and server of home gateway service function |
| WO2015024168A1 (en) * | 2013-08-20 | 2015-02-26 | 华为技术有限公司 | Method for realizing residential gateway service function and server |
| US20170250907A1 (en) * | 2016-02-29 | 2017-08-31 | Cisco Technology, Inc. | System and method for dataplane-signaled packet capture in ipv6 environment |
| CN106713528A (en) * | 2017-03-15 | 2017-05-24 | 烽火通信科技股份有限公司 | Home gateway and method of IPv6 host to access network server |
| CN107248941A (en) * | 2017-06-30 | 2017-10-13 | 华为技术有限公司 | A kind of method and apparatus in detection path |
| US20190289056A1 (en) * | 2018-03-16 | 2019-09-19 | Bridgewest Ventures LLC | Method and Apparatus for Cross Layer Network Diagnostics and Self-Healing Platform for Point-to-Multipoint Networks |
| CN112600725A (en) * | 2020-11-20 | 2021-04-02 | 四川迅游网络科技股份有限公司 | ICMP message acceleration method |
| CN113507394A (en) * | 2021-06-10 | 2021-10-15 | 广州虎牙科技有限公司 | Network performance detection method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117176559B (en) | 2024-01-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7966420B2 (en) | Enhance fault tracing in multi-tiered Ethernet/MPLS network | |
| US7388829B2 (en) | Method and apparatus for detecting and recovering from faults associated with transport protocol connections across network address translators | |
| US20090161576A1 (en) | Methods And Systems For Sending Information To A Zone Included In An Internet Network | |
| US20060215657A1 (en) | ISATAP tunneling system and method between IPv4 network and IPv6 network | |
| Jankiewicz et al. | Ipv6 node requirements | |
| US20080071927A1 (en) | Method and system for automatic tunneling using network address translation | |
| US8254286B2 (en) | Method and system for detection of NAT devices in a network | |
| US8687503B2 (en) | Technique for identifying a failed network interface card within a team of network interface cards | |
| US20090279426A1 (en) | System and method for dead gateway detection | |
| JP2004179812A (en) | Address translation apparatus and address translation rule management system | |
| US7545741B1 (en) | Technique for identifying a failed network interface card within a team of network interface cards | |
| CN113595897B (en) | Path detection method and device | |
| US7269661B2 (en) | Method using receive and transmit protocol aware logic modules for confirming checksum values stored in network packet | |
| US8891551B2 (en) | IPv6 over IPv4 transition method and apparatus for improving performance of control server | |
| KR20110094128A (en) | Neighbour discovery protocol mediation | |
| WO2013044827A1 (en) | Test method for trace route and system, apparatus and device thereof | |
| US20080212609A1 (en) | ICMP translator | |
| US20070115838A1 (en) | Method and system for loop-back and continue in packet-based network | |
| CN117176559B (en) | NAT 64-based cross-protocol stack network fault positioning method and system | |
| US7626937B2 (en) | System and method for network connection detection | |
| Komu et al. | Sockets Application Program Interface (API) for Multihoming Shim | |
| WO2009005212A1 (en) | Ipv6 over ipv4 transition method and apparatus for improving performance of control server | |
| WO2004071052A1 (en) | Enhanced dns server | |
| JP4472651B2 (en) | Network access system and network access method | |
| CN114268578B (en) | Data transmission method, device, equipment and storage medium for switching line |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |