CN116074285A - Address conflict detection method and device - Google Patents
Address conflict detection method and device Download PDFInfo
- Publication number
- CN116074285A CN116074285A CN202211726458.6A CN202211726458A CN116074285A CN 116074285 A CN116074285 A CN 116074285A CN 202211726458 A CN202211726458 A CN 202211726458A CN 116074285 A CN116074285 A CN 116074285A
- Authority
- CN
- China
- Prior art keywords
- address
- determining
- conflict
- configuration information
- routing table
- 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.)
- Pending
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 65
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000015654 memory Effects 0.000 claims description 34
- 238000004590 computer program Methods 0.000 claims description 6
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 239000007787 solid Substances 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Abstract
The invention discloses an address conflict detection method and device, relates to the technical field of computers, and solves the problem that whether IP addresses conflict can not be judged in real time at present. The method comprises the following steps: the method comprises the steps of obtaining an address to be used and routing table configuration information of a hierarchy where the address is located, wherein the routing table configuration information comprises: and determining a cross comparison result by utilizing the address to be used and the destination address, and determining the target equipment corresponding to the destination address if the cross comparison result is conflict.
Description
Technical Field
The present invention relates to the field of cloud computing technologies, and in particular, to a method and an apparatus for detecting address collision.
Background
With the introduction of new technologies such as a service architecture, a software defined network, network function virtualization and the like, the network element equipment is turned to a standardized server from the traditional network equipment, and the characteristics such as IT (information technology) and Internet are presented. Meanwhile, network faults caused by IP address configuration conflict frequently occur due to the wide application of IPV6 technology.
In the related art, the process of judging the IP conflict between network devices is to construct a knowledge graph of the IP address by using the configuration information of the network devices. For example, the IP address knowledge graph is constructed by taking configuration information of network devices as entities of the knowledge graph and network connection relations between the network devices as relations between the entities. However, since the network configuration information is not real-time information of the present network, whether the IP address conflicts can not be judged in real time. Meanwhile, in the related technology, whether the IP addresses conflict or not can only be judged, and specific network equipment with the IP conflict cannot be accurately positioned.
Disclosure of Invention
The invention provides an address conflict detection method and device, which are used for solving the problem that whether IP addresses conflict or not cannot be judged in real time at present.
In order to achieve the above purpose, the invention adopts the following technical scheme:
in a first aspect, the present invention provides an address collision detection method, including: acquiring an address to be used and routing table configuration information of a hierarchy where the address is located; the routing table configuration information includes: a destination address. And determining a cross comparison result by using the address to be used and the destination address. And if the cross comparison result is conflict, determining the target equipment corresponding to the target address.
According to the address conflict detection method, the address to be used and the configuration information of the routing table of the level where the address is located are obtained, and then the cross comparison result is determined by utilizing the address to be used and the destination address in the configuration information of the routing table, if the cross comparison result is conflict, the target equipment corresponding to the destination address is determined, so that the problem that whether the IP address to be used conflicts with the used IP address or not is judged in real time is solved, and meanwhile, after the conflict between the IP address to be used and the used IP address is judged, the specific network equipment with the conflict can be accurately located, and the subsequent conflict determination reason and countermeasure solving are facilitated.
A possible implementation manner, determining a cross comparison result by using an address to be used and a destination address, including: comparing the address to be used with all destination addresses of configuration information of the routing table, and if the address to be used exists in the destination addresses, determining that the cross comparison result is conflict; if the target address does not have the address to be used, determining that the cross comparison result is not conflicted.
In one possible implementation, the routing table configuration information further includes: out of the interface and the next hop address. Determining a target device corresponding to the destination address, including: and determining a next-hop address by utilizing the destination address, logging in the next-hop address, and if the logging result is failure, acquiring an output interface of the routing table configuration information corresponding to the next-hop address, and determining that equipment corresponding to the interface is target equipment.
In one possible implementation manner, after determining that the device corresponding to the interface is the target device, the address conflict detection method provided by the application further includes: and displaying the target device.
In one possible implementation manner, the address conflict detection method provided by the application further includes: if the login result is successful, the next hop address is logged in.
In a second aspect, the present invention provides an address collision detection apparatus, including: the device comprises an acquisition module, a processing module and a determination module.
The device comprises an acquisition module, a routing table configuration module and a routing table configuration module, wherein the acquisition module is used for acquiring an address to be used and routing table configuration information of a hierarchy where the address is located, and the routing table configuration information comprises: a destination address.
And the processing module is used for determining a cross comparison result by utilizing the address to be used and the destination address.
And the determining module is used for determining the target equipment corresponding to the target address if the cross comparison result is a conflict.
According to the address conflict detection device, the address to be used and the configuration information of the routing table of the level where the address is located are obtained, and then the cross comparison result is determined by utilizing the address to be used and the destination address in the configuration information of the routing table, if the cross comparison result is conflict, the target equipment corresponding to the destination address is determined, so that the problem that whether the IP address to be used conflicts with the used IP address or not is judged in real time is solved, and meanwhile, after the conflict between the IP address to be used and the used IP address is judged, the specific network equipment with the conflict can be accurately positioned, and the subsequent conflict determination reason and countermeasure solving are facilitated.
In one possible implementation manner, the processing module is specifically configured to: comparing the address to be used with all destination addresses of the routing table configuration information, and if the address to be used exists in the destination addresses, determining that the cross comparison result is conflict; if the target address does not have the address to be used, determining that the cross comparison result is not conflicted.
In one possible implementation, the routing table configuration information further includes: out of the interface and the next hop address. The determining module is specifically configured to: the address conflict detection device provided by the application further comprises: the login module is used for logging the next hop address, and the acquisition module is also used for: if the login result is failure, the output interface of the routing table configuration information corresponding to the next hop address is obtained, and the determining module is further configured to: and determining the equipment corresponding to the interface as target equipment.
In one possible implementation manner, the address conflict detection apparatus provided in the present application further includes: and the display module is used for displaying the target equipment after the determining module determines that the equipment corresponding to the interface is the target equipment.
In one possible implementation, the login module is further configured to: if the login result is successful, the next hop address is logged in.
In a third aspect, a computing device is provided, which has a function of implementing the address conflict detection method described in the first aspect or any one of possible implementation manners. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.
In a fourth aspect, a computer readable storage medium is provided, in which instructions are stored which, when run on a computer, enable the computer to perform the address collision detection method according to the first aspect or any one of the possible implementations described above.
In a fifth aspect, a computer program product is provided comprising instructions which, when run on a computer, cause the computer to perform the address conflict detection method of the first aspect or any of the possible implementations described above.
The technical effects of any one of the design manners of the third aspect to the fifth aspect may be referred to technical effects of different possible implementation manners of the first aspect, which are not described herein.
For a detailed description of the second to fifth aspects and various implementations thereof in this application, reference may be made to the detailed description of the first aspect and various implementations thereof; moreover, the advantages of the second aspect and the various implementations thereof may be referred to as analyzing the advantages of the first aspect and the various implementations thereof, and will not be described herein.
These and other aspects of the present application will be more readily apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of an address conflict detection system according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a core network device according to an embodiment of the present application;
fig. 3 is a schematic flow chart of an address conflict detection method according to an embodiment of the present application;
fig. 4 is another flow chart of an address conflict detection method according to an embodiment of the present application;
fig. 5 is a schematic diagram of an address conflict detection method according to an embodiment of the present application;
fig. 6 is another schematic diagram of an address conflict detection method according to an embodiment of the present application;
fig. 7 is another flow chart of an address conflict detection method according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an address collision detection device according to an embodiment of the present application;
fig. 9 is another schematic structural diagram of an address collision detecting device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an address collision detection device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present invention, unless otherwise indicated, the meaning of "a plurality" is two or more.
In addition, the network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and as a person of ordinary skill in the art can know, with evolution of the network architecture and appearance of a new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.
Currently, the process of judging the IP conflict between network devices is to construct a knowledge graph of the IP address by using the configuration information of the network devices. However, since the network configuration information is not real-time information of the present network, whether the IP address conflicts can not be judged in real time. Meanwhile, the process can only judge whether the IP addresses conflict or not, and specific network equipment with the IP conflict cannot be accurately positioned. The application provides an address conflict detection method, which is used for acquiring an address to be used and routing table configuration information of a hierarchy where the address is located, determining a cross comparison result by utilizing the address to be used and a destination address of the routing table configuration information, and determining target equipment corresponding to the destination address if the cross comparison result is a conflict so as to judge whether the IP address is in conflict in real time and accurately locate specific network equipment with the IP conflict.
The implementation of the examples of the present application will be described in detail below with reference to the accompanying drawings.
The scheme provided by the application can be applied to the address conflict detection system 100 illustrated in fig. 1. As shown in fig. 1, the address conflict detection system 100 includes: a plurality of core network devices 101.
The core network device 101 may be a computer, a router, a switch, etc., and the type and the function of the core network device 101 are not limited in the embodiments of the present application.
It should be noted that, the number of core network devices 101 included in the address conflict detection system 100 may be configured according to actual requirements, and fig. 1 is only schematic in this application, and is not a specific limitation on the scale of the address conflict detection system 100.
The solution provided in the present application may be applied to the core network device 101 illustrated in fig. 2, where the core network device 101 may be disposed in the address conflict detection system 100 shown in fig. 1, and the core network device 101 may be a computer or other product forms, which is not specifically limited. The core network device 101 includes: processor 201, memory 202.
The processor 201 may be a central processing unit (central processing unit, CPU), and the processor 201 may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field-programmable gate arrays (field-programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination thereof.
The memory 202 may be a volatile memory (RAM), such as a random-access memory (RAM); or a nonvolatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a hard disk (HDD) or a Solid State Drive (SSD); or a combination of the above types of memories for storing application programs, configuration files, data information or other content that may implement the methods of the present application.
The processor 201 performs the following functions by running or executing software programs and/or modules stored in the memory 202 and invoking data stored in the memory 202:
and acquiring the address to be used and the configuration information of the routing table of the hierarchy where the address is located, determining a cross comparison result by utilizing the address to be used and the destination address, and determining the target equipment corresponding to the destination address if the cross comparison result is a conflict.
In one aspect, the present application discloses an address collision detection method, which may be performed by an address collision detection device, such as the core network device 101 illustrated in fig. 2. As shown in fig. 3, the method may include the steps of:
s301, obtaining an address to be used and routing table configuration information of a hierarchy where the address is located.
Specifically, the core network device acquires an IP address to be used input by a user, and simultaneously acquires routing table configuration information of the core network device at a level where the IP address is located.
For example, a user may log in to the core network device by inputting a password of an account number of the core network device, and further input an IP address to be used and a VPN of the address in the core network device, and after the core network device obtains the IP address to be used and the VPN of the address, obtain routing table configuration information of the core network device.
S302, determining a cross comparison result by utilizing the address to be used and the destination address.
The cross comparison is used for indicating that the address to be used is compared with the destination address in the routing table configuration information.
Specifically, the process of determining the cross-comparison result by using the address to be used and the destination address is as follows: comparing the address to be used with all destination addresses of configuration information of the routing table, and if the address to be used exists in the destination addresses, determining that the cross comparison result is conflict; if the destination address does not have the address to be used, determining that the crossing result is not conflict.
For example, the core network device matches all destination addresses of the core network device under the VPN by traversing within the core network device in a regular matching manner, while rejecting the default address 0.0.0.0/0. Further, the core network device performs cross comparison by using the address to be used and all the matched destination addresses, if the address to be used exists in the destination addresses, it can be determined that the address to be used is already used by a certain core network device under the core network device, and the cross comparison result is determined to be a conflict; if the address to be used does not exist in the destination address, it can be determined that the address to be used is not used as an idle state, and the cross comparison result is determined to be non-conflict.
If the address to be used is an address field, the core network device uses all the addresses to be used in the address field and all the matched destination addresses to carry out cross comparison.
S303, if the cross comparison result is conflict, determining the target equipment corresponding to the target address.
Specifically, after the cross comparison result is determined to be a conflict, the core network device can determine a next-hop address corresponding to the destination address in the routing table configuration information by using the destination address, log in the next-hop address, and if the login result is failure, acquire an outgoing interface of the routing table configuration information corresponding to the next-hop address, and determine that a device corresponding to the outgoing interface is a target device; if the login result is successful, the next hop address is logged in, and a next hop address corresponding to the destination address in the next hop device is determined continuously according to the routing table configuration information of the next hop device, and the next hop address is logged in until the login result is failure, an outgoing interface of the routing table configuration information corresponding to the next hop address is obtained, and the device corresponding to the outgoing interface is determined to be the target device.
For example, if the cross comparison result is a conflict, firstly, inquiring the next hop route corresponding to the address to be used in the conflict in the configuration information of the routing table, obtaining the outgoing interface of the next hop route, and logging in the outgoing interface address, namely logging in the core network device of the next hop route. If the login is successful, continuing to inquire downwards; if the login fails, the next hop opinion reaches the terminal equipment, and the specific terminal core network equipment using the IP address conflicting with the address to be used is determined according to the description of the outbound interface.
According to the method and the device, the address to be used and the configuration information of the routing table of the hierarchy where the address is located are obtained, then the cross comparison result is determined by utilizing the address to be used and the destination address in the configuration information of the routing table, if the cross comparison result is conflict, the target device corresponding to the destination address is determined, so that the problem that whether the IP address to be used conflicts with the used IP address or not is judged in real time is solved, and meanwhile, after the conflict between the IP address to be used and the used IP address is judged, the specific network device with the conflict can be accurately located, and the subsequent determination of the conflict reason and the solution are facilitated.
The following describes the embodiments of the present application in detail by way of specific examples.
For example, as shown in fig. 4, a user may log in to the address conflict detection system through a platform URL portal of the address conflict detection system by using an account number and a password allocated by the address conflict detection system, and after the login is successful, the user inputs parameters to be queried, where the parameters include, but are not limited to, an IP address to be used, an account number password of a device to be logged in, and a VPN of the device to be logged in that needs to be verified.
As shown in fig. 5, a user may add a core network device in the existing network in the address conflict detection system, specifically may add information such as a device name, a device IP address, a manufacturer, a region, a machine room of the core network device, and the like, and may modify the device information of the core network device according to the requirement. Meanwhile, when the user adds the information of the core network equipment in the address conflict detection system, the address conflict detection system can check the IP address of the equipment, and if the IP address which is the same as the IP address of the equipment is stored in the system, repeated addition is displayed, and the addition fails.
After the user inputs the parameter to be queried, as shown in fig. 6, the address conflict detection system traverses all the entered core network devices, and uses a regular matching mode to reject the route information in all the route configuration tables of the core network devices under the appointed VPN, and eliminates the default route 0.0.0/0 in the route configuration tables, so as to perform cross comparison between the IP address to be used and the destination address in all the obtained route configuration tables, and if the cross comparison result of the IP address to be used and the destination address is non-conflict, the interface of the address conflict detection system is displayed to be idle; if the cross comparison result of the to-be-used IP address and the destination addresses in all the obtained route configuration tables is a conflict, the terminal home core network equipment of the conflict IP address is continuously searched in a recursion mode.
Further, as shown in fig. 7, the procedure of recursively querying the end home core network device of the conflicting IP address is: firstly, the address conflict detection system firstly inquires the next hop route corresponding to the conflict IP address in the route configuration table and the exit interface corresponding to the next hop route, and then logs in the exit interface address, namely the core network equipment logging the next hop route. If the login succeeds in the outbound interface address, the next hop route which has succeeded in the login is continuously queried. If the login of the out interface address fails, the end log core network device which has reached the conflict IP address at the moment is indicated, and the specific end core network device which uses the conflict IP address is determined according to the out interface description.
The above description has been presented mainly in terms of the working principle of the device, with respect to the solution provided in the embodiments of the present application. It is to be appreciated that the computing device, in order to implement the functionality described above, includes corresponding hardware structures and/or software modules that perform the various functions. Those of skill in the art will readily appreciate that the algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The embodiment of the application may divide the functional modules of the computing device according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
In the case of dividing the respective functional modules with the respective functions, fig. 8 shows a schematic diagram of one possible composition of the address conflict detection apparatus referred to in the above-described and embodiments, as shown in fig. 8, the address conflict detection apparatus 800 may include: an acquisition module 801, a processing module 802, and a determination module 803.
Wherein, the obtaining module 801 is configured to support the address conflict detection apparatus 800 to execute S301 in the address conflict detection method shown in fig. 3.
A processing module 802, configured to support the address conflict detection apparatus 800 to execute S302 in the address conflict detection method shown in fig. 3.
A determining module 803 for supporting the address conflict detection apparatus 800 to execute S303 in the address conflict detection method shown in fig. 3.
In an embodiment of the present application, further, as shown in fig. 9, the address conflict detection apparatus 800 may further include: a login module 804 and a display module 805.
A login module 804, configured to support the address conflict detection apparatus 800 to perform a step of logging a next hop address.
A display module 805 for supporting the address conflict detection apparatus 800 to execute the step of displaying the target device.
It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.
The address conflict detection apparatus 800 provided in the embodiment of the present application is configured to perform the above address conflict detection method, so that the same effect as the above address conflict detection method can be achieved.
The embodiment of the present application further provides an address conflict detection apparatus 1000, as shown in fig. 10, where the address conflict detection apparatus 1000 may include a memory 1001, a processor 1002, and a transceiver 1003, where the memory 1001 and the processor 1002 may be connected by a bus or a network or other manners, and in fig. 10, the connection is exemplified by a bus.
The processor 1002 may be a central processing unit (central processing unit, CPU). The processor 1002 may also be a chip such as another general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or a combination thereof.
The memory 1001 may be a volatile memory (RAM) such as a random-access memory (RAM); or a nonvolatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a hard disk (HDD) or a Solid State Drive (SSD); or a combination of the above types of memories for storing application code, configuration files, data information, or other content in which the methods of the present application may be implemented.
The memory 1001 is used as a non-transitory computer readable storage medium for storing non-transitory software programs, non-transitory computer executable programs, and modules, such as metadata collection modules and the like in the embodiments of the present application. The processor 1002 executes various functional applications of the processor and data processing by running non-transitory software programs, instructions, and modules stored in the memory 1001.
The memory 1001 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created by the processor 1002, etc. In addition, memory 1001 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 1001 optionally includes memory remotely located with respect to processor 1002, which may be connected to processor 1002 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transceiver 1003 is used for information interaction of the address collision detecting device 1000 with other devices.
The one or more modules are stored in the memory 1001 and when executed by the processor 1002 perform the address conflict detection method in the embodiment shown in fig. 3.
Embodiments of the present application also provide a computer readable storage medium having stored thereon instructions that, when executed, perform the address conflict detection method and related steps of the method embodiments described above.
The present application also provides a computer program product, which when run on a computer, causes the computer to perform the relevant steps of the address conflict detection method in the above-mentioned method embodiments.
It will be apparent to those skilled in the art from this description that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or contributing part or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, where the software product includes several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (13)
1. An address collision detection method, comprising:
acquiring an address to be used and routing table configuration information of a hierarchy where the address is located; the routing table configuration information includes: a destination address;
determining a cross comparison result by utilizing the address to be used and the destination address;
and if the cross comparison result is conflict, determining the target equipment corresponding to the target address.
2. The method of claim 1, wherein determining the cross-over result using the address to be used and the destination address comprises:
comparing the address to be used with all destination addresses of the routing table configuration information;
if the address to be used exists in the destination address, determining that the cross comparison result is conflict;
and if the address to be used does not exist in the destination address, determining that the cross comparison result is not in conflict.
3. The method of claim 1, wherein the routing table configuration information further comprises: an outgoing interface and a next hop address;
the determining the target device corresponding to the destination address includes:
determining the next hop address by utilizing the destination address;
logging in the next hop address;
if the login result is failure, acquiring an output interface of the routing table configuration information corresponding to the next hop address;
and determining the equipment corresponding to the output interface as the target equipment.
4. A method according to claim 3, wherein after determining that the device to which the outgoing interface corresponds is the target device, the method further comprises:
and displaying the target equipment.
5. A method according to claim 3, characterized in that the method further comprises:
and if the login result is successful, logging in the next hop address.
6. An address collision detection apparatus, comprising:
the acquisition module is used for acquiring the address to be used and the routing table configuration information of the hierarchy where the address is located; the routing table configuration information includes: a destination address;
the processing module is used for determining a cross comparison result by utilizing the address to be used and the destination address;
and the determining module is used for determining the target equipment corresponding to the target address if the cross comparison result is a conflict.
7. The apparatus of claim 6, wherein the device comprises a plurality of sensors,
the processing module is specifically configured to: comparing the address to be used with all destination addresses of the routing table configuration information; if the address to be used exists in the destination address, determining that the cross comparison result is conflict; and if the address to be used does not exist in the destination address, determining that the cross comparison result is not in conflict.
8. The apparatus of claim 6, wherein the routing table configuration information further comprises: an outgoing interface and a next hop address;
the determining module is specifically configured to: determining the next hop address by utilizing the destination address;
the apparatus further comprises: the login module is used for logging in the next hop address;
the acquisition module is further configured to: if the login result is failure, acquiring an output interface of the routing table configuration information corresponding to the next hop address;
the determining module is further configured to: and determining the equipment corresponding to the output interface as the target equipment.
9. The apparatus of claim 8, wherein the apparatus further comprises:
and the display module is used for displaying the target equipment after the determining module determines that the equipment corresponding to the output interface is the target equipment.
10. The apparatus of claim 8, wherein the device comprises a plurality of sensors,
the login module is further configured to: and if the login result is successful, logging in the next hop address.
11. An address collision detection apparatus, characterized by comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the address collision detection method of any of claims 1-5.
12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the address conflict detection method according to any of claims 1-5.
13. A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the address conflict detection method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211726458.6A CN116074285A (en) | 2022-12-30 | 2022-12-30 | Address conflict detection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211726458.6A CN116074285A (en) | 2022-12-30 | 2022-12-30 | Address conflict detection method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116074285A true CN116074285A (en) | 2023-05-05 |
Family
ID=86177998
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211726458.6A Pending CN116074285A (en) | 2022-12-30 | 2022-12-30 | Address conflict detection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116074285A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7200649B1 (en) * | 2001-09-27 | 2007-04-03 | Rockwell Automation Technologies, Inc. | Adaptive method for duplicative IP address detection |
| CN101977137A (en) * | 2010-11-03 | 2011-02-16 | 神州数码网络(北京)有限公司 | Address conflict detection and self-adaption method in VPN (Virtual Private Network) |
| CN104837138A (en) * | 2015-03-27 | 2015-08-12 | 广东欧珀移动通信有限公司 | Detection method of terminal hardware identifier, and detection device of terminal hardware identifier |
| CN105376343A (en) * | 2015-11-26 | 2016-03-02 | 上海贝锐信息科技有限公司 | Router address distribution method, router address distribution device and server in VPN |
| CN112637377A (en) * | 2020-12-17 | 2021-04-09 | 上海云轴信息科技有限公司 | Method and equipment for detecting IP address conflict |
| CN112995350A (en) * | 2019-12-13 | 2021-06-18 | 中盈优创资讯科技有限公司 | Network equipment address pool conflict detection method and device |
| CN114500467A (en) * | 2021-12-23 | 2022-05-13 | 云洲(盐城)创新科技有限公司 | Address conflict detection method, address conflict detection device and electronic equipment |
| CN114513492A (en) * | 2022-04-18 | 2022-05-17 | 浙江国利网安科技有限公司 | Method and device for configuring IP address |
| CN115174528A (en) * | 2022-09-07 | 2022-10-11 | 广州市保伦电子有限公司 | Equipment address control method, device and system |
-
2022
- 2022-12-30 CN CN202211726458.6A patent/CN116074285A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7200649B1 (en) * | 2001-09-27 | 2007-04-03 | Rockwell Automation Technologies, Inc. | Adaptive method for duplicative IP address detection |
| CN101977137A (en) * | 2010-11-03 | 2011-02-16 | 神州数码网络(北京)有限公司 | Address conflict detection and self-adaption method in VPN (Virtual Private Network) |
| CN104837138A (en) * | 2015-03-27 | 2015-08-12 | 广东欧珀移动通信有限公司 | Detection method of terminal hardware identifier, and detection device of terminal hardware identifier |
| CN105376343A (en) * | 2015-11-26 | 2016-03-02 | 上海贝锐信息科技有限公司 | Router address distribution method, router address distribution device and server in VPN |
| CN112995350A (en) * | 2019-12-13 | 2021-06-18 | 中盈优创资讯科技有限公司 | Network equipment address pool conflict detection method and device |
| CN112637377A (en) * | 2020-12-17 | 2021-04-09 | 上海云轴信息科技有限公司 | Method and equipment for detecting IP address conflict |
| CN114500467A (en) * | 2021-12-23 | 2022-05-13 | 云洲(盐城)创新科技有限公司 | Address conflict detection method, address conflict detection device and electronic equipment |
| CN114513492A (en) * | 2022-04-18 | 2022-05-17 | 浙江国利网安科技有限公司 | Method and device for configuring IP address |
| CN115174528A (en) * | 2022-09-07 | 2022-10-11 | 广州市保伦电子有限公司 | Equipment address control method, device and system |
Non-Patent Citations (2)
| Title |
|---|
| 王存祥, 樊婷婷: "校园网IP地址冲突的分析及解决方案", 中国电化教育, no. 07, 10 July 2004 (2004-07-10) * |
| 王宏林;: "解决IP地址冲突的路由器控制方案", 计算机安全, no. 12, 5 December 2007 (2007-12-05) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11159488B2 (en) | Dynamic application firewalling in cloud systems | |
| CN109067930B (en) | Domain name access method, domain name resolution method, server, terminal and storage medium | |
| CN109474640B (en) | Malicious crawler detection method and device, electronic equipment and storage medium | |
| RU2609134C2 (en) | Method, device and network equipment to obtain attribute information | |
| CN108924005B (en) | Network detection method, network detection apparatus, medium, and device | |
| CN110932933B (en) | Network condition monitoring method, computing device and computer storage medium | |
| CN109905396A (en) | A kind of WebShell file test method, device and electronic equipment | |
| CN107357885B (en) | Data writing method and device, electronic equipment and computer storage medium | |
| CN112688806A (en) | Method and system for presenting network assets | |
| CN114500467A (en) | Address conflict detection method, address conflict detection device and electronic equipment | |
| CN113014681A (en) | Network card binding method and device of multi-network card server, electronic equipment and storage medium | |
| US20130042020A1 (en) | Quick Network Path Discovery | |
| CN108965318B (en) | Method and device for detecting unauthorized access equipment IP in industrial control network | |
| CN112751704B (en) | Method, device and equipment for checking connectivity of heterogeneous network in network target range | |
| US10554760B2 (en) | Method and networking equipment for acquiring feature information | |
| CN110943887B (en) | Probe scheduling method, device, equipment and storage medium | |
| US11050629B2 (en) | Fingerprint determination for network mapping | |
| CN116074285A (en) | Address conflict detection method and device | |
| CN112152824A (en) | Performance index data acquisition method and device | |
| US20190089671A1 (en) | Application access method and application access system | |
| CN110611678B (en) | Method for identifying message and access network equipment | |
| CN114911515A (en) | Configuration management method, device, equipment and medium | |
| CN112104523B (en) | Detection method, device and equipment for flow transparent transmission and storage medium | |
| CN114520784A (en) | Dynamic content accelerated access method and device | |
| CN114499942A (en) | Data access method and device and electronic equipment |
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 |