CN113542095A - Equipment and method for recovering tunnel - Google Patents
Equipment and method for recovering tunnel Download PDFInfo
- Publication number
- CN113542095A CN113542095A CN202110691987.6A CN202110691987A CN113542095A CN 113542095 A CN113542095 A CN 113542095A CN 202110691987 A CN202110691987 A CN 202110691987A CN 113542095 A CN113542095 A CN 113542095A
- Authority
- CN
- China
- Prior art keywords
- address
- tunnel
- vxlan tunnel
- private network
- public network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2592—Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a device and a method for recovering a tunnel. The method comprises the following steps: establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends; establishing a public network VXLAN tunnel connection core node; determining a public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through a private network VXLAN tunnel; and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
Description
Technical Field
The present application relates to communications technologies, and in particular, to an apparatus and a method for recovering a tunnel thereof.
Background
VXLAN (Virtual eXtensible local area Network) is a two-layer VPN (Virtual Private Network) technology, and is used to encapsulate a two-layer data packet in a UDP packet (User Datagram Protocol) and transmit the two-layer data packet in a three-layer Network.
In the VXLAN network, a private network VXLAN Tunnel is established between VTEPs (VXLAN Tunnel End points ) of Leaf node roles of a client access VXLAN, and a public network Tunnel is established between the VTEP of the Leaf node roles and the VTEP of a core node role. Although it can be detected by using a network detection technology that the different reasons of the Leaf node link are a private network tunnel fault or a public network tunnel fault, the Leaf node tunnel cannot be automatically recovered, so that the Leaf node fails to access the message to the VXLAN network.
Disclosure of Invention
The present application aims to provide a device and a method for recovering a tunnel thereof, so that a VTEP device of a Leaf node repairs a failed VXLAN tunnel, and a packet forwarding service is performed normally.
In order to achieve the above object, the present application provides a tunnel recovery method, including: establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends; establishing a public network VXLAN tunnel connection core node; determining a public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through a private network VXLAN tunnel; and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
To achieve the above object, the present application also provides an apparatus whose tunnel endpoint, which is a leaf node of a virtual extensible local area network, includes a processor and a memory for storing processor-executable instructions; wherein the processor is configured to perform the following by executing the processor-executable instructions in the memory: establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends; establishing a public network VXLAN tunnel connection core node; determining a public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through a private network VXLAN tunnel; and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
The method has the advantages that when the public network tunnel between the Leaf nodes fails, the Leaf nodes can reconstruct the tunnel reaching the core node through the source IP address of the private network tunnel connected between the Leaf nodes at the opposite end and the entrance IP address of the private network tunnel penetrated by the core node, so that the message forwarding service can be carried out between the Leaf nodes and the core node through the reconstructed VXLAN tunnel.
Drawings
FIG. 1 is a flowchart of an embodiment of a method for recovering a tunnel provided herein;
fig. 2 is a schematic diagram of a recovery tunnel within a VxLAN network provided by the present application;
fig. 3 is a schematic diagram of an embodiment of an apparatus provided herein.
Detailed Description
A detailed description will be given of a number of examples shown in a number of figures. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present application. Well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the examples.
The term "including" as that term is used is meant to include, but is not limited to; the term "comprising" means including but not limited to; the terms "above," "within," and "below" include the instant numbers; the terms "greater than" and "less than" mean that the number is not included. The term "based on" means based on at least a portion thereof.
Fig. 1 is a flowchart of an embodiment of a method for recovering a tunnel according to the present application, including the following steps:
and step 104, reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
The method has the advantages that when the public network tunnel between the Leaf nodes fails, the Leaf nodes can reconstruct the tunnel reaching the core node through the source IP address of the private network tunnel connected between the Leaf nodes at the opposite end and the entrance IP address of the private network tunnel penetrated by the core node, so that the message forwarding service can be carried out between the Leaf nodes and the core node through the reconstructed VXLAN tunnel.
Fig. 2 is a schematic diagram of recovering a tunnel in a VxLAN network provided by the present application. The three interfaces (not shown in fig. 2) 211, 212, 213 of the Leaf node 21 are configured with IP addresses IP211, IP212, IP 213; the three interfaces (not shown in fig. 2) 221, 222, 223 of the Leaf node 22 are configured with IP addresses IP221, IP222, IP 223; the four interfaces 231, 232, 233 of the Spine node (not shown in fig. 2) are configured with IP addresses of IP231, IP232, IP233, and IP 234.
The Leaf21 establishes a public network tunnel reaching the Spine node by taking the IP address IP211 of the interface 211 as a source IP address and the IP address of the interface 231 as a destination IP address; the Spine node establishes a public network tunnel to reach the Leaf21 node with the IP address IP231 of the interface 231 as the source IP address and the IP address of the interface 211 as the destination IP address.
The Leaf22 establishes a public network tunnel reaching the Spine node by taking the IP address IP221 of the interface 221 as a source IP address and the IP address of the interface 232 as a destination IP address; the Spine node establishes a public network tunnel reaching a Leaf22 point by taking the IP address IP232 of the interface 232 as a source IP address and the IP address of the interface 221 as a destination IP address.
The Leaf21 establishes a private network tunnel reaching the Leaf22 node by taking the IP address IP212 of the interface 212 as a source IP address and the IP address IP222 of the interface 222 as a destination IP address, and the next hop of the IP address IP212 of the interface 212 of the Leaf21 reaching the IP address IP222 of the interface 222 of the Leaf22 is the IP address IP233 of the interface 233 of the Spine node.
The Leaf22 establishes a private network tunnel reaching the Leaf21 node by taking the IP address IP222 of the interface 222 as a source IP address and the IP address IP212 of the interface 212 as a destination IP address, and the next hop of the IP address IP222 of the interface 222 of the Leaf22 reaching the IP address IP222 of the interface 212 of the Leaf21 is the IP address IP234 of the interface 234 of the Spine node.
When receiving that the message of the connected terminal needs to be sent to the server connected to the Spine node 23, the Leaf21 sends the VXLAN message to the Spine node 23 according to the VXLAN public network tunnel encapsulation message with the source IP address IP211 and the destination IP address IP 231. After receiving the VXLAN message, the Spine node 23 decapsulates the VXLAN message and sends the VXLAN message to a corresponding server according to the destination MAC address.
When receiving that the message of the connected terminal needs to be sent to the server connected to the Spine node 23, the Leaf22 sends the VXLAN message to the Spine node 23 according to the VXLAN public network tunnel encapsulation message with the source IP address being IP221 and the destination IP address being IP 232. After receiving the VXLAN message, the Spine node 23 decapsulates the VXLAN message and sends the VXLAN message to a corresponding server according to the destination MAC address.
Its next hop IP address IP233, on top of the original source IP address of the private network tunnel configured with Leaf21 of Leaf 21; the Leaf22 is configured with a next hop IP address IP234 of the original source IP address of the private network tunnel of Leaf 22.
When receiving the message of the connected terminal and needing to be sent to the terminal connected by the Leaf22, the Leaf21 sends the VXLAN message to the interface 233 of the next-hop Spine node 23 of the IP212 according to the VXLAN public network tunnel encapsulation message with the source IP address of the IP212 and the destination IP address of the IP 222. The Spine node 23 receives the VXLAN message through the interface 233, strips off the outer ethernet header, repackages the ethernet header according to the interface 234 connecting the outer destination IP address in the VXLAN header, and sends the message to the Leaf 22. And the Leaf22 decapsulates the VXLAN message according to the received VXLAN message, and sends the message to a destination end according to the destination MAC address.
Similarly, when receiving the message from the connected terminal and needing to be sent to the terminal connected by the Leaf21, the Leaf22 sends the VXLAN message to the interface 234 of the next-hop Spine node 23 of the IP222 according to the VXLAN public network tunnel encapsulation message whose source IP address is IP222 and destination IP address is IP 212. The Spine node 23 receives the VXLAN message through the interface 234, strips off the outer ethernet header, repackages the ethernet header according to the interface 232 connecting the outer destination IP address in the VXLAN header, and sends the message to the Leaf 21. And the Leaf21 decapsulates the VXLAN message according to the received VXLAN message, and sends the message to a destination end according to the destination MAC address.
The IP address of the interface 233 of the Spine node 23 is an ingress interface IP address of a private network tunnel traversing leaf21 to leaf 22; the IP address of the interface 234 of the Spine node 23 is the ingress interface IP address of the private network tunnel traversing leaf22 to leaf 221.
When leaf21 determines that the public network tunnel connected with leaf 23 has a fault, the original source IP address IP212 of the private network tunnel connected with leaf22 is used as a source IP address, and the entrance interface IP address IP233 of the private network tunnel crossed by the leaf node is used as a destination IP address to establish the public network tunnel. Then, when the Leaf21 receives that the message of the connected terminal needs to be sent to the server connected to the Spine node 23, the VXLAN message is sent to the Spine node 23 according to the VXLAN public network tunnel encapsulation message with the source IP address being IP212 and the destination IP address being IP 233. After receiving the VXLAN message, the Spine node 23 decapsulates the VXLAN message and sends the VXLAN message to a corresponding server according to the destination MAC address. When Leaf21 determines the public network tunnel policy, it re-establishes the public network tunnel to reach Spine node with the IP address IP211 of interface 211 as the source IP address and the IP address of interface 231 as the destination IP address.
When leaf22 determines that the public network tunnel connected with leaf 23 has a fault, the original source IP address IP222 of the private network tunnel connected with leaf21 is used as a source IP address, and the entrance interface IP address IP234 of the private network tunnel crossed by the leaf node is used as a destination IP address to establish the public network tunnel. Then, when the Leaf22 receives that the message of the connected terminal needs to be sent to the server connected to the Spine node 23, the VXLAN message is sent to the Spine node 23 according to the VXLAN public network tunnel encapsulation message with the source IP address IP222 and the destination IP address IP 234. After receiving the VXLAN message, the Spine node 23 decapsulates the VXLAN message and sends the VXLAN message to a corresponding server according to the destination MAC address. When Leaf22 determines the policy of the public network tunnel, it re-establishes the public network tunnel to reach the Spine node with the IP address IP221 of interface 221 as the source IP address and the IP address of interface 232 as the destination IP address.
Fig. 3 is a schematic diagram of an embodiment of an apparatus provided herein. The device can be used for the tunnel endpoint of the leaf node role of VXLAN. The device comprises a switching unit 301 implemented as a switching chip, a processor 302 and a memory 303. The memory is used for storing processor executable instructions; wherein the processor 302 is configured to execute the processor 302 executable instructions in the memory to: establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends; establishing a public network VXLAN tunnel connection core node; determining a public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through a private network VXLAN tunnel; and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
Processor 302, by executing processor-executable instructions in memory 303, also performs the following: determining the failure recovery of a public network VXLAN tunnel; and reestablishing the public network tunnel by using the original source IP address and the original destination IP address of the public network VXLAN tunnel.
Processor 302, by executing processor-executable instructions in memory 303, also performs the following: determining a private network VXLAN tunnel fault, and acquiring a destination IP address of an opposite-end private network VXLAN tunnel from a central node to an opposite-end leaf node; and establishing a private network tunnel by using the original IP address of the public network VXLAN tunnel and the acquired destination IP address.
Processor 302, by executing processor-executable instructions in memory 303, also performs the following: determining the recovery of private network VXLAN tunnel failure; and reestablishing the private network tunnel by using the original source IP address and the original destination IP address of the private network VXLAN tunnel.
Before the processor 302 executes the establishment of the private network virtual extensible local area network VXLAN tunnel to connect the leaf nodes of the opposite end by executing the instructions in the memory 303, the following operations are also executed: configuring an original source IP address and a destination IP address of a private network VXLAN tunnel; configuring an original source IP address and an original destination IP address of a public network VXLAN tunnel; and configuring an original source IP address and an original destination IP address of the VXLAN tunnel of the opposite-end public network.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A method of recovering a tunnel, the method comprising:
establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends;
establishing a public network VXLAN tunnel connection core node;
determining the public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through the private network VXLAN tunnel;
and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
2. The method of claim 1, further comprising:
determining that the public network VXLAN tunnel fault is recovered;
and reestablishing the public network tunnel by using the original source IP address and the original destination IP address of the public network VXLAN tunnel.
3. The method of claim 2, further comprising:
determining the private network VXLAN tunnel fault, and acquiring a destination IP address of an opposite-end private network VXLAN tunnel from the central node to the opposite-end leaf node;
and establishing the private network tunnel by using the original IP address of the public network VXLAN tunnel and the obtained destination IP address.
4. The method of claim 3, further comprising:
determining that the private network VXLAN tunnel failure is recovered;
and reestablishing the private network tunnel by using the original source IP address and the original destination IP address of the private network VXLAN tunnel.
5. The method of claim 4, wherein before establishing a private network virtual extensible local area network (VXLAN) tunnel to connect to a peer leaf node, the method further comprises:
configuring an original source IP address and a destination IP address of the private network VXLAN tunnel; configuring an original source IP address and an original destination IP address of the public network VXLAN tunnel; and configuring an original source IP address and an original destination IP address of the opposite-end public network VXLAN tunnel.
6. An apparatus, usable for a tunnel endpoint that is a leaf node of a tunnel endpoint of a virtual extensible local area network, comprising a processor and a memory, wherein the memory is to store processor-executable instructions; wherein the processor, by executing the processor-executable instructions in the memory, is to perform operations comprising:
establishing a private network virtual extensible local area network VXLAN tunnel to connect leaf nodes of opposite ends;
establishing a public network VXLAN tunnel connection core node;
determining the public network VXLAN tunnel fault, and acquiring an entrance IP address of a central node passing through the private network VXLAN tunnel;
and reestablishing the public network tunnel by using the source IP address of the private network VXLAN tunnel and the acquired entrance IP address.
7. The device of claim 6, wherein the processor, by executing the processor-executable instructions in the memory, further performs the following:
determining that the public network VXLAN tunnel fault is recovered;
and reestablishing the public network tunnel by using the original source IP address and the original destination IP address of the public network VXLAN tunnel.
8. The device of claim 7, wherein the processor, by executing the processor-executable instructions in the memory, further performs the following:
determining the private network VXLAN tunnel fault, and acquiring a destination IP address of an opposite-end private network VXLAN tunnel from the central node to the opposite-end leaf node;
and establishing the private network tunnel by using the original IP address of the public network VXLAN tunnel and the obtained destination IP address.
9. The device of claim 8, wherein the processor, by executing the processor-executable instructions in the memory, further performs the following:
determining that the private network VXLAN tunnel failure is recovered;
and reestablishing the private network tunnel by using the original source IP address and the original destination IP address of the private network VXLAN tunnel.
10. The apparatus of claim 9, wherein the processor executes the following operations before executing the instructions in the memory to establish a private network virtual extensible local area network (VXLAN) tunnel to connect to a peer leaf node:
configuring an original source IP address and a destination IP address of the private network VXLAN tunnel; configuring an original source IP address and an original destination IP address of the public network VXLAN tunnel; and configuring an original source IP address and an original destination IP address of the opposite-end public network VXLAN tunnel.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110691987.6A CN113542095B (en) | 2021-06-22 | 2021-06-22 | Equipment and method for recovering tunnel |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110691987.6A CN113542095B (en) | 2021-06-22 | 2021-06-22 | Equipment and method for recovering tunnel |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113542095A true CN113542095A (en) | 2021-10-22 |
| CN113542095B CN113542095B (en) | 2023-03-31 |
Family
ID=78125551
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110691987.6A Active CN113542095B (en) | 2021-06-22 | 2021-06-22 | Equipment and method for recovering tunnel |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113542095B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639417A (en) * | 2015-02-27 | 2015-05-20 | 杭州华三通信技术有限公司 | Method and device for binding public network link for ADVPN (auto discovery virtual private network) tunnel |
| CN104702480A (en) * | 2015-03-24 | 2015-06-10 | 华为技术有限公司 | Method and device for establishing tunnel protection group in next generation multicast virtual private network |
| CN104883287A (en) * | 2014-02-28 | 2015-09-02 | 杭州迪普科技有限公司 | Ipsec vpn system control method |
| CN105591870A (en) * | 2015-08-13 | 2016-05-18 | 杭州华三通信技术有限公司 | Tunnel establishment method and equipment |
| CN106878065A (en) * | 2017-01-18 | 2017-06-20 | 新华三技术有限公司 | A kind of collocation method and device of distributed paradigmatic system |
| CN109474687A (en) * | 2018-11-23 | 2019-03-15 | 杭州数梦工场科技有限公司 | A kind of methods, devices and systems of different private internetwork communications |
| CN110166270A (en) * | 2018-02-13 | 2019-08-23 | 中兴通讯股份有限公司 | Hot standby switch processing method, equipment and storage medium |
| EP3629164A1 (en) * | 2018-09-28 | 2020-04-01 | Juniper Networks, Inc. | Migrating workloads in multicloud computing environments |
| US20200213151A1 (en) * | 2018-12-26 | 2020-07-02 | Citrix Systems, Inc. | Intelligent and dynamic overlay tunnel formation via automatic discovery of citrivity/sdwan peer in the datapath in a pure plug and play environment with zero networking configuration |
| CN111988222A (en) * | 2020-08-31 | 2020-11-24 | 网易（杭州）网络有限公司 | Data transmission method and device, electronic equipment and computer readable storage medium |
-
2021
- 2021-06-22 CN CN202110691987.6A patent/CN113542095B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104883287A (en) * | 2014-02-28 | 2015-09-02 | 杭州迪普科技有限公司 | Ipsec vpn system control method |
| CN104639417A (en) * | 2015-02-27 | 2015-05-20 | 杭州华三通信技术有限公司 | Method and device for binding public network link for ADVPN (auto discovery virtual private network) tunnel |
| CN104702480A (en) * | 2015-03-24 | 2015-06-10 | 华为技术有限公司 | Method and device for establishing tunnel protection group in next generation multicast virtual private network |
| CN105591870A (en) * | 2015-08-13 | 2016-05-18 | 杭州华三通信技术有限公司 | Tunnel establishment method and equipment |
| CN106878065A (en) * | 2017-01-18 | 2017-06-20 | 新华三技术有限公司 | A kind of collocation method and device of distributed paradigmatic system |
| CN110166270A (en) * | 2018-02-13 | 2019-08-23 | 中兴通讯股份有限公司 | Hot standby switch processing method, equipment and storage medium |
| EP3629164A1 (en) * | 2018-09-28 | 2020-04-01 | Juniper Networks, Inc. | Migrating workloads in multicloud computing environments |
| CN109474687A (en) * | 2018-11-23 | 2019-03-15 | 杭州数梦工场科技有限公司 | A kind of methods, devices and systems of different private internetwork communications |
| US20200213151A1 (en) * | 2018-12-26 | 2020-07-02 | Citrix Systems, Inc. | Intelligent and dynamic overlay tunnel formation via automatic discovery of citrivity/sdwan peer in the datapath in a pure plug and play environment with zero networking configuration |
| CN111988222A (en) * | 2020-08-31 | 2020-11-24 | 网易（杭州）网络有限公司 | Data transmission method and device, electronic equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 丁娟: "私网STP在公网的透传", 《科学技术与工程》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113542095B (en) | 2023-03-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10938627B2 (en) | Packet processing method, device, and network system | |
| EP3198822B1 (en) | Computer network packet flow controller | |
| CN107819677B (en) | Message forwarding method and device | |
| US9608903B2 (en) | Systems and methods for recovery from network changes | |
| EP3231160B1 (en) | Stateful load balancing in a stateless network | |
| CN111343093B (en) | Service data transmission method and device | |
| EP3593498B1 (en) | Router device using flow duplication | |
| KR102342286B1 (en) | DCN message processing method, network device, and network system | |
| US9288129B2 (en) | Host-router virtual tunnelling and multiple tunnel management | |
| JPWO2001099354A1 (en) | Communication device including VPN accommodating function | |
| JP2007104440A (en) | Packet transmission system, its method, and tunneling device | |
| CN112887188B (en) | Message forwarding method and device | |
| US20070165603A1 (en) | Access network system, subscriber station device, and network terminal device | |
| CN106899500B (en) | Message processing method and device for cross-virtual extensible local area network | |
| US11601335B2 (en) | Methods and systems for neighbor-acknowledged graceful insertion/removal protocol | |
| CN115567346A (en) | Data message transmission method and device, electronic equipment and storage medium | |
| CN107659436B (en) | Method and device for preventing service interruption | |
| CN105592490A (en) | Route switching method and equipment | |
| CN106059885A (en) | Method and system for processing CAPWAP message by wireless controller | |
| CN113542095B (en) | Equipment and method for recovering tunnel | |
| CN108322379B (en) | Virtual private network VPN system and implementation method | |
| CN114338607B (en) | Method, device and system for confirming IP address of 5G user terminal | |
| EP2858415B1 (en) | Multi-link-based data transmission method and device | |
| CN104639417B (en) | A kind of method and apparatus of ADVPN tunnel binding public network link | |
| CN101150510B (en) | A method and device for realizing GRE protocol compatible IPinIP protocol |
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 |