A message forwarding method and device
By determining the unreachable route of the peer boundary device in the SAVA architecture and modifying the SAVA table entry to a low priority route, the traffic interruption problem caused by boundary device failure is solved, and traffic continuity and configuration in IPv6 multi-access environment are achieved simplify.
Patent Information
- Application Number
- CN202210470001.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-30
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2042-04-30
AI Technical Summary
In an IPv6 multi-access networking environment, when the boundary equipment fails or link failures, SAVA technology causes traffic interruption between the user network and the external network network, and the configuration management is complex, making misjudgment difficult.
By determining that the route of the peer boundary device is unreachable, modify the SAVA table entry to a low priority route, and forward data packets through the IPv6 over IPv6 tunnel to ensure traffic continuity and avoid traffic interruption.
It effectively avoids traffic interruption between the user network and the external network caused by boundary equipment failure under the SAVA architecture, simplifies the configuration management of network administrators, and improves the stability and reliability of the network.
Smart Images

Figure CN115037686B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to communication technology and in particular to a method and device for forwarding a message. Background Art
[0002] SAVA (Source Address Validation Architecture) is a technology that checks attack packets based on the routing information of the device. In an IPv6 multi-access networking environment, when routing asymmetry occurs, there is no guarantee that the outbound interface to the source IPv6 address of the packet found in the routing table is consistent with the inbound interface of the packet entering the device. SAVA technology can prevent source address-based attacks while avoiding misjudgments caused by asymmetric paths.
[0003] Figure 1 The following figure shows a common scenario where SAVA is deployed on a border device directly connected to a LAN. Due to the routing policy in the network, the host is assigned a primary IP address and a sub-IP address so that different devices and applications can be accessed through the primary IP address and the sub-IP address. However, the host is usually only configured with the gateway address of the primary IP address, and the addresses of the sub-IP network segment and the primary IP network segment are configured on the border devices 1 and 2 respectively. The SAVA function is enabled on Interface 10 and Interface 20 of the border devices 1 and 2, and the border devices 1 and 2 obtain the network prefix based on the local routing information to generate local SAVA table entries, and also generate SAVA table entries based on the routing entries of the other party learned by the routing protocol OSPF.
[0004] In this way, even if the host uses the sub-IP address to access the core network, the border device 1 will determine that the three-layer message from the sub-IP address is safe based on the SAVA table entry learned by the routing table entry, and will continue to forward it to the next-hop network device that reaches the core network according to the routing table entry, thereby preventing legitimate user messages from being discarded by mistake. However, the gateway address is configured for border device 2. Once border device 1 fails or the link between the border device and network device 3 fails, the three-layer message sent by the device in the core network to the host in the sub-IP network segment cannot be forwarded. Therefore, the same number of gateway addresses need to be configured on border devices 1 and 2. At that time, the more border devices there were in the network and the more gateway addresses there were in different network segments, the more difficult it was for network administrators to configure and manage, and the more complex the configuration items of the border devices were. Summary of the invention
[0005] The purpose of this application is to provide a message forwarding device to avoid traffic interruption between a user network and an external network caused by a boundary device failure.
[0006] To achieve the above-mentioned purpose, the present application provides a message forwarding method, which includes: determining that the route of the opposite border device is unreachable; setting the ineffective flag of the opposite ND table entry of the directly connected network segment of the opposite border interface of the synchronized opposite border device in the local neighbor discovery ND table to an effective flag and setting a non-aging flag; wherein the opposite border interface and the local border interface are directly connected to different network segments of the same local area network; modifying the network segment prefix of the source address verification architecture SAVA table entry of the directly connected network segment of the opposite border interface to a low priority route; publishing the low priority route to the previous-hop network device of the present device and the opposite border device to reach the core network, so that the previous-hop network device modifies the next-hop outgoing interface of the directly connected network segment of the opposite border interface to an interface connected to the present device; receiving an IPv6 data packet sent to the directly connected network segment of the opposite border interface; encapsulating it into an Ethernet data packet by matching the opposite ND table entry of the IPv6 data packet and sending the Ethernet data packet through the local border interface in the opposite ND table entry that matches the IPv6 data packet.
[0007] To achieve the above-mentioned purpose, the present application also provides a message forwarding device, which is a device for setting a gateway network segment in a source address verification architecture, and the device includes a processor and a memory; the processor executes the following operations by running the processor executable instructions in the memory: determining that the route of the opposite border device is unreachable; setting the opposite ND table entry ineffective flag of the directly connected network segment of the opposite border interface of the synchronized opposite border device in the local neighbor discovery ND table to an effective flag and setting a non-aging flag; wherein the opposite border interface and the local border interface are directly connected to different network segments of the same local area network; setting the opposite border interface The source address verification architecture SAVA table entry of the directly connected network segment modifies the network segment prefix to a low-priority route; publishes the low-priority route to the previous-hop network device between this device and the opposite-end border device to reach the core network, so that the previous-hop network device modifies the next-hop outgoing interface of the directly connected network segment of the opposite-end border interface to the interface connected to this device; receives the IPv6 datagram of the directly connected network segment sent to the opposite-end border interface; encapsulates it into an Ethernet datagram by matching the opposite-end ND table entry of the IPv6 datagram and sends the Ethernet datagram through the local border interface in the opposite-end ND table entry that matches the IPv6 datagram.
[0008] The beneficial effect of the present application is that when a boundary device under the SAVA architecture fails, the IP data packets from different network segments of the same local area network sent by the boundary interface of the opposite boundary device are diverted to the boundary interface of this device for forwarding, thereby avoiding traffic interruption between the user network and the external network caused by the failure of boundary devices in different network segments connected to the same local area network in the SAVA architecture. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1This is a common scenario where SAVA-deployed edge devices are directly connected to the LAN.
[0010] Figure 2 A flowchart of an embodiment of a message forwarding method provided by the present application;
[0011] Figure 3 A schematic diagram of switching the routing of a faulty border device in a scenario where a border device directly connected to a LAN with SAVA deployed is provided for this application;
[0012] Figure 4 A schematic diagram of an embodiment of a message forwarding device provided in this application. DETAILED DESCRIPTION
[0013] The present invention will be described in detail with multiple examples shown in multiple figures. In the following detailed description, multiple specific details are used to provide a comprehensive understanding of the present application. Known methods, steps, components and circuits are not described in detail in the examples to avoid making these examples difficult to understand.
[0014] Among the terms used, the term "include" means including but not limited to; the term "contain" means including but not limited to; the terms "above", "within" and "below" are inclusive of the number; the terms "greater than" and "less than" are exclusive of the number. The term "based on" means based on at least a part thereof.
[0015] Figure 2 A flowchart of an embodiment of a message forwarding method provided in the present application; the method embodiment includes:
[0016] Step 201: Determine that the route of the peer edge device is unreachable.
[0017] Step 202: Set the invalid flag of the opposite ND table entry of the directly connected network segment of the opposite border interface of the synchronized opposite border device in the local neighbor discovery ND table to a valid flag and set a non-aging flag.
[0018] In the SAVA architecture applied in the present application, the peer boundary interface and the local boundary interface are directly connected to different network segments of the same local area network.
[0019] Step 203: modify the network segment prefix of the source address verification architecture SAVA table entry of the directly connected network segment of the peer boundary interface to a low priority route.
[0020] Step 204: publish the low priority route to the previous hop network device between the local device and the peer edge device to reach the core network.
[0021] In the present application, the border device publishes a low-priority route so that the previous-hop network device modifies the next-hop outgoing interface of the directly connected network segment of the opposite-end border interface to the interface connected to the current device, thereby diverting traffic.
[0022] Step 205: Receive an IPv6 datagram sent to the directly connected network segment of the peer boundary interface.
[0023] Step 206: Encapsulate the IPv6 datagram into an Ethernet datagram by matching the peer ND table entry and send the Ethernet datagram through the local boundary interface in the peer ND table entry matching the IPv6 datagram.
[0024] The beneficial effect of the present application is that when a boundary device under the SAVA architecture fails, the IP data packets from different network segments of the same local area network sent by the boundary interface of the opposite boundary device are diverted to the boundary interface of this device for forwarding, thereby avoiding traffic interruption between the user network and the external network caused by the failure of boundary devices in different network segments connected to the same local area network in the SAVA architecture.
[0025] Figure 3 In the example, the network segment 10::0 / 64 is configured for edge device 1, and the IPv6 address of the edge interface Interface 10 is 10::1. The network segment 11::0 / 64 is configured for the gateway of edge device 2, and the IPv6 address of the edge interface Interface 20 is 11::1. The SAVA function is enabled on the edge interfaces Interface 10 and 20 connected to the LAN, and Tag 100 is bound to them.
[0026] In the SAVA scenario, in order to allow edge devices connected to the same LAN to obtain edge devices in the LAN, each edge device synchronizes the locally learned LAN routing information and the label of the edge interface connected to the LAN to other edge devices through the routing protocol, so that other edge devices at the other end can learn all prefixes in the LAN through remote routing synchronization.
[0027] Figure 3 In the embodiment, the border device 1 sets an interface host route for the IPv6 address 10::1 of the border interface Interface10, and the border device 2 sets an interface host route for the IPv6 address 11::1 of the border interface Interface20.
[0028] Border device 1 synchronizes the network segment route 10:: / 64 of the terminal IPv6 address with tag 100 and the host route 10::1 / 128 of the interface IPv6 address of Inetrface10 to border device 2 through the routing protocol OSPF.
[0029] Border device 2 synchronizes the network segment route 11:: / 64 of the terminal IPv6 address with tag 100 and the host route 11::1 / 128 of the interface IPv6 address of Interface 20 to border device 1 through the routing protocol OSPF.
[0030] Edge device 1 obtains the network segment prefix 11:: / 64 in the LAN of Tag100 and generates a SAVA table entry for the network segment prefix 11:: / 64. The outbound interface of the network segment prefix 11:: / 64 is Interface10.
[0031] Based on the host route of interface Interface 20 and Tag value 100, edge device 1 establishes an IPv6 over IPv6 tunnel from edge interface Interface 10 of the LAN identified by Tag 100 to edge interface Interface 20, where the source IP address and destination IP address are IPv6 address 10::1 of Interface 10 and IPv6 address 11::1 of Interface 20 respectively.
[0032] Edge device 2 obtains the network segment prefix 10:: / 64 in the LAN and generates a SAVA table entry for the network segment prefix 10:: / 64. The outbound interface of the network segment prefix 10:: / 64 is Interface 20.
[0033] Based on the host route of interface 10 and the tag value 100, edge device 2 establishes an IPv6 over IPv6 tunnel from edge interface 20 of the LAN to edge interface 10, where the source IP address and destination IP address are the IPv6 address 11::1 of Interface 20 and the IPv6 address 10::1 of Interface 10, respectively.
[0034] A pair of IPv6 over IPv6 tunnels between the border interfaces of border devices 1 and 2 form a table synchronization tunnel for synchronizing the ND table entries of the directly connected network segments.
[0035] Border device 1 encapsulates the learned ND entry 10::2 of the sub-IP address of the terminal in the LAN in the TLV field of the IP message, and encapsulates the outer tunnel IP message header of the IP data message carrying the synchronized ND entry according to the IPv6 over IPv6 tunnel of Interface 20 connected to the border device, and sends it to border device 2.
[0036] That is, the border device 1 searches for the next hop according to the destination IP address of the tunnel IP message header, encapsulates the outer Ethernet message according to the MAC address of the next hop, and sends it to the next hop device of the border device Interface 20 through the Layer 2 network. The next hop device receives the IPv6 over IPv6 tunnel message, determines that the outer destination MAC address is the IP address of the device, removes the outer destination MAC address, searches for the next next hop of the destination IP address of the tunnel IP message header, encapsulates the outer Ethernet message according to the MAC address of the next next hop, and sends it to the next next hop device of the border device Interface 20 through the Layer 2 network. In this way, the IPv6 over IPv6 tunnel message with the synchronization ND table entry is sent to the border device 2 hop by hop, and the device on the IPv6 over IPv6 tunnel will not parse the synchronization ND table entry carried inside.
[0037] Border device 2 encapsulates the ND entry 11::2 of the primary IP address of the terminal in the LAN learned in the TLV field of the IP message, and encapsulates the outer tunnel IP message header of the IP data message carrying the synchronization ND entry according to the IPv6over IPv6 tunnel from Interface 20 to Interface 10, and sends it to border device 1.
[0038] Border device 1 receives the IPv6 over IPv6 tunnel message and records the synchronized ND entry of 11::2 as an ND entry with an invalid flag in the ND table, where the outgoing interface is Interface 10. Border device 2 receives the IPv6 over IPv6 tunnel message and records the synchronized ND entry of 10::2 as an ND entry with an invalid flag in the ND table, where the outgoing interface is Interface 20.
[0039] When the border device 1 fails or the link between the border device 1 and the network device 3 fails, the network topology in the network reconverges, and the routing table entry on the border device 2 that reaches the border device 1 is deleted based on the reconverged network topology, the border device 2 determines that the route of the border device 1 on the other end is unreachable, and the border device 2 sets the IPv6over IPv6 tunnel of Interface 10 connected to the border device 1 to the failure (down) state, and sets the invalid ND table entry recorded in the ND table to the ND table entry with the effective flag and the SAVA flag. The border device 2 does not perform aging processing on the ND table entry with the SAVA flag.
[0040] Based on the IPv6 over IPv6 tunnel connected to the border device 1 in the faulty state, the border device 2 changes the SAVA table entry of the network segment prefix 10:: / 64 to which the destination IP address of the tunnel belongs to the SAVA backup state; the SAVA table entry in the backup state prompts the network administrator that there is a network fault. However, the border device 2 still checks whether the received data message is legal based on the SAVA table entry in the backup state.
[0041] Border device 2 modifies the network segment prefix 10:: / 64 of the SAVA table entry in the backup state to a low priority route and publishes the route to border device 3 through routing protocol message 303. Network device 3 learns the route of network segment prefix 10:: / 64 by connecting to border device 2. The outbound interface of the route information of network segment prefix 10:: / 64 in the routing table of network device 3 is the outbound interface to border device 2.
[0042] When the network device 3 receives an IP data packet addressed to the IPv6 primary IP address of the terminal, it sends the IP packet to the edge device 2 according to the outgoing interface information in the routing table.
[0043] Boundary device 2 finds the effective ND table entry with the SAVA identifier according to the destination IPv6 address, and sends the IP datagram with the IPv6 primary IP address to the terminal through the outgoing interface Interface 20 in the ND table entry; that is, the MAC address corresponding to the IPv6 primary IP address in the ND table entry is used as the destination MAC address, the MAC address of Interface 20 is used as the source MAC address, the outer Ethernet header is encapsulated for the IP datagram, and then it is sent through Interface 20.
[0044] When the failure of border device 1 is restored or the link failure between border devices 1 and 3 is restored, border device 1 will normally send the direct route of network segment prefix 10:: / 64. Because border device 2 modifies its route priority to a lower priority before publishing network segment prefix 10:: / 64, the network segment prefix 10:: / 64 normally published by border device 1 has a higher route priority. Based on the route priority, network device 3 will preferentially learn the route of network segment prefix 10:: / 64 published by border device A. The outgoing interface of network segment prefix 10:: / 64 in the route table entry is the interface connected to border device 1. In this way, the subsequent three-layer data IP sent by network device 3 to the terminal will be forwarded through border device 1 again.
[0045] Border device 1 publishes the network segment route 10:: / 64 with tag 100 and the host route of interface IPv6 address 10::1 / 128 of Inetrface10 to border device 2 through the routing protocol. Border device 2 stops publishing the route of network segment prefix 10:: / 64 to network device 3, re-establishes the IPv6 over IPv6 tunnel connected to Interface 10 of border device 1, resets the effective ND table entry with SAVA flag to the ND table entry with ineffective flag, and sets the SAVA table entry of network segment prefix 10:: / 64 in backup state to normal state.
[0046] At this time, the data packets sent from the user network to the external network can be forwarded normally according to the SAVA table entry of the edge device 1, and the data packets sent from the external network to the user network can be forwarded normally according to the routing information released by the edge device 1.
[0047] Figure 4 This is a schematic diagram of an embodiment of a message forwarding device provided by the present application. The device 400, as a boundary device for setting a gateway network segment in a source address verification architecture, may at least include: a network interface, a switching chip, a CPU, and a memory.
[0048] The processor performs the following operations by running the processor executable instructions in the memory: determining that the route of the opposite border device is unreachable; setting the opposite ND table entry of the directly connected network segment of the opposite border interface of the synchronized opposite border device in the local neighbor discovery ND table to an effective flag and setting a non-aging flag; wherein the opposite border interface and the local border interface are directly connected to different network segments of the same local area network; modifying the network segment prefix of the source address verification architecture SAVA table entry of the directly connected network segment of the opposite border interface to a low priority route; publishing the low priority route to the previous hop network device of the present device and the opposite border device to reach the core network, so that the previous hop network device modifies the next hop outgoing interface of the directly connected network segment of the opposite border interface to the interface connected to the present device; receiving an IPv6 datagram sent to the directly connected network segment of the opposite border interface; encapsulating the opposite ND table entry that matches the IPv6 datagram into an Ethernet datagram and sending the Ethernet datagram through the local border interface in the opposite ND table entry that matches the IPv6 datagram.
[0049] Before the processor determines that the route of the opposite border device is unreachable by running the instructions in the memory, it also performs the following operations: establishing a source address verification architecture SAVA table entry for the directly connected network segment of the opposite border interface; establishing an IPv6 over IPv6 tunnel between the local border interface and the opposite border interface; and synchronizing the ND table entry of the directly connected network segment of the local border interface and the ND table entry of the directly connected network segment of the opposite border interface through the IPv6 over IPv6 tunnel.
[0050] The processor executes the instructions in the memory to establish an IPv6 over IPv6 tunnel between the local border interface and the opposite border interface, including: establishing a host route for the local border interface; publishing the host route of the local border interface with a LAN label to the opposite border device; so that the opposite border device establishes an IPv6over IPv6 tunnel connected to the local border port; receiving the host route of the opposite border interface with a LAN label published by the opposite border device; establishing an IPv6 over IPv6 tunnel with the IPv6 address of the host route of the opposite border interface as the destination IP address and the IPv6 address of the local border interface as the source IP address.
[0051] The processor executes the synchronization of the ND table entry of the directly connected network segment of the local border interface and the ND table entry of the directly connected network segment of the opposite border interface through the IPv6 over IPv6 tunnel by running the instructions in the memory, including: receiving the ND table entry of the IP address of the directly connected network segment of the opposite border interface through the IPv6 over IPv6 tunnel connected to the local border port; recording the ND table entry of the IP address of the directly connected network segment of the opposite border interface as the opposite ND table entry with an invalid flag in the local ND table and an output interface being the local border port; and sending the ND table entry of the IP address of the directly connected network segment of the local border interface through the IPv6 over IPv6 tunnel connected to the opposite border port.
[0052] The processor further performs the following operations by running the processor executable instructions in the memory: determining that the route of the opposite edge device is reachable; setting the validity flag of the opposite ND table entry in the local ND table to the invalid flag and deleting the non-aging flag.
[0053] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A message forwarding method, characterized in that: The method comprises: Determine that the route to the peer border device is unreachable; Setting the established IPv6 over IPv6 tunnel between the local border interface and the opposite border interface of the opposite border device to fault; The opposite-end ND table entry of the directly connected network segment of the opposite-end border interface of the synchronized opposite-end border device in the local neighbor discovery ND table is set to the valid flag and the non-aging flag is set; wherein the opposite-end border interface and the local border interface are directly connected to different network segments of the same local area network; Modify the network segment prefix of the source address verification architecture SAVA table entry of the directly connected network segment of the opposite end boundary interface to a low priority route; Publishing the low-priority route to the previous-hop network device of the local device and the opposite-end border device to reach the core network, so that the previous-hop network device modifies the next-hop outgoing interface of the directly connected network segment of the opposite-end border interface to the interface connected to the local device; Receiving an IPv6 datagram sent to a directly connected network segment of the opposite end boundary interface; The IPv6 data message is encapsulated into an Ethernet data message by matching the peer ND table entry of the IPv6 data message, and the Ethernet data message is sent by matching the local boundary interface in the peer ND table entry of the IPv6 data message.
2. The method according to claim 1, characterized in that: Before determining that the route of the peer edge device is unreachable, the method further includes: Establishing the source address verification architecture SAVA table entry for the directly connected network segment of the opposite end boundary interface; Establishing the IPv6 over IPv6 tunnel between the local border interface and the opposite border interface; The ND table entries of the directly connected network segment of the local border interface and the ND table entries of the directly connected network segment of the opposite end border interface are synchronized through the IPv6 over IPv6 tunnel.
3. The method according to claim 2, characterized in that Establishing an IPv6 over IPv6 tunnel between the local border interface and the opposite border interface includes: Establishing a host route for the local border interface; Publishing the host route of the local border interface with the LAN label to the opposite border device; so that the opposite border device establishes an IPv6 over IPv6 tunnel connected to the local border port; Receiving a host route of the peer boundary interface with the LAN label issued by the peer boundary device; An IPv6 over IPv6 tunnel is established with the IPv6 address of the host route of the opposite boundary interface as the destination IP address and the IPv6 address of the local boundary interface as the source IP address.
4. The method according to claim 2, characterized in that: The ND table entry of the directly connected network segment of the local border interface and the ND table entry of the directly connected network segment of the opposite end border interface synchronized through the IPv6 over IPv6 tunnel include: Receive an ND table entry of the IP address of the directly connected network segment of the opposite end border interface through an IPv6 over IPv6 tunnel connected to the local border port; Recording the ND table entry of the IP address of the directly connected network segment of the peer boundary interface as the peer ND table entry with an invalid flag in the local ND table and an outgoing interface as the local boundary port; The ND table entry of the IP address of the directly connected network segment of the local border interface is sent through the IPv6 over IPv6 tunnel connected to the peer border port.
5. The method according to claim 1, characterized in that: The method further comprises: Determining that the route of the opposite edge device is reachable; The validity flag of the peer ND entry in the local ND table is set to an invalid flag and the non-aging flag is deleted.
6. A message forwarding device, the device being used as a device for setting a gateway network segment in a source address verification architecture, characterized in that: The device includes a processor and a memory, wherein the processor executes processor-executable instructions in the memory to perform the following operations: Determine that the route to the peer border device is unreachable; Setting an IPv6 over IPv6 tunnel of an opposite-end border interface connected to the opposite-end border device to be faulty; The opposite-end ND table entry of the directly connected network segment of the opposite-end border interface of the synchronized opposite-end border device in the local neighbor discovery ND table is set to the valid flag and the non-aging flag is set; wherein the opposite-end border interface and the local border interface are directly connected to different network segments of the same local area network; Modify the network segment prefix of the source address verification architecture SAVA table entry of the directly connected network segment of the opposite end boundary interface to a low priority route; Publishing the low-priority route to the previous-hop network device of the local device and the opposite-end border device to reach the core network, so that the previous-hop network device modifies the next-hop outgoing interface of the directly connected network segment of the opposite-end border interface to the interface connected to the local device; Receiving an IPv6 datagram sent to a directly connected network segment of the opposite end boundary interface; The IPv6 data message is encapsulated into an Ethernet data message by matching the peer ND table entry of the IPv6 data message, and the Ethernet data message is sent by matching the local boundary interface in the peer ND table entry of the IPv6 data message.
7. The device according to claim 6, characterized in that Before the processor determines that the route of the opposite-end edge device is unreachable by running the instructions in the memory, the processor further performs the following operations: Establishing the source address verification architecture SAVA table entry for the directly connected network segment of the opposite end boundary interface; Establishing the IPv6 over IPv6 tunnel between the local border interface and the opposite border interface; The ND table entries of the directly connected network segment of the local border interface and the ND table entries of the directly connected network segment of the opposite end border interface are synchronized through the IPv6 over IPv6 tunnel.
8. The device according to claim 7, characterized in that The processor executes the instructions in the memory to establish an IPv6 over IPv6 tunnel between the local border interface and the opposite border interface, including: Establishing a host route for the local border interface; Publishing the host route of the local border interface with the LAN label to the opposite border device; so that the opposite border device establishes an IPv6 over IPv6 tunnel connected to the local border port; Receiving a host route of the peer boundary interface with the LAN label issued by the peer boundary device; An IPv6 over IPv6 tunnel is established with the IPv6 address of the host route of the opposite boundary interface as the destination IP address and the IPv6 address of the local boundary interface as the source IP address.
9. The device according to claim 7, characterized in that The processor executes the synchronization of the ND table entry of the directly connected network segment of the local border interface and the ND table entry of the directly connected network segment of the opposite end border interface through the IPv6 over IPv6 tunnel by running the instructions in the memory, including: Receive an ND table entry of the IP address of the directly connected network segment of the opposite end border interface through an IPv6 over IPv6 tunnel connected to the local border port; Recording the ND table entry of the IP address of the directly connected network segment of the peer boundary interface as the peer ND table entry with an invalid flag in the local ND table and an outgoing interface as the local boundary port; The ND table entry of the IP address of the directly connected network segment of the local border interface is sent through the IPv6 over IPv6 tunnel connected to the peer border port.
10. The device according to claim 6, characterized in that The processor further performs the following operations by executing the processor executable instructions in the memory: Determining that the route of the opposite edge device is reachable; The validity flag of the peer ND entry in the local ND table is set to an invalid flag and the non-aging flag is deleted.
Citation Information
Patent Citations
Multiple engine quick master-slave swap and its method
CN101052010A
Method and equipment for forwarding message
CN103457854A
IPv6 option explicit source address encryption security verification gateway and verification method
CN114389835A
Efficient mechanism for fast recovery in case of border router node failure in a computer network
US20060126502A1
