A network comprises a destination node; a source node configured to output an enhanced route trace packet; and one or more intermediate nodes configured to forward the enhanced route trace packet toward the destination node based on a routing table until the enhanced route trace packet reaches the destination node. Each of the one or more intermediate nodes is further configured to insert identifying information into the enhanced route trace packet. The destination node is configured to send a response packet to the source node containing all the identifying information entered by the one or more intermediate nodes. The destination node is also configured to insert identifying information into the response packet.

The communication device comprises a first table that stores a first entry in which a match condition that includes at least a destination address is associated with an output destination of a packet matching the match condition; a second table that stores a second entry having a predetermined match condition; a destination learning unit that registers a set of a source and a receiving port of a received packet as a match condition and an output destination, respectively, in the first table; and a packet processing unit that forwards a packet to an output destination determined in the first table when an entry having a match condition matching a received packet is found from each of the first and second tables. The packet processing unit broadcasts a received packet according to a third entry when no entry having a match condition matching the received packet is found.

Embodiments of the present invention provide a Multiprotocol Label Switching traffic engineering tunnel establishing method and device. A tunnel establishing method includes: receiving, by a second routing device, an identifier, which is sent by a first routing device, of an MPLS TE tunnel from a first VPN instance to a second VPN instance; acquiring, by the second routing device according to the identifier, path information of the MPLS TE tunnel from the first VPN instance to the second VPN instance; and establishing an MPLS TE tunnel from the second VPN instance to the first VPN instance according to the acquired path information. Therefore, forward and reverse bidirectional tunnels are co-routed or partially co-routed, thereby solving a problem caused by non-co-routing during BFD.

A receiving node receives a virtual LDP initialization (vInit) message from a first node, where the vInit message comprises a request to establish a vLDP session between a requesting node and a target node. If the receiving node does not own a destination address of the vInit message, the receiving node is determined to be a relay node. The relay node inserts a relay label into the vInit message, where the relay label is an outgoing label that the relay node uses to reach the first node, and forwards the vInit message toward the destination address. If the receiving node owns the destination address, the receiving node is determined to be the target node, which extracts a stack of relay labels from the vInit message. The relay labels are used to define a return path to the requesting node for messages transmitted over the vLDP session.

Disclosed are a multi-connection system (MCS) and method for a service using an Internet protocol. The MCS includes a plurality of proxies; an MCS client to receive a packet to be transmitted from the client to the server, generate MCS packets by adding an MCS sequence identification (ID) to the packet, and sequentially and respectively transmit the MCS packets to the plurality of proxies, wherein a number of MCS packets corresponds to a number of pieces of proxy access information connected to the plurality of proxies or a set number of pieces of proxy access information; and an MCS server to respectively receive the MCS packets from the plurality of proxies; extract the MCS sequence IDs from the MCS packets, compare the extracted MCS sequence IDs with MCS sequence IDs stored beforehand; store the extracted MCS sequence IDs, generate server-receivable packets from the MCS packets, and transmit the server-receivable packets to the server when the extracted MCS sequence IDs are not identical to the stored MCS sequence IDs; and block the MCS packets from being transmitted to the server when the extracted MCS sequence IDs are identical to the stored MCS sequence IDs.

A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.

A packet processing method includes a first network device receiving a first Bit Index Explicit Replication (BIER) packet including a first BIER header. When the first BIER packet is a packet sent to a second network device, and in response to determining that the second network device is an edge node device in a BIER communication network and does not support BIER packet forwarding, the first network device determines a target label used for a reverse path forwarding (RPF) check, updates the first BIER packet to obtain a second BIER packet, where the second BIER packet includes the target label but does not include the first BIER header, and sends the second BIER packet to the second network device.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.

A distribution of a content selection being distributed throughout a wireless mesh network may be tracked. A wireless device in the wireless mesh network enables the content selection to be exchanged. Wireless devices then exchange the content, and a network topology is recorded in response. Finally, the network topology is reported to a reporting agent.