CN113746944B - IPv6 network point management method and equipment - Google Patents
IPv6 network point management method and equipment Download PDFInfo
- Publication number
- CN113746944B CN113746944B CN202010474400.1A CN202010474400A CN113746944B CN 113746944 B CN113746944 B CN 113746944B CN 202010474400 A CN202010474400 A CN 202010474400A CN 113746944 B CN113746944 B CN 113746944B
- Authority
- CN
- China
- Prior art keywords
- mesh point
- ipv6
- address
- packet
- information
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 105
- 238000000034 method Methods 0.000 claims abstract description 9
- 238000004458 analytical method Methods 0.000 claims description 32
- 238000001514 detection method Methods 0.000 claims description 17
- 238000003491 array Methods 0.000 claims description 13
- 230000000903 blocking effect Effects 0.000 claims description 13
- 210000001072 colon Anatomy 0.000 claims description 11
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 230000001133 acceleration Effects 0.000 claims description 7
- 238000000605 extraction Methods 0.000 claims description 5
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000001788 irregular Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/659—Internet protocol version 6 [IPv6] addresses
-
- 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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- 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/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- 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/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to an IPv6 network point management method, which comprises the following steps: the method comprises a packet collecting step, a packet analyzing step and an IPv6 address allocation step, wherein the packet collecting step, the packet analyzing step and the IPv6 address allocation step are used for allocating the website management IPv6 address with the macroscopic identification address suffix to the object website, so that the identification of the IPv6 address of the object website is improved, and the website management is facilitated. When the IPv6 address is distributed by the DHCPv6, the suffix of the IPv6 address obtained by the object network node is identical with the IPv4 address, namely, the network node with the macroscopic identification address suffix manages the IPv6 address, thereby improving the identification of the IPv6 address of the object network node and being beneficial to the management of the network node.
Description
Technical Field
The present invention relates to IP address management, and in particular, to a method and apparatus for IPv6 mesh point management.
Background
The IP address (Internet protocol address; internet Protocol address) is a digital tag assigned to each device (i.e., a mesh point) on the network that uses the Internet protocol (Internet Protocol), where IPv4 (Internet communication protocol fourth edition; internet Protocol version 4) is the first widely deployed and used version. IPv4 uses 32-bit (4-byte) addresses, while limiting the address space to 4294967296 (2 32) addresses, IPv4 can be represented in any representation that represents a 32-bit integer value, and is typically written in the form of a dot-decimal (dot-decimal) unit.
With the explosion of the Internet, a new generation of IPv6 (Internet protocol version six; internet Protocol version) was proposed to be used to gradually replace IPv4 to deal with the problem of IPv4address exhaustion (IPv 4address exhaustion). Therefore, in networks in recent years, the coexistence of IPv6 addresses and IPv4 addresses is very common. However, the IPv6 address has 128 bits, and the representation form is different from that of the IPv4address, so that in the network environment where the IPv6 address and the IPv4address coexist, it is very difficult to manually identify and manage the IPv4 network point and the IPv6 network point, and there is a need for improvement.
Disclosure of Invention
Therefore, the present invention provides a method and an apparatus for managing an IPv6 network node, which can improve the management identification of the network node, so as to facilitate the manual identification and management of the network node.
The invention provides a IPv6 network point management method for solving the technical means adopted by the prior art, which is applied to a network environment where IPv6 addresses and IPv4 addresses coexist, and manages the network points to which the network environment belongs, wherein the IPv6 network point management method comprises the following steps: a packet collection step, namely collecting the node packets of each node in the network environment by using a packet collection module; a packet analysis step of analyzing each of the node packets collected in the packet collection step by a packet analysis module to obtain node information about each of the nodes from the node packets, the node information containing IP address information and MAC address information, and establishing an IP and MAC correspondence table according to the node information; and an IPv6 address allocation step of allocating the dot management IPv6 address generated according to the IP and MAC correspondence table to the target dot requesting allocation of the IPv6 address by using a DHCPv6 service module, wherein the DHCPv6 service module directly substitutes the number of the decimal array of the individual dot in the configured IPv4 address of the target dot into the number of the hexadecimal array of the colon number which is the end individual corresponding position in the dot management IPv6 address in a mode of not carrying out carry conversion, thereby generating the dot management IPv6 address with the macroscopic identification address suffix.
In an embodiment of the present invention, in the packet analysis step, the IP address information of the node information includes IPv6 address information of the node, and the packet analysis module obtains the node information including the IPv6 address information and/or the MAC address information from a neighbor request packet and/or a neighbor advertisement packet belonging to a neighbor discovery protocol in the node packet.
In an embodiment of the present invention, an IPv6 mesh point management method is provided, wherein in the packet analysis step, the mesh point information including the IPv6 address information and/or the MAC address information is obtained from the mesh point packet, and the method includes the following steps: an IPv6 packet classifying sub-step of classifying the mesh point packet, of which the content of the Ethernet type field of the packet is judged to be 0x86DD, as an IPv6 classified packet; an ICMPv6 packet classifying sub-step of classifying the IPv6 classified packet, in which the content of the next header field of the packet is judged to be "58", as an ICMPv6 classified packet; and an information extraction sub-step of extracting the mesh point information including the IPv6 address information and/or the MAC address information from the ICMPv6 classified packet whose content of the type field of the packet is judged as "135" or "136".
In an embodiment of the present invention, in the step of IPv6 address allocation, the DHCPv6 service module directly substitutes numbers of all four decimal arrays in the configured IPv4 address of the target mesh point into numbers of hexadecimal arrays of colon numbers serving as four corresponding positions at the end in the mesh point management IPv6 address respectively in a manner of not performing carry conversion.
In an embodiment of the present invention, in the IPv6 address allocation step, when the target node is not configured with an IPv4 address, the DHCPv6 service module generates the node management IPv6 address by using a simulated configuration IPv4 address as a configured IPv4 address of the target node, where the simulated configuration IPv4 address is selected from an IPv4 address outside an IPv4 address allocation range of the network environment, or the simulated configuration IPv4 address is selected from a denormal IPv4 address, and the denormal IPv4 address contains at least one hexadecimal number from "a" to "F", or at least one point of the denormal IPv4 address has a decimal number exceeding 8 bits.
In an embodiment of the present invention, an IPv6 node management method is provided, further including an illegal node blocking step of comparing a preset allowed node list with the node information obtained in the packet analysis step, so as to determine whether the node of the configured IPv6 address to which the network environment belongs is a legal node or an illegal node, and blocking the node determined as the illegal node.
In an embodiment of the present invention, an IPv6 network node management method is provided, further comprising an acceleration detection step, wherein the current IP address information of each network node in the IP and MAC mapping table and the IPv6 address allocation range to which the network environment belongs are processed by an operation, so as to obtain a possible IPv6 address range of an undiscovered network node in the IP and MAC mapping table, and send a detection packet for an IPv6 address in the possible IPv6 address range of the undiscovered network node, so as to drive the corresponding network node in the network environment to send the network node packet containing the network node information.
In one embodiment of the present invention, there is provided an IPv6 mesh point management device for executing the above-mentioned IPv6 mesh point management method, where the IPv6 mesh point management device is disposed in the network environment where an IPv6 address and an IPv4 address coexist, and manages a mesh point to which the network environment belongs, and the IPv6 mesh point management device includes: the packet collection module is configured to collect the network point packets of each network point in the network environment; the packet analysis module is connected with the packet collection module, and is configured to analyze each of the node packets collected by the packet collection module, obtain node information about each of the nodes from the node packets, wherein the node information contains the IP address information and the MAC address information, and establish the IP and MAC corresponding relation table according to the node information; and the DHCPv6 service module is connected with the packet analysis module, and the DHCPv6 service module is configured to allocate the website management IPv6 address generated according to the IP and MAC corresponding relation table to the object website requesting to allocate the IPv6 address, wherein the DHCPv6 service module directly substitutes the numbers of the decimal array of the individual points in the configured IPv4 address of the object website into the numbers of the hexadecimal array of the colon number serving as the tail corresponding position in the website management IPv6 address respectively in a mode of not carrying out carry conversion, so as to generate the website management IPv6 address with the suffix of the macroscopic identification address.
In an embodiment of the present invention, an IPv6 node management device is provided, further including a node management module connected to the packet analysis module, where the node management module is configured to compare the preset allowed node list with the node information obtained by the packet analysis module, determine that the node of the configured IPv6 address to which the network environment belongs is a legal node or an illegal node, and block the node determined as the illegal node.
When the IPv6 address is distributed by the DHCPv6, the suffix of the IPv6 address obtained by the object network node is identical with the IPv4 address, namely, the network node with the macroscopic identification address suffix manages the IPv6 address, thereby improving the identification of the IPv6 address of the object network node and being beneficial to the management of the network node.
Drawings
Fig. 1 is a flow chart showing an IPv6 mesh point management method according to an embodiment of the present invention;
fig. 2 is a schematic diagram showing an IPv6 mesh point management device according to an embodiment of the present invention;
fig. 3 is a block diagram illustrating an IPv6 mesh point management device according to an embodiment of the present invention;
FIG. 4 is a diagram showing a packet analysis step of an IPv6 network point management method according to an embodiment of the present invention;
Fig. 5 is a schematic diagram showing an IPv6 address allocation step of an IPv6 mesh point management method according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating an IPv6 mesh point management method according to another embodiment of the present invention;
Fig. 7 is a schematic diagram showing an illegal mesh point blocking step of an IPv6 mesh point management method according to an embodiment of the present invention;
Fig. 8 is a flowchart illustrating an IPv6 mesh point management method according to another embodiment of the present invention;
Fig. 9 is a schematic diagram showing an acceleration detection step of an IPv6 mesh point management method according to an embodiment of the present invention.
Reference numerals:
100 IPv6 network point management equipment
1. Packet collection module
2. Packet analysis module
21 IP and MAC correspondence table
3 DHCPv6 service module
4. Network point management module
41. Allow site inventory
E network environment
N net point
S1 packet collection step
S2 packet analysis step
S21 IPv6 packet classifying sub-step
S22 ICMPv6 packet classification sub-step
S23 information extraction sub-step
S3 IPv6 address allocation step
S31 substep
S32 substep
S33 substep
S34 substep
S35 substep
S4 illegal network point blocking step
S41 substep
S42 substep
S43 substep
S44 substep
S5 acceleration detection step
S51 substep
S52 substep
Detailed Description
An embodiment of the present invention will be described below with reference to fig. 1 to 9. The description is not intended to limit the embodiments of the invention, but is one example of the invention.
As shown in fig. 1 to 5, the IPv6 mesh point management method according to an embodiment of the present invention is applied to a network environment E where an IPv6 address and an IPv4 address coexist, and manages a mesh point N to which the network environment E belongs. An IPv6 mesh point management apparatus 100 is provided in the network environment E, and the IPv6 mesh point management apparatus 100 includes: a packet collecting module 1, a packet analyzing module 2 connected to the packet collecting module 1, and a DHCPv6 service module 3 connected to the packet analyzing module 2. The IPv6 network point management method comprises the following steps: a packet collection step S1, a packet analysis step S2 and an IPv6 address allocation step S3.
As shown in fig. 1 to 3, in the packet collecting step S1, the packet collecting module 1 collects the node packets of each node N in the network environment E. Specifically, the network packets of the mesh point (i.e. mesh point packets) are collected from the network environment for subsequent parsing, which is a means commonly used in network management, so any manner of collecting mesh point packets known to those skilled in the art can be applied in the packet collecting step S1, which is not limited in this invention.
In the present invention, since the network environment E is a network environment where IPv6 addresses and IPv4 addresses coexist, the collected mesh point packets include IPv6 packets and IPv4 packets. In this case, in the present invention, the IPv6 packet and the IPv4 packet may be collected separately in a separate manner, or the IPv6 packet and the IPv4 packet may be collected together in a single manner, which is not limited in any way.
As shown in fig. 1 to 3, in the packet analysis step S2, the packet analysis module 2 analyzes each of the mesh point packets collected in the packet collection step S1, and obtains mesh point information about each mesh point N from the mesh point packets, wherein the mesh point information contains IP address information and MAC address information, and establishes an IP and MAC correspondence table 21 according to the mesh point information.
Specifically, in the packet analysis step S2, the IP address information of the mesh point information includes the IPv6 address information of the mesh point N, and the packet analysis module 2 obtains the mesh point information including the IPv6 address information and/or the MAC address information from a neighbor request (Neighbor Solicitation; NS) packet and/or a neighbor advertisement (Neighbor Advertisement; NA) packet belonging to a neighbor discovery protocol (Neighbor Discovery Protocol; NDP) in the mesh point packet, thereby establishing the IP and MAC correspondence table 21.
The neighbor discovery protocol is a part of the IPv6 network communication specification protocol, and is used for network communication OSI third layer information exchange. The neighbor discovery protocol defines five ICMPv6 packet types, including: routing request (Router Solicitation (Type 133)), routing advertisement (Router Advertisement (Type 134)), neighbor request (Neighbor Solicitation (Type 135)), neighbor advertisement (Neighbor Advertisement (Type 136)), and reset direction (Redirect (Type 137)). The neighbor solicitation can be used to determine the neighbor's MAC address or to determine if the neighbor's cache MAC address is still reachable, and in addition, to repeat IP address detection by the mesh point. The neighbor advertisement is then used for the acknowledgement sent by the neighbor solicitation or as a notification sent to the neighbor mesh point when the IP address/MAC address changes.
As shown in fig. 4, in the packet analysis step S2, the mesh point information including the IPv6 address information and/or the MAC address information is obtained from the mesh point packet, which includes the following steps: an IPv6 packet classification sub-step S21, an ICMPv6 packet classification sub-step S22, and an information extraction sub-step S23.
In the IPv6 packet classifying sub-step S21, for the mesh point packet collected in the packet collecting step S1, the mesh point packet whose content of an ethernet type (EtherType) field of the packet is judged to be "0x86DD" is classified as an IPv6 classified packet. The ethernet type is a two-byte field (two-byte field) in an ethernet frame (ETHERNET FRAME) that represents what protocol is encapsulated in the ethernet frame. The protocol represented by "0x86DD" in the ethernet type field is IPv6, and IPv4 is numbered with "0x0800", so that in the packet collecting step S1, the mesh point packet having the content of "0x86DD" in the ethernet type field can be separated from the mesh point packet belonging to IPv4 by classifying the mesh point packet as an IPv6 classification packet.
In ICMPv6 packet classification sub-step S22, the IPv6 classified packet whose content of the next header field of the packet is judged as "58" is classified as an ICMPv6 classified packet. Specifically, the Next Header (Next Header) field "58" of the IPv6 classified packet represents "ICMPv6", and thus, in ICMPv6 packet classification sub-step S22, such packet is further classified as the ICMPv6 classified packet.
In the information extraction sub-step S23, the mesh point information including the IPv6 address information and/or the MAC address information is extracted from the ICMPv6 classified packet whose content of the type field of the packet is determined as "135" or "136". Specifically, when the Type (Type) threshold is "135", it represents that the ICMPv6 classification packet belongs to a Neighbor Solicitation (NS) packet, and when the Type (Type) threshold is "136", it represents that the ICMPv6 classification packet belongs to a Neighbor Advertisement (NA) packet. As described above, from the two types of packets, the mesh point information including the IPv6 address information and/or the MAC address information can be obtained, thereby establishing the IP and MAC correspondence table 21.
As shown in fig. 1 to 3, in the IPv6 address allocation step S3, the DHCPv6 service module 3 allocates the dot management IPv6 address generated according to the IP and MAC correspondence table 21 to the target dot N requesting to allocate the IPv6 address, wherein the DHCPv6 service module 3 directly substitutes the numbers of the decimal arrays of the individual dots in the configured IPv4 address of the target dot N, respectively, without performing carry conversion, into the numbers of the hexadecimal arrays of the colon in the respective corresponding positions at the end of the dot management IPv6 address, thereby generating the dot management IPv6 address having the address suffix identified by naked eyes.
Specifically, DHCPv6 (dynamic host configuration protocol version six; dynamic Host Configuration Protocol version) is a network protocol for configuring IP addresses, IP prefixes, and/or other configurations required by an IPv6 host operating on an IPv6 network, and the DHCPv6 service module 3 allocates an IPv6 address to the target mesh point N based on the protocol.
IPv6 addresses are typically coded with a colon ": "eight groups of 4-digit hexadecimal digits separated by a colon" is represented, i.e., in the form of a colon-split hexadecimal (colon-hexadecimal notation), and therefore, in the present invention, the groups separated by a colon are referred to as a colon-split hexadecimal array. For example, in the example IPv6 addresses "2001:0db8:0000:0000:0000:ff00:0042:8329," 2001"," 0DB8"," 0000"," FF00"," 0042"," 8329 "are respectively colon-split hexadecimal arrays.
Compared with an IPv4 address (for example, 192.168.1.235) expressed in a dot decimal form, the IPv6 address is longer, and more complex hexadecimal numbers are also used, so that the corresponding relation between the dot and the IPv6 address can be difficult to memorize and identify for network management personnel, and the management can be inconvenient. Therefore, in the IPv6 address allocation step S3, the DHCPv6 service module 3 is configured to allocate the mesh point management IPv6 address having the macroscopic address suffix to the object mesh point N, so as to improve the visibility of the IPv6 address of the object mesh point N.
Specifically, as shown in fig. 5, in the present embodiment, the DHCPv6 service module 3 first receives a DHCPv6 allocation request of the object mesh point N (sub-step S31), that is, requests allocation of an IPv6 address. Next, the DHCPv6 service module 3 obtains the IP and MAC correspondence table 21 generated in the packet analysis step S2 (sub-step S32). Based on the IP-MAC correspondence table 21, it is possible to confirm whether or not the IPv4 address is already allocated to the target mesh point N (substep S33).
In the case where the object mesh point N has been configured with an IPv4 address, the mesh point management IPv6 address is generated with the configured IPv4 address of the object mesh point N (sub-step S34). For example, as shown in table 1 below, when the object mesh point N has been configured with an IPv4 address (e.g.: "192.168.1.235"), the DHCPv6 service module 3 directly substitutes the numbers of the decimal arrays (i.e., "192", "168", "1", "235") of the respective points in the configured IPv4 address of the object node N into the respective corresponding positions at the end of the predetermined IPv6 address to be allocated (e.g., "2001:0DB8:0000:0000:？？？？:？？？？:？？？？:？？？？. Also, since IPv6 addresses are shown with leading 0 omitted for convenience, the mesh point management IPv6 addresses are shown as "2001:0DB8:0000:0000:0192:0168:0001:0235" or further omitted with consecutive 0 s as "2001:DB8:192:168:1:235". In this way, the suffix of the mesh point management IPv6 address (i.e., "192:168:1:235") and the configured IPv4 address "192.168.1.235" of the target mesh point N have the same number, so that the network administrator does not need to remember the entire string of IPv6 addresses, and can easily recognize the correspondence between the mesh point management IPv6 address and the mesh point N by naked eyes.
[ Table 1]
| Configured IPv4 address for object mesh point | 192.168.1.235 |
| Preset IPv6 address to be allocated | 2001:0DB8:0000:0000:？？？？:？？？？:？？？？:？？？？ |
| Mesh point management IPv6 address | 2001:0DB8:0000:0000:0192:0168:0001:0235 |
| Mesh point management IPv6 address (omitting preamble 0) | 2001:DB8:0:0:192:168:1:235 |
| Mesh point management IPv6 address (omitting continuous 0) | 2001:DB8::192:168:1:235 |
In the above example, the DHCPv6 service module 3 directly substitutes the numbers of all four decimal arrays in the configured IPv4 address of the target mesh point N into the numbers of the colon-divided hexadecimal arrays as the last four corresponding positions in the mesh point management IPv6 address, respectively, in a manner of not performing carry conversion. However, the invention is not limited thereto. For example, an IPv4 address can generally be divided into two parts: a network identifier (network identifier; network ID) and a host identifier (host ID). In the same local area network, the host identifier will vary from one network point to another, but the network identifiers will typically be the same. In other words, the mesh point can be identified based solely on the host identifier. Thus, as shown in Table 2 below, in other embodiments, only the digits of the decimal array of points belonging to the host identifier in the configured IPv4 address of the object node N (e.g., "1" and "235") can be substituted directly without carry conversion into the digits of the hexadecimal array of colon numbers that are the last individual corresponding positions (i.e., last two corresponding positions) in the node management IPv6 address, respectively, to generate the node management IPv6 address with a macroscopic identifying address suffix (i.e., "2001:DB8:: FF00: 1:235").
[ Table 2]
| Configured IPv4 address for object mesh point | 192.168.1.235 |
| Preset IPv6 address to be allocated | 2001:0DB8:0000:0000:0000:FF00:？？？？:？？？？ |
| Mesh point management IPv6 address | 2001:0DB8:0000:0000:0000:FF00:0001:0235 |
| Mesh point management IPv6 address (omitting preamble 0) | 2001:DB8:0:0:0:FF00:1:235 |
| Mesh point management IPv6 address (omitting continuous 0) | 2001:DB8::FF00:1:235 |
On the other hand, as shown in fig. 5, in the case where the target mesh point N is not configured with an IPv4 address, the DHCPv6 service module 3 generates the mesh point management IPv6 address according to a preset allocation rule (sub-step S35). The preset allocation rule is not limited, and preferably, in order to improve the identification of the mesh point management IPv6 address of the mesh point N not configured with the IPv4 address, in this embodiment, the DHCPv6 service module 3 generates the mesh point management IPv6 address by using the emulated configuration IPv4 address as the configured IPv4 address of the target mesh point N, where the emulated configuration IPv4 address is selected from the IPv4 addresses outside the range of the allocation range of the IPv4 address of the network environment E, or the emulated configuration IPv4 address is selected from the irregular IPv4 address, and the irregular IPv4 address contains at least one hexadecimal number of "a" to "F", or at least one point of the irregular IPv4 address has a decimal number exceeding 8 bits.
In the present invention, since the network environment E is a network environment in which IPv6 addresses and IPv4 addresses coexist, in addition to assigning IPv6 addresses, IPv4 addresses are also assigned to the mesh point N in the network environment E, and these IPv4 addresses to be assigned are all selected from a set IPv4 address assignment range, and IPv4 addresses outside the IPv4 address assignment range are referred to as "out-of-range IPv4 addresses". The IPv4 address is selected from the IPv4 addresses outside the range through the simulation configuration, so that the allocation range of the IPv4 addresses belonging to the network environment E can be avoided, and the network point management IPv6 address occupying the network point N with the IPv4 address can be effectively avoided. In addition, in a regular IPv4 address, each point is decimal and has no more than 8 bits (i.e., 0 to 255), and an IPv4 address having hexadecimal numbers of "a" to "F" or having numbers more than 8 bits is called a "denormal IPv4 address". The simulation configuration IPv4 address is selected from the irregular IPv4 address, so that the possible configured IPv4 address of the mesh point N can be avoided, and the mesh point management IPv6 address of the mesh point N with the configured IPv4 address is effectively avoided.
Specifically, as shown in the following table 3, in the present embodiment, when the target node N is not configured with an IPv4 address, the DHCPv6 service module 3 may select the simulated configured IPv4 address (for example, "192.168.1. A") from among the out-of-range IPv4 addresses (for example, "192.168.1.1 to 192.168.1.255" when the IPv4 address allocation range is "192.168.2.1 to 192.168.2.255", "10.0.0.1 to 10.0.255") or the irregular IPv4 address (for example, "192.168.1 a to 192.168.1.F", "192.168.a.1 to 192.168.a.255", "192.168.1.256 to 192.1.ffff") as the configured IPv4 address of the target node N. Therefore, the generated mesh point management IPv6 address (namely, "2001:DB8:: 192:168:1:A") also has the macroscopic address suffix of "192:168:1:A", so that a network manager can conveniently memorize and identify the object mesh point N, and can further identify that the object mesh point N is not configured with an IPv4 address.
[ Table 3]
| Configured IPv4 address for object mesh point | Without any means for |
| Emulation configuration of IPv4 addresses | 192.168.1.A |
| Mesh point management IPv6 address | 2001:0DB8:0000:0000:0192:0168:0001:000A |
| Mesh point management IPv6 address (omitting preamble 0) | 2001:DB8:0:0:192:168:1:A |
| Mesh point management IPv6 address (omitting continuous 0) | 2001:DB8::192:168:1:A |
As shown in fig. 6 and 3, in another embodiment of the present invention, the IPv6 mesh point management method further includes an illegal mesh point blocking step S4, comparing the mesh point information obtained in the preset allowed mesh point list 41 and the packet analysis step S2, determining that the mesh point N of the configured IPv6 address to which the network environment E belongs is a legal mesh point or an illegal mesh point, and blocking the mesh point N determined as the illegal mesh point. The illegal node blocking step S4 and the IPv6 address allocation step S3 do not affect each other, so the illegal node blocking step S4 may be performed before, after, or simultaneously with the IPv6 address allocation step S3, which is not limited by the present invention.
As shown in fig. 7 and 3, in the present embodiment, the IPv6 mesh point management device 100 further includes a mesh point management module 4 for executing the illegal mesh point blocking step S4. Specifically, the mesh point management module 4 is configured to compare the preset allowed mesh point list 41 with the mesh point information obtained by the packet analysis module 2 (sub-step S41), thereby determining whether the mesh point N is a legal mesh point existing in the allowed mesh point list 41 (sub-step S42). When the mesh point N is a legal mesh point, the mesh point N is allowed to exist in the network environment E (sub-step S43). When the mesh point N is an illegal mesh point, the mesh point N is blocked (substep S44). For example, a neighbor advertisement packet of the fake gateway-related ICMPv6 is transmitted to an illegal mesh point. Of course, the present invention is not limited to this, and any conventional method of blocking dots can be applied to the illegal dot blocking step S4.
As shown in fig. 8 and 9 and fig. 3, in another embodiment of the present invention, the IPv6 mesh point management method further includes an acceleration detection step S5, performing an operation process on the IP address information of each mesh point N existing in the current IP and MAC correspondence table 21 and the IPv6 address allocation range to which the network environment E belongs, so as to obtain an undiscovered mesh point possible IPv6 address range related to the IP and MAC correspondence table (sub-step S51), and sending a detection packet for an IPv6 address within the undiscovered mesh point possible IPv6 address range, so as to drive the corresponding mesh point N in the network environment E to send the mesh point packet containing the mesh point information (sub-step S52). Specifically, since the node N in the network environment E may use the static IPv6 address or the node packet (e.g. neighbor solicitation packet, neighbor advertisement packet) that can obtain the IPv6 address information is not yet collected for the node N, the present IP and MAC correspondence table 21 does not find the node information of the node N. Through the acceleration detection step S5, the undiscovered mesh points N can be driven to send out mesh point packets containing mesh point information as soon as possible, so as to accelerate the update of the IP and MAC correspondence table 21, so that the IPv6 mesh point management device 100 can master and manage all mesh points N in the network environment E as soon as possible.
The IPv6 address allocation range refers to a set of IPv6 addresses provided by an internet service Provider (INTERNET SERVICE Provider; ISP) to be allocated to the mesh point N in the network environment E. Based on the IPv6 address allocation range and the IPv4 address information already existing in the IP-MAC correspondence table 21, the possible IPv6 addresses of each of the mesh points N in the network environment E are estimated by an arithmetic process, and a set of possible IPv6 addresses is obtained. By comparing the set of possible IPv6 addresses with the IPv6 address information already existing in the current IP-MAC correspondence table 21, it is possible to determine the unknown IPv6 addresses in the current IP-MAC correspondence table 21, and the unknown IPv6 address sets are the range of the possible IPv6 addresses of the undiscovered network point. Next, a detection packet, e.g., a DAD (Duplicate Address Detection; repeat address detection) detection packet, is sent for IPv6 addresses within the range of possible IPv6 addresses for the undiscovered mesh point to force the corresponding mesh point N to send out a mesh point packet (e.g., neighbor advertisement packet) containing mesh point information when detected. In this way, the IPv6 mesh point management device 100 can collect the mesh point packet, and accelerate the update of mesh point information about the mesh point N in the IP and MAC correspondence table 21. Compared with the method of detecting the entire IPv6 address allocation range of the network environment E, the acceleration detection step S5 limits the amount of detection to a smaller range (the range of IPv6 addresses where no network point is found), so that the detection speed is faster and more efficient.
When the IPv6 address is distributed by the DHCPv6, the suffix of the IPv6 address obtained by the object network node is identical with the IPv4 address, namely, the network node with the macroscopic identification address suffix manages the IPv6 address, thereby improving the identification of the IPv6 address of the object network node and being beneficial to the management of the network node.
The foregoing description and description are only illustrative of the preferred embodiments of the invention, and other modifications will occur to those skilled in the art upon the reading of the following claims and the description, but are intended to be within the spirit and scope of the invention.
In this specification, the invention has been described with reference to specific embodiments thereof. It will be apparent that various modifications and variations can be made without departing from the spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Claims (9)
1. An IPv6 network point management method is applied to a network environment where IPv6 addresses and IPv4 addresses coexist, and manages network points to which the network environment belongs, the IPv6 network point management method comprises the following steps:
a packet collection step, namely collecting the network point packets of all the network points in the network environment by using a packet collection module;
a packet analysis step of analyzing each of the node packets collected in the packet collection step by a packet analysis module, and obtaining node information about each of the nodes from the node packets, wherein the node information contains IP address information and MAC address information, and an IP and MAC corresponding relation table is established according to the node information; and
And an IPv6 address allocation step, namely, allocating the website management IPv6 address generated according to the IP and MAC corresponding relation table to an object website requesting to allocate the IPv6 address by using a DHCPv6 service module, wherein the DHCPv6 service module directly substitutes the numbers of the individual decimal arrays in the configured IPv4 address of the object website into the numbers of the hexadecimal arrays of the colon number at the end individual corresponding position in the website management IPv6 address in a mode of not carrying out carry conversion, so as to generate the website management IPv6 address with the suffix of the address identified by naked eyes.
2. The IPv6 mesh point management method according to claim 1, wherein in the packet analysis step, the IP address information of the mesh point information includes IPv6 address information of the mesh point, and the packet analysis module obtains the mesh point information including the IPv6 address information and/or the MAC address information from a neighbor solicitation packet and/or a neighbor advertisement packet belonging to a neighbor discovery protocol in the mesh point packet.
3. The IPv6 mesh point management method according to claim 2, wherein in the packet analysis step, the mesh point information including the IPv6 address information and/or the MAC address information is derived from the mesh point packet, comprising the steps of:
an IPv6 packet classifying sub-step, namely classifying the mesh point packet with the content of the Ethernet type field of the packet being judged to be 0x86DD as an IPv6 classified packet;
An ICMPv6 packet classifying sub-step of classifying the IPv6 classified packet, in which the content of the next header field of the packet is judged to be "58", as an ICMPv6 classified packet; and
And an information extraction sub-step, extracting the mesh point information comprising the IPv6 address information and/or the MAC address information from the ICMPv6 classification packet with the content of the type field of the packet judged as '135' or '136'.
4. The IPv6 mesh point management method according to claim 1, wherein in the IPv6 address allocation step, the DHCPv6 service module directly substitutes numbers of all four decimal arrays in the configured IPv4 address of the object mesh point into numbers of a colon hexadecimal array as last four corresponding positions in the mesh point management IPv6 address, respectively, in a manner of not performing carry conversion.
5. The IPv6 mesh point management method according to claim 1, wherein in the IPv6 address allocation step, when the target mesh point is not configured with an IPv4 address, the DHCPv6 service module generates the mesh point management IPv6 address by using a simulated configuration IPv4 address as the configured IPv4 address of the target mesh point, wherein the simulated configuration IPv4 address is selected from an IPv4 address outside a range of the IPv4 address allocation range of the network environment, or the simulated configuration IPv4 address is selected from a denominator IPv4 address, and the denominator IPv4 address contains at least one hexadecimal number from "a" to "F", or at least one point decimal number of the denominator IPv4 address has a number exceeding 8 bits.
6. The IPv6 mesh point management method according to claim 1, further comprising an illegal mesh point blocking step of comparing a preset allowed mesh point list with the mesh point information obtained in the packet analysis step to determine whether the mesh point of the configured IPv6 address to which the network environment belongs is a legal mesh point or an illegal mesh point, and blocking the mesh point determined as the illegal mesh point.
7. The method according to claim 1, further comprising an acceleration detection step of performing an operation process on the IP address information of each of the nodes existing in the current IP and MAC correspondence table and the IPv6 address allocation range to which the network environment belongs, thereby obtaining an undiscovered node possible IPv6 address range related to the IP and MAC correspondence table, and sending a detection packet for an IPv6 address within the undiscovered node possible IPv6 address range, so as to drive the corresponding node in the network environment to send the node packet containing the node information.
8. An IPv6 mesh point management device for executing the IPv6 mesh point management method according to any one of claims 1 to 7, the IPv6 mesh point management device being disposed in the network environment where an IPv6 address and an IPv4 address coexist, and managing a mesh point to which the network environment belongs, the IPv6 mesh point management device comprising:
the packet collecting module is configured to collect the network point packets of each network point in the network environment;
The packet analysis module is connected with the packet collection module, and is configured to analyze each of the node packets collected by the packet collection module, obtain node information about each node from the node packets, wherein the node information contains the IP address information and the MAC address information, and establish the IP and MAC corresponding relation table according to the node information; and
The DHCPv6 service module is connected to the packet analysis module, and the DHCPv6 service module is configured to allocate the website management IPv6 address generated according to the IP and MAC correspondence table to the target website requesting to allocate the IPv6 address, where the DHCPv6 service module directly substitutes the numbers of the individual decimal arrays of the points in the configured IPv4 address of the target website into the numbers of the hexadecimal arrays of the colon marks corresponding to the end positions in the website management IPv6 address, respectively, without performing carry conversion, so as to generate the website management IPv6 address with the macroscopic identification address suffix.
9. The IPv6 mesh point management device of claim 8, further comprising a mesh point management module, coupled to the packet analysis module, wherein the mesh point management module is configured to compare the preset allowed mesh point list with the mesh point information obtained by the packet analysis module, determine whether the mesh point of the configured IPv6 address to which the network environment belongs is a legal mesh point or an illegal mesh point, and block the mesh point determined as the illegal mesh point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010474400.1A CN113746944B (en) | 2020-05-29 | 2020-05-29 | IPv6 network point management method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010474400.1A CN113746944B (en) | 2020-05-29 | 2020-05-29 | IPv6 network point management method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113746944A CN113746944A (en) | 2021-12-03 |
| CN113746944B true CN113746944B (en) | 2024-05-14 |
Family
ID=78724598
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010474400.1A Active CN113746944B (en) | 2020-05-29 | 2020-05-29 | IPv6 network point management method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113746944B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101199166A (en) * | 2005-04-29 | 2008-06-11 | 艾利森电话股份有限公司 | Operator shop selection in broadband access |
| CN101848247A (en) * | 2009-03-26 | 2010-09-29 | 华为技术有限公司 | Method for implementing access of IPv6 host to IPv4 host, method for acquiring IPv6 address prefix and conversion device |
| CN102447617A (en) * | 2010-10-09 | 2012-05-09 | 华为技术有限公司 | Method, terminals and gateway for transmitting IPv6 (Internet Protocol version 6) message in IPv4 network |
| CN103051744A (en) * | 2013-01-08 | 2013-04-17 | 中兴通讯股份有限公司 | Method and device for converting multicast address |
| JP2014007510A (en) * | 2012-06-22 | 2014-01-16 | Nippon Telegr & Teleph Corp <Ntt> | IPv4-IPv6 CONVERSION PROCESSING METHOD, IPv4-IPv6 CONVERSION PROCESSING APPARATUS AND IPv4-IPv6 INTEGRATION NETWORK SYSTEM |
| WO2014089677A1 (en) * | 2012-12-10 | 2014-06-19 | Bluecat Networks Inc | System and method for ip network semantic label storage and management |
| CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
| CN104883407A (en) * | 2014-02-28 | 2015-09-02 | 中兴通讯股份有限公司 | IPv6 address handling method and apparatus and DHCPv6 relay |
-
2020
- 2020-05-29 CN CN202010474400.1A patent/CN113746944B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101199166A (en) * | 2005-04-29 | 2008-06-11 | 艾利森电话股份有限公司 | Operator shop selection in broadband access |
| CN101848247A (en) * | 2009-03-26 | 2010-09-29 | 华为技术有限公司 | Method for implementing access of IPv6 host to IPv4 host, method for acquiring IPv6 address prefix and conversion device |
| CN102447617A (en) * | 2010-10-09 | 2012-05-09 | 华为技术有限公司 | Method, terminals and gateway for transmitting IPv6 (Internet Protocol version 6) message in IPv4 network |
| JP2014007510A (en) * | 2012-06-22 | 2014-01-16 | Nippon Telegr & Teleph Corp <Ntt> | IPv4-IPv6 CONVERSION PROCESSING METHOD, IPv4-IPv6 CONVERSION PROCESSING APPARATUS AND IPv4-IPv6 INTEGRATION NETWORK SYSTEM |
| WO2014089677A1 (en) * | 2012-12-10 | 2014-06-19 | Bluecat Networks Inc | System and method for ip network semantic label storage and management |
| CN103051744A (en) * | 2013-01-08 | 2013-04-17 | 中兴通讯股份有限公司 | Method and device for converting multicast address |
| CN104883407A (en) * | 2014-02-28 | 2015-09-02 | 中兴通讯股份有限公司 | IPv6 address handling method and apparatus and DHCPv6 relay |
| CN104734963A (en) * | 2015-03-24 | 2015-06-24 | 电子科技大学 | IPv4 and IPv6 network interconnection method based on SDN |
Non-Patent Citations (1)
| Title |
|---|
| IVI/MAP-T/MAP-E:Unified IPv4/IPv6 Stateless Translation and Encapsulation Technologies;Congxiao Bao;Xing Li;;ZTE Communications;20130925(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113746944A (en) | 2021-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11418444B2 (en) | IPv6 network node managing method and equipment | |
| US6618755B1 (en) | Automatically identifying subnetworks in a network | |
| US20050027778A1 (en) | Automatic configuration of an address allocation mechanism in a computer network | |
| US7280752B2 (en) | Network address routing using multiple routing identifiers | |
| EP1357725A2 (en) | An internet protocol based communication system and method for setting host address and selecting source address therein | |
| EP2191634B1 (en) | A system and method for generating functional addresses | |
| US7035941B2 (en) | Method of and device for deciding network address, and computer product | |
| US7293106B2 (en) | Method of finding a path between two nodes in a network | |
| US7948916B2 (en) | Method and apparatus for discovering topology information in a network | |
| CN113746944B (en) | IPv6 network point management method and equipment | |
| US20150372968A1 (en) | A Method of and a Processing Device Handling a Protocol Address in a Network | |
| KR101052913B1 (en) | Network system and method for allocating IPv6 address | |
| JPH08223206A (en) | Automatic address assignment system | |
| KR100846014B1 (en) | METHOD OF CONFIGURING IPv6 LINK-LOCAL ADDRESSES USING PSEUDO EUI-64 IDENTIFIERS IRRESPECTIVE OF TYPE OF PHYSICAL MEDIA | |
| CN112165539B (en) | IPv6 address translation method | |
| CN113301001B (en) | Attacker determination method, attacker determination device, computing equipment and attacker determination medium | |
| CN112995353B (en) | IPv6 address survivability scanning system and method based on flow analysis | |
| CN107241457A (en) | A kind of method for realizing network end-to-end communication | |
| KR100426055B1 (en) | SECURE AUTOMATIC CONFIGURATION METHOD OF MULTICAST ADDRESSES IN IPv6-BASED NODES IN NETWORK LAYER | |
| US8422492B2 (en) | Method for generating and identifying identifier and communication system | |
| CN111212442B (en) | System and method for distinguishing AP (Access Point) and wireless client traffic by dpi (Point-to-Point) engine | |
| KR100473118B1 (en) | An internet protocol packet address lookup method and apparatus for a backbone router | |
| Carpene et al. | A survey of IPv6 address usage in the public domain name system | |
| JP2003143226A (en) | Probe apparatus for ip network and traffic statistic method | |
| CN113709268A (en) | Network random on-demand addressing method and its interconnected network |
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 |