Method, apparatus and computer-readable medium for multicast communication in a containerized environment
By implementing a container with a routing table connected to a bridge, multicast traffic in containerized environments is effectively managed, ensuring correct routing and addressing, thus enhancing network efficiency and security.
Patent Information
- Application Number
- JP2024525625
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-26
- Filing Date
- 2022-05-26
- Publication Date
- 2024-11-13
AI Technical Summary
In containerized environments, multicast traffic from applications running on containers is not effectively managed due to network bridges hiding containers, making it difficult to associate multicast groups with specific applications.
Implementing a container that stores a routing table and is connected to a bridge, allowing the host network element to manage multicast traffic by modifying the routing table to set the bridge as the next hop for packets destined for a multicast group, increasing the expiration parameter, and configuring address changes to facilitate communication.
Enables efficient and secure multicast communication within containerized environments by ensuring that multicast packets are correctly routed and addressed, enhancing network efficiency and security.
Smart Images

Figure 2024542020000001_ABST
Abstract
Description
[Technical field]
[0001] The present specification relates generally to data networks, and more particularly to multicast communications in a containerized environment. [Background technology]
[0002] It is often desirable to send multicast traffic within a network, so that the traffic can reach multiple members of a multicast group and be processed in different ways. This occurs frequently in video processing applications, where cameras publish video traffic to a multicast group and hosts join the multicast group to access the video traffic.
[0003] For efficiency and security reasons, it is often desirable to implement a containerized environment: containers essentially isolate applications from each other, with all communication with the outside world happening through a common network bridge.
[0004] However, there is currently an issue with multicast traffic arriving and departing from applications running in containers when a network bridge is in use, because the network bridge hides the container from the network and there is no convenient way to associate a multicast group with a particular application. Summary of the Invention
[0005] According to a first broad aspect, there is provided a method executed by a processor of a host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the method including obtaining an indication of a request for the container to join a multicast group having a multicast group address, transmitting a request for the host network element to join the multicast group having the multicast group address via the external interface in response to the obtaining, modifying the routing table to make the bridge a next hop for future packets obtained from the external interface and destined for the multicast group address, and setting an increase in a time-to-live parameter for such future packets.
[0006] According to another broad aspect, a non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, and execution of the instructions by the processor causes the host network element to perform the aforementioned method.
[0007] According to another broad aspect, there is provided a method executed by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory, and implementing a container connected to a bridge, the container being addressable by an internal address on a bridge network associated with the bridge. Execution of instructions by the processor causes the host network element to perform the aforementioned method.
[0008] According to another broad aspect, there is provided a method executed by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the container being addressable by an internal address on a bridged network associated with the bridge. The method includes modifying the routing table to make the external interface a next hop for future packets obtained from the bridge and having a source address that is an internal address of the container and that are destined for a multicast group. The method also includes setting an increase in a time-to-live parameter for such future packets. The method further includes setting an address change that replaces a source address of such future packets with an external address of the host network element.
[0009] According to another broad aspect, there is provided a host network element for use in a packet-based data network, the host network element including a processor, a memory operatively coupled to the processor, and an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network, the memory storing an external address by which the host network element is addressable on the packet-based data network, the memory further storing a routing table and non-transitory computer readable instructions, the processor configured to implement a container, a bridge, and a bridge network, the container being further addressable on the bridge network by an internal address, and the processor configured to execute the instructions to thereby perform the method described above.
[0010] According to another broad aspect, a non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the container being addressable on a bridge network associated with the bridge by an internal address, and execution of the instructions by the processor causes the host network element to perform the aforementioned method.
[0011] According to another broad aspect, there is provided a method executed by a processor of a host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the host implementing an internal interface for connecting to the bridge. The method includes obtaining a packet from the external interface having a destination address that is a multicast group address. The method also includes increasing a time-to-live parameter of the packet. The method further includes consulting the routing table to identify the internal interface as a next hop for the packet. The method also includes sending the packet to the bridge via the internal interface.
[0012] According to another broad aspect, there is provided a host network element for use in a packet-based data network, the host network element including a processor, a memory operatively coupled to the processor, an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network, the memory storing routing tables and non-transitory computer readable instructions, the processor configured to implement a container, a bridge, and an internal interface for connecting to the bridge, the processor further configured to execute the instructions to thereby perform the method described above.
[0013] According to another broad aspect, a non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the host implementing an internal interface for connecting to the bridge, and execution of the instructions by the processor causes the host network element to perform the aforementioned method.
[0014] According to another broad aspect, there is provided a method executed by a processor of a host network element in a packet-based environment, where each packet has a source address and a destination address, and where the host network element has an external interface for connecting to at least one other network element of a packet-based data network. The method includes implementing a container, a bridge, and a bridge network, where the container is addressable on the bridge network by an internal address. The method also includes implementing a routing process separated from the container by the bridge. The routing process itself includes obtaining a packet from the bridge, the packet having an internal address of the container on the bridge network as its source address and having a multicast group address as its destination address, increasing a time-to-live parameter of the packet, identifying an external interface of the host network element as the next hop of the packet, replacing the source address of the packet with an address of the host network element, and sending the packet out from the host network element via the external interface.
[0015] According to another broad aspect, there is provided a host network element for use in a packet-based data network, the host network element including a processor, a memory operatively coupled to the processor for storing non-transitory computer readable instructions, and an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network, the processor configured to execute the instructions to thereby perform the method described above.
[0016] According to another broad aspect, a non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, and execution of the instructions by the processor causes the host network element to perform the aforementioned method.
[0017] According to a further broad aspect, a method is provided that is executed by a processor of a host network element in a packet-based environment, the host network element implementing a container and a container engine, the container being addressable by an internal address used by the container engine. The method includes obtaining a packet having a source address, a destination address, and a time-to-live parameter, and based on attributes of the packet, the packet is modified and transmitted to an internal interface or an external interface of the host network element. It is noted that if the packet is obtained from the internal interface, the source address of the packet is an internal address of the container, and the destination of the packet is a multicast group address, then (i) said modification increases the time-to-live parameter of the packet and sets the source address of the packet to an address of the host, and (ii) said transmission transmits the modified packet to the external interface of the host network element.
[0018] According to another broad aspect, there is provided a host network element for use in a packet-based data network, the host network element including a processor, a memory operatively coupled to the processor storing non-transitory computer readable instructions, an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network, the processor configured to implement a container with an internal interface and a container engine, the container being addressable by an internal address stored in the memory, and the processor further configured to execute the instructions to thereby perform the aforementioned method.
[0019] According to another broad aspect, a non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element in a packet-based environment, the host network element implementing a container and a container engine, the container being addressable by an internal address used by the container engine, and execution of the instructions by the processor causing the host network element to perform the aforementioned method.
[0020] The above aspects will now be explained in more detail with reference to the accompanying drawings. [Brief description of the drawings]
[0021] [Figure 1] 1 is a block diagram of a data network including multiple network devices, including a host, according to a non-limiting embodiment. [Diagram 2] 1 shows an example of an IP packet with a header and a payload. [Diagram 3] FIG. 2 is a block diagram of host-implemented processes and data structures, including a routing process, a routing control process, a bridge, and multiple containers, in accordance with a non-limiting embodiment. [Figure 4]6 is a flow chart illustrating a sequence of actions performed by a routing control process in response to notification of a container's request to join a multicast group, according to a non-limiting embodiment. [Diagram 5] 4 is a flow chart illustrating actions performed by a routing process to process an IP packet received via an external interface and destined for a particular multicast group, according to a non-limiting embodiment. [Figure 6] 11 is a flowchart illustrating actions performed by a routing process to process a container-issued IP packet obtained through a bridge, according to a non-limiting embodiment. [Figure 7] FIG. 2 is a block diagram illustrating various elements of a computing device, according to a non-limiting embodiment. [Figure 8] 1 illustrates an example of a routing table, according to a non-limiting embodiment. [Figure 9] 4 is a flowchart illustrating actions performed by a routing control process in accordance with various non-limiting embodiments. [Figure 10] 4 is a flowchart illustrating actions performed by a routing control process in accordance with various non-limiting embodiments. [Figure 11] 4 is a flowchart illustrating actions performed by a routing process, according to various non-limiting embodiments. [Figure 12] 4 is a flowchart illustrating actions performed by a routing process, according to various non-limiting embodiments. [Figure 13] 4 is a flowchart illustrating actions performed by a routing process, according to various non-limiting embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0022] The drawings are to be considered non-limiting.
[0023] 1, a network architecture is shown in which multiple network devices 12 are interconnected as part of a data network 10. The data network 10 may be a local area network (LAN), a wide area network (WAN), a campus area network (CAN), the public Internet, etc. The data network 10 may be connected to at least one other network 20 through one or more of the network devices 12.
[0024] The network devices 12 include various end nodes 14 and host network elements 16 (or simply "hosts"). The end nodes 14 may be sources or consumers of data traffic. In one non-limiting embodiment, the end nodes 14 may be security cameras transmitting video data over a secure link. In another non-limiting embodiment, the end nodes 14 may be web servers streaming digital music, gaming data, or rendering instructions over the Internet. Additional network elements (e.g., servers, switches, edge devices, routers, mobile devices, etc.) may also be part of the network architecture. For example, a router 18 may be located between the end nodes 14 and the hosts 16. The links interconnecting the various network devices 12 may be wired or wireless.
[0025] The host 16 is used to process some of the data traffic sent by the end nodes 14 (and arriving via the router 18) and may also be used to send data traffic to other network devices (also via the router 18). In a non-limiting implementation, from a hardware perspective, and with reference to Figure 7, the host 16 includes a processor 702, a memory 704, and a network interface 706, all of which may be interconnected via an internal bus 708. The memory 704 stores computer readable instructions that are read and executed by the processor 702 to perform various processes, as described below. The memory 704 also stores data structures (e.g., tables, databases, etc.) for use in such processes, as described below.
[0026] Some of the network devices 12 (e.g., end nodes 14, hosts 16, routers 18) have Internet Protocol (IP) addresses that may be statically or dynamically assigned. Such IP addresses are used to communicate data traffic via IP packets, examples of which include IPv4 packets (see RFC 790, incorporated herein by reference) and IPv6 packets (see RFC 2460 and RFC 8200, incorporated herein by reference). Referring to FIG. 2, an example IP packet 202 is shown that includes a header 204 and a payload 206. The header 204 includes a source address 208 (the IP address of the device from which the packet is sent), a destination address 210 (another IP address), an expiration parameter (EXP) 212, and other information 214. The expiration parameter 212 is called the time to live (TTL) in IPv4 and the hop limit in IPv6. The payload 206 includes the data traffic of interest (e.g., video data, streaming digital music, game data, images, rendering instructions, documents, autodiscovery messages, etc.).
[0027] The expiration parameter 212 refers to a mechanism that limits the number of times a packet can be retransmitted on the data network 10. The expiration parameter 212 may be implemented as a counter attached or embedded in the header 204 of the IP packet 202. When a defined event count occurs for the IP packet 202, the data traffic (held in the payload 206 of the IP packet) is either discarded or revalidated.
[0028] 3, a functional block diagram of various processes and data structures implemented by a processor of a host is shown according to a non-limiting embodiment. The processes include a routing process 302, a routing control process 304, and a containerized environment.
[0029] The containerized environment includes multiple containers 308 and a container engine 309. The various containers 308 run any number of applications, which may include applications for consuming and / or generating IP packets. A container is a unit of software that packages code and its dependencies, thereby ensuring that the application runs regardless of the underlying computing platform / native operating system. In particular, the container engine 309 is configured to unpack various files and metadata required for a given container and pass them to the kernel (described below). The container engine 309 may implement a bridge network 314 and a (software) bridge 316. Each container 308 has an internal address on the bridge network 314 that the bridge 316 knows about, which may be a MAC address, for example. The bridge network 314 uses the bridge 316 to allow containers connected to the same bridge network (i.e., container 308) to communicate and isolate them from containers not connected to the bridge network 314 (such containers are not shown in FIG. 3). Thus, containers 308 are isolated from the routing process 302 and each container 308 is reachable from the routing process 302 based on rules inserted into the routing process 302 by the container engine 309 (particularly bridge 316). A non-limiting example of a suitable container engine is Docker, available from Docker, Inc., 3790 El Camino Real #1052, Palo Alto, California, 94306. Other examples of container engines include CRI-O, Railcar, RKT, Podman, and LXC, although these examples should not be construed as limiting.
[0030] In the illustrated non-limiting embodiment, multiple interfaces are also provided to which the routing process 302 is connected. In this case, an external interface 320 connects the routing process 302 to the router 18, and an internal interface 330 connects the routing process 302 to the bridge 316. Each of the external and internal interfaces 320 and 330 is associated with a respective IP address known to the routing process 302. Other external and internal interfaces 340 may also be provided. The routing process 302 (which may be implemented as part of the host's operating system, or "kernel") is configured to process IP packets obtained / received via the internal and external interfaces 320, 330, 340. In particular, the routine process may be configured to process the obtained / received packet, possibly modify it, and possibly output it via one or more of the external and / or internal interfaces 320, 330, 340.
[0031] The routing process 302 accesses various data structures in memory to perform its functions. Such data structures may include a routing table 350, a list (called a "TTL increment list") 360, and a rules database 370. These will now be described in detail, with the understanding that "table," "list," and "database" are expressions that refer to non-limiting examples of data structures, and of course equivalent ways of representing data may be used.
[0032] 8, routing table 350 is a data structure that provides the identity of an interface ("next hop" 358) to which an IP packet, obtained through a particular interface ("previous hop" 352) and having a particular source IP address 354 and destination IP address 356, should be routed. Each of previous hop 352 and next hop 358 may be an internal interface (such as internal interface 330 leading to bridge 316) or an external interface (such as external interface 320 leading to network interface 706). Next hop 358 may also include multiple interfaces (internal and / or external) to send IP packets under certain conditions.
[0033] A distinction can be made between "unicast" routing tables (used for routing one-to-one traffic) and "multicast" routing tables (used for routing one-to-many, or multicast, traffic). Multicast traffic can be considered as data traffic consisting of IP packets whose destination IP address is not the IP address of a specific network device, but rather identifies a "multicast group" known to the interested receivers of the data traffic, of which there may be many at various points in the network. Thus, one way in which a multicast routing table differs from a unicast routing table is that multiple interfaces may be specified as the next hop.
[0034] In light of the above, one of the functions performed by the routing process 302 is to process IP packets obtained from outside the host (e.g., those received / obtained at the external interface 320, so-called "inbound" IP packets) or from one of the containers 308 (e.g., those received / obtained at the internal interface 330 from the bridge 316, so-called "container-issued" IP packets) by checking an appropriate routing table (unicast or multicast) to determine the next hop (e.g., the external interface or internal interface(s)) to which the IP packet needs to be sent, and then send the IP packet to the next hop.
[0035] Another function performed by the routing process 302 includes modifying the expiration parameters (e.g., time to live (TTL) or hop limit) of IP packets. In some embodiments, as described below, the expiration parameter 212 of an IP packet 202 should be incremented if the IP packet 202 is a multicast packet whose multicast group address is on a list of multicast group addresses called the "TTL increment list" 360. Adding (or deleting) a particular multicast group address to (or from) the TTL increment list 360 is performed by the routing control process 304.
[0036] We now turn to rules database 370. This data structure contains a set of rules that routing process 302 must follow when routing incoming and outgoing data traffic. The set of rules may include rules for modifying the source or destination IP addresses of an IP packet before sending the IP packet to an internal or external interface. In a Linux environment, the rules encoded by rules database 370 may be referred to as "iptables rules." An example of an iptables rule may be a rule that the source IP address of an IP packet should be set to the IP address of host 16 before sending the IP packet to external interface 320. Creation or deletion of individual rules in rules database 370 is accomplished by routing control process 304.
[0037] By performing the above functions, such as adding (or deleting) a multicast group address to TTL increment list 360 or creating or deleting rules in rule database 370, routing control process 304 (which may also be referred to as a routing "daemon") makes changes to memory 704 and alters the results of routing process 302. Additionally, routing control process 304 may be configured to instruct routing process 302 to send control messages 390 to router 18 (e.g., via external interface 320) and to container 308 (e.g., via internal interface 330 and bridge 316).
[0038] According to a particular non-limiting embodiment, a particular container 308P may wish to join a particular multicast group. That is, a particular container 308P may wish to be a recipient of IP packets having the address of a particular multicast group as the destination IP address. The address of the particular multicast group (i.e., the particular multicast group address) may be made known / known to the host 16 in a variety of ways, including an online resource, an industry-wide manufacturer code, or user input. Thus, referring to FIG. 4, a particular container 308P may issue a multicast join request 402 requesting that the container join a multicast group having the particular multicast group address.
[0039] In a non-limiting embodiment applicable to IPv4-based networks, sending a multicast join request 402 may require a particular container 308 to send (via bridge 316) a so-called "IGMP request" to the routing process 302. An IGMP request is a message that conforms to the Internet Group Membership Protocol (described in RFCs 1112, 2236, 3376, and 4604, which are incorporated herein by reference) and specifies the IP address of the requester and the multicast group that the requester wishes to join (i.e., identifies the multicast group address for which the requester will receive multicast packets).
[0040] It should be understood that a similar situation and similar message exchanges are applicable to IPv6-based networks, and that instead of implementing IGMP, various network entities can implement the Multicast Listener Discovery (MLD) protocol, which is described in RFCs 2710, 3590, and 3810, and which are incorporated herein by reference.
[0041] Now suppose a multicast join request 402 (e.g., an IGMP request or an MLD request) is issued by a particular container 308P, and the multicast join request indicates a particular multicast group address (denoted by "MG") that the particular container 308P wants to listen to. This may be a multicast group address that is known (by the particular container 308P) to be used by a given end node.
[0042] Upon receiving a multicast join request 402 (which may be an IGMP request in the case of an IPv4-based network, or an MLD request in the case of an IPv6-based network) from a particular container 308P (through the bridge 316), the routing process 302 issues a notification 404 to the routing control process 304. The notification 404 may be delivered as a software parameter change. According to a particular embodiment to be described, the routing control process 304 is carefully designed to respond to such notifications.
[0043] A routing control process that responds to container-issued requests to join multicast groups. 4, there is shown a series of actions taken by the routing control process 304 in response to being notified of a multicast join request 402 by the routing process 302. These actions do not have to be performed in the order described.
[0044] In block 410, the routing control process 304 adds the particular multicast group address MG to the TTL increment list 360 (ie, the list of multicast group addresses for which the routing process 302 should increment the time-to-live parameter).
[0045] In block 420, the routing control process 304 edits / modifies the multicast routing table 350 to add an entry to reflect the situation where, for an inbound IP packet received / obtained from the router 18 (i.e., previous hop 352 is the external interface 320) having the particular multicast group address MG as its destination IP address 356, the next hop 358 is set to the internal interface 330 (leading to the bridge 316). The routing control process 304 also edits the multicast routing table 350 to reflect the situation where, for a container-issued IP packet obtained from the bridge 316 (i.e., previous hop 352 is the internal interface 330) having the particular multicast group address MG as its destination IP address 356, the next hop 358 is set to the external interface 320 (leading to the router 18).
[0046] In block 430, the routing control process 304 edits / modifies the rules database 370. Specifically, the routing control process 304 establishes an "iptables rule" such that for future container-issued IP packets having the particular container's internal IP address as the source IP address and the particular multicast group address MG as the destination IP address, the routing process 302 replaces the packet's source IP address with the IP address of the host 16 (this can be referred to as "masquerading").
[0047] The routing control process 304 then sends a message 406 to the routing process 302, causing the routing process 302 to send a new multicast join request 408. This new multicast join request 308 is sent to the router 18, indicating that the host 16 wishes to join the multicast group associated with the particular multicast group address MG. The new multicast join request 408 conforms to the IGMP protocol (for IPv4) or the MLD protocol (for IPv6), originates from the host, and can include the particular multicast group address MG. The message can be sent as a parameter change in the software.
[0048] The routing process that responds to inbound IP packets that contain data traffic 5, the actions performed by routing process 302 to process a subsequently obtained inbound IP packet (i.e., a packet received from external interface 320) whose destination IP address is a particular multicast group address MG will now be described. These actions need not be performed in the order described.
[0049] In block 510, the routing process checks the TTL increment list 360 and increments the expiration parameter of the IP packet 502 if the destination IP address is on the TTL increment list 360. In this example, because the particular multicast group address MG is deemed to be on the TTL list 360 (as discussed above), the routing process 302 increments (e.g., increments) the expiration parameter (e.g., time to live or hop limit) of the IP packet 502 by modifying data in the header.
[0050] In block 520, the routing process 302 consults the multicast routing table 350 to identify the next hop. In this case, based on the particular multicast group address MG (and the fact that the IP packet 502 was obtained from the external interface 320), the next hop is identified to be the internal interface 330 that leads to the bridge 316.
[0051] In block 530, the routing process 302 sends the IP packet 502 to the next hop, which in this case is the bridge 316, reachable via an internal interface 330.
[0052] The bridge 316 knows that the particular container 308B has expressed an interest in joining a particular multicast group because, as described above, the bridge 316 previously received a multicast join request 402 from the particular container and relayed it to the routing process 302. Thus, when the bridge 316 obtains the aforementioned IP packet 502 from the routing process 302 (as a result of block 530), the bridge 316 determines from the information in the header of the IP packet 502 (which may include the particular multicast group address MG) that the IP packet 502 should be sent to the particular container 308P. Thus, the IP packet 502 is delivered to the particular container 308P at its internal address on the bridge network 314 (e.g., its MAC address or other layer 2 address known to the bridge 316), and once received at the particular container 308P, the IP packet 502 is processed according to the associated application.
[0053] A routing process that responds to container-issued IP packets containing data traffic It is also assumed that a particular container 308P may issue an IP packet belonging to a given multicast group identified by a new multicast group address NG. (The new multicast group address NG is assumed to already be in the TTL increment list 360.) Such a container-issued IP packet has as a source IP address the internal IP address of the particular container 308P and as a destination IP address the new multicast group address NG. With reference to FIG. 6, such a container-issued packet 602 is received / obtained by the routing process 302 via an internal interface 330 connected to the bridge 316 that connects to the particular container 308P. The actions performed by the routing process 302 in such a situation are described with continued reference to FIG. 6. These actions do not have to be performed in the order described.
[0054] In block 610, the routing process 302 checks the TTL increment list 360 and increments the expiration parameter of the retrieved IP packet 602 if the destination IP address is on the TTL increment list 360. In this case, because the retrieved packet 602 is destined for the new multicast group address NG (and, as discussed above, the new multicast group address NG is already on the TTL increment list 360), the expiration parameter of the retrieved IP packet 602 is modified (e.g., increased or incremented) accordingly.
[0055] In block 620, the routing process 302 refers to the multicast routing table 350 to identify the next hop. In this case, based on the fact that the destination IP address of the retrieved IP packet 602 is the new multicast group address NG (and based on the fact that the IP packet 602 was retrieved via the internal interface 330), the next hop is identified to be the external interface 320, i.e., it is determined that the retrieved IP packet 602 should be sent via the external interface 330 connected to the router 18.
[0056] Before doing so, however, in block 630, routing process 302 replaces the source IP address of the obtained IP packet 602 with the external IP address of host 16 (which may be referred to as "masquerading"), resulting in modified IP packet 604.
[0057] At block 640 , the routing process then transmits the modified IP packet 604 to the router 18 via the external interface 320 .
[0058] The modified IP packet 604 reaches the router 18 and is routed according to the router 18's own multicast routing table, just as if there had been no intervention by the host 16 .
[0059] In summary, with reference to FIG. 9 , a method 900 is described that is executed by a processor of a host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge.
[0060] At step 910 of method 900, an indication is obtained requesting that a container join a multicast group having a multicast group address.
[0061] At step 920 of method 900, in response to the acquisition, a request is sent over an external interface for the host network element to join a multicast group having the multicast group address.
[0062] In step 930 of method 900, routing tables are modified to make the bridge the next hop for future packets received from an external interface and destined for a multicast group address.
[0063] In step 940 of method 900, an increase in the expiration parameter is set for such future packets.
[0064] Referring to FIG. 10, a method 1000 executed by a processor of a host network element is described, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory, and implementing a container connected to a bridge, the container being addressable by an internal address on a bridge network associated with the bridge.
[0065] In step 1010 of method 1000, the routing table is modified so that the external interface is taken from the bridge and becomes the next hop for future packets whose source address is an internal address of the container and is destined for the multicast group.
[0066] In step 1020 of method 1000, an increase in the expiration parameter is set for such future packets.
[0067] At step 1030 of method 1000, an address change is configured, which replaces the source address of such future packets with the external address of the host network element.
[0068] Referring to FIG. 11 , a method 1100 is described that is executed by a processor of a host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in memory and implementing a container connected to a bridge, and the host implementing an internal interface for connecting to the bridge.
[0069] In step 1110 of the method 1100, a packet having a destination address that is a multicast group address is obtained from an external interface.
[0070] In a step 1120 of the method 1100, the time-to-live parameter of the packet is incremented.
[0071] A step 1130 of the method 1100 involves consulting a routing table to identify an internal interface as the next hop for the packet.
[0072] In a step 1140 of the method 1100, the packet is sent to the bridge via an internal interface.
[0073] Referring to FIG. 12, a method 1200 is described that is performed by a processor of a host network element in a packet-based environment, where each packet has a source address and a destination address, and where the host network element has an external interface for connecting to at least one other network element of a packet-based data network.
[0074] At step 1210 of the method 1200, a container, a bridge, and a bridge network are implemented, where the container is addressable on the bridge network by an internal address.
[0075] At step 1220 of the method 1200, a routing process is implemented that is separated from the container by the bridge.
[0076] The routing process itself involves several steps:
[0077] In step 1222, this causes a packet to be picked up from the bridge, the packet having as its source address the internal address of the container on the bridge network and as its destination address the multicast group address.
[0078] This causes the expiration parameter of the packet to be incremented in step 1224 .
[0079] In step 1226, an external interface of the host network element is identified as the next hop for the packet.
[0080] This causes the source address of the packet to be replaced with the address of the host network element, step 1228 .
[0081] This causes the packet to be transmitted out from the host network element via the external interface, step 1230 . Finally, referring to FIG. 13, which is a variation of FIG. 12, a method 1300 is described that is performed by a processor of a host network element in a packet-based environment, where the host network element implements a container and a bridge network, where the container is addressable by an internal address on the bridge network.
[0082] At step 1310 of the method 1300, a packet having a source address, a destination address, and a time to live parameter is obtained.
[0083] In step 1320 of method 1300, the packet is modified based on the attributes of the packet and sent to an internal or external interface of the host network element. Note that if the packet is received / obtained from an internal interface, the source address of the packet is an internal address of the container, and the destination of the packet is a multicast group address, then (i) said modification causes the packet's time to live parameter to be increased and the source address of the packet to be set to the address of the host, and (ii) said transmission causes the modified packet to be sent to the external interface of the host network element.
[0084] The above computer-readable storage medium may be a tangible device capable of holding and storing instructions in a non-transitory form for use by an instruction execution device such as a processor. The computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples of computer-readable storage media include, but are not limited to, portable computer diskettes, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), static random access memories (SRAMs), portable compact disk read-only memories (CD-ROMs), digital versatile disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures with instructions stored in grooves, and any suitable combination of the foregoing.
[0085] The computer readable program instructions described herein may be downloaded from such computer readable storage media into the respective computing / processing device or may be downloaded to an external computer or storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical fiber transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives / obtains the computer readable program instructions from the network and transfers the computer readable program instructions for storage in the computer readable storage media in the respective computing / processing device.
[0086] The computer readable program instructions for performing the operations of the present disclosure may be either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including object oriented programming languages such as Smalltalk, C++, and traditional procedural programming languages such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the host, or may be executed partially on the host and partially on a remote computer. In the latter scenario, the remote computer may be connected to the host through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, an electronic circuit, including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may execute the computer readable program instructions and perform aspects of the present disclosure by utilizing state information of the computer readable program instructions to personalize the electronic circuit.
[0087] Aspects of the present disclosure are described herein with reference to flowchart / signal flow diagrams and / or block diagrams of methods, apparatus (systems), and computer program products according to various embodiments. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.
[0088] These computer readable program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to manufacture a machine, such that the instructions executing via the processor of the computer or other programmable data processing apparatus create means for performing the functions / acts specified in the flowchart and / or block diagram of the block or blocks. These computer readable program instructions may also be stored on a computer readable storage medium capable of instructing a computer, programmable data processing apparatus, and / or other device to function in a particular manner, such that the computer readable storage medium having stored thereon instructions includes an article of manufacture including instructions implementing aspects of the functions / acts specified in the flowchart and / or block diagram of the block or blocks.
[0089] The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to create a computer-implemented process that causes the computer, other programmable apparatus, or other device to execute a series of operational steps such that the instructions executing on the computer, other programmable apparatus, or other device perform the functions / acts specified in the flowcharts and / or block diagrams of a block or blocks.
[0090] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, apparatus, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or part of instructions that includes one or more executable instructions for implementing a specified logical function(s). In some alternative implementations, the functions described in the blocks may occur out of the order described in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart diagrams, as well as combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or acts, or performs a combination of dedicated hardware and computer instructions.
[0091] The description of various embodiments of the present disclosure is presented for illustrative purposes and is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terms used in this specification are selected to best explain the principles of the embodiments, practical applications or technical improvements to the technology found in the market, or to enable those skilled in the art to understand the embodiments disclosed herein.
[0092] It should be understood that throughout this specification, discussions using terms such as "processing," "computing," "calculating," "determining," "analyzing," and the like may refer to operations and / or processes of a computer or computing system, or similar electronic computing device, that manipulates and / or transforms data represented as physical quantities, such as electronic quantities, into other data also represented as physical quantities.
[0093] References throughout this specification to "one embodiment," "an exemplary embodiment," or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Thus, the use of the phrases "in one embodiment," "in an exemplary embodiment," or "in an embodiment" in various places throughout this specification do not necessarily all refer to the same embodiment, although in some cases they may. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner apparent to one of ordinary skill in the art in one or more embodiments. Similarly, in the description of the example embodiments above, it should be understood that various features may be grouped together in an embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various aspects. However, this method of disclosure should not be interpreted as reflecting an intention requiring more features than are expressly recited in each claim. Rather, as the following claims reflect, aspects reside in less than all features of a single foregoing disclosed embodiment. As such, the claims following the Detailed Description are expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment. Furthermore, while some embodiments described herein include some features but not other features included in other embodiments, combinations of features from different embodiments are intended to form different embodiments, as would be understood by one of ordinary skill in the art and are within the scope of the present disclosure.
[0094] As used herein, unless otherwise indicated, the use of ordinal adjectives such as "first," "second," "third," etc. to describe a common object or step is intended merely to indicate that different instances of a similar object or step are being referred to and does not imply that the objects or steps so described must be in a given order in time, space, precedence, or otherwise.
[0095] It should be noted that various individual features may be described in only one exemplary embodiment herein. A particular selection to describe in relation to a single exemplary embodiment herein should not be construed as a limitation that a particular feature is applicable only to the embodiment in which it is described. All features described in this specification are equally applicable, additional, or interchangeable to any or all of the other exemplary embodiments described herein, and may be applied in any combination, grouping, or arrangement. In particular, the use of a single reference number herein to illustrate, define, or describe a particular feature does not imply that the feature cannot be associated with or considered equivalent to another feature in another drawing or description. Furthermore, if more than one reference number is used in a figure or drawing, this should not be construed as being limited to only those embodiments or features, but may be equally applicable to similar features, in which case no reference number is used or another reference number is omitted.
[0096] Also, when the phrase "at least one of A and B" is used, the phrase is intended and defined as selecting either A or B, or both A and B, and is similar to the word "and / or." When there are more than one variable in such a phrase, the phrase is defined as including only one of the variables, any one of the variables, any combination of any of the variables, and all of the variables.
[0097] The foregoing description and accompanying drawings illustrate the principles and modes of operation of certain embodiments. However, these embodiments should not be considered limiting. Further variations of the above-described embodiments will be apparent to those skilled in the art, and the above-described embodiments should be considered illustrative, rather than limiting. It should therefore be understood that those skilled in the art can make changes to these embodiments without departing from the scope of the invention as defined by the following claims.
Claims
1. 1. A method executed by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the method comprising: obtaining an indication of a request for the container to join a multicast group having a multicast group address; in response to said obtaining, sending via said external interface a request for said host network element to join said multicast group having said multicast group address; modifying the routing table to make the bridge the next hop for future packets received from the external interface and destined for the multicast group address; setting an increase in a time-to-live parameter of said future packets; The method comprising:
2. The method of claim 1 , wherein the bridge isolates the container from other host functions.
3. The method of claim 2 , wherein the other host function comprises a routing function that uses the routing table to route the future packets.
4. 4. The method of claim 3, wherein the bridge is implemented by a container engine, the container engine further implementing a bridge network that connects the container to other containers while being isolated from the other host functions.
5. 2. The method of claim 1, wherein the host network element is addressable by an IP address from outside the host network element, and the request for the host network element to join the multicast group includes a multicast join request message that identifies the IP address of the host.
6. 6. The method of claim 5, wherein the multicast join request is an IGMP request if the IP address is an IPv4 address or an MLD request if the IP address is an IPv6 address.
7. 2. The method of claim 1, wherein the host network element is connected via the external interface to a router, the router being addressable by an address on the packet-based data network, and the request for the host network element to join the multicast group is embedded in a packet having the address of the router as its destination address.
8. 8. The method of claim 7, wherein the host network element is addressable on the packet-based data network by an external address, and the packet identifies the external address of the host.
9. The method of claim 1 , wherein the host network element implements a kernel, and the indication of the request for the container to join the multicast group comprises a notification message from the kernel.
10. 10. The method of claim 9, further comprising the kernel obtaining the request for the container to join the multicast group via the container engine.
11. The method of claim 10 , wherein the request for the container to join the multicast group comprises an IGMP request message or an MLD request message issued by the given container.
12. 2. The method of claim 1, wherein setting the increase in the expiration parameter comprises adding the multicast group address to a list stored in the memory.
13. 13. The method of claim 12, wherein the host network element implements a routing process, the routing process including consulting the list and incrementing the expiration parameter of an IP packet obtained from the external interface if the destination address of the obtained IP packet is on the list.
14. The method of claim 13 , wherein the increasing comprises incrementing.
15. 2. The method of claim 1, further comprising modifying the routing table such that the container is addressable by an internal address on a bridged network associated with the bridge, and making the external interface the next hop for a second future packet obtained from the bridge whose source address is the internal address of the container.
16. 16. The method of claim 15, further comprising setting an increase in an expiration parameter for the second future packet as well.
17. 17. The method of claim 16, wherein the host network element implements a routing process that consults the list and increments the expiration parameter of an IP packet retrieved from the container engine if a destination address of the retrieved IP packet is on the list.
18. The method of claim 17 , wherein the increasing comprises incrementing.
19. 17. The method of claim 16, wherein the host network element is addressable by a network element other than the host network element by an external address, further comprising setting an address change to set the source address of the second future packet to be the external address of the host network element.
20. A host network element for use in a packet-based data network, comprising: A processor; a memory operatively coupled to the processor; an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network; Including, the memory stores a routing table and non-transitory computer readable instructions; The processor is configured to implement a container and a bridge and is further configured to execute the instructions, thereby providing a method comprising: obtaining an indication of a request for the container to join a multicast group having a multicast group address; in response to said obtaining, sending via said external interface a request for said host network element to join said multicast group having said multicast group address; modifying the routing table to make the bridge the next hop for future packets received from the external interface and destined for the multicast group address; setting an increase in a time-to-live parameter of said future packets; performing the method, The host network element.
21. 1. A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, and execution of the instructions by the processor causes the host network element to perform a method comprising: obtaining an indication of a request for the container to join a multicast group having a multicast group address; in response to said obtaining, sending via said external interface a request for said host network element to join said multicast group having said multicast group address; modifying the routing table to make the bridge the next hop for future packets received from the external interface and destined for the multicast group address; setting an increase in a time-to-live parameter of said future packets; The non-transitory computer-readable medium for performing the method.
22. 1. A method executed by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the container being addressable by an internal address on a bridge network associated with the bridge, the method comprising: modifying the routing table to make the external interface the next hop for future packets obtained from the bridge whose source address is the internal address of the container and which are destined for a multicast group; setting an increase in a time-to-live parameter of said future packets; configuring an address change to replace the source address of the future packets with the external address of the host network element; The method comprising:
23. The method of claim 22 , wherein the bridge isolates the container from other host functions.
24. 24. The method of claim 23, wherein the other host functions include a routing function that uses the routing table.
25. 25. The method of claim 24, wherein the bridge network connects the container to other containers while being isolated from the other host functions.
26. 23. The method of claim 22, wherein the configuring the address change comprises modifying a rules database.
27. 23. The method of claim 22, wherein the configuring the address change includes creating an iptables rule in a rules database.
28. 23. The method of claim 22, wherein the multicast group is associated with a multicast group address, and setting an increase in a time-to-live parameter comprises adding the multicast group address to a list of addresses for which the time-to-live parameter is increased.
29. 29. The method of claim 28, wherein the host network element implements a routing function, the routing function configured to consult the list and to increment the expiration parameter of a packet obtained from the bridge if the destination address of the packet is on the list.
30. 30. The method of claim 29, wherein the packet is an IPv4 packet and the expiration parameter is a time to live, or wherein the packet is an IPv6 packet and the expiration parameter is a hop limit.
31. A host network element for use in a packet-based data network, comprising: A processor; a memory operatively coupled to the processor; an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network; Including, the memory stores an external address by which the host network element is addressable on the packet-based data network, the memory further storing a routing table and non-transitory computer readable instructions; The processor is configured to implement a container, a bridge, and a bridge network, the container being addressable by an internal address on the bridge network, and the processor is further configured to execute the instructions, thereby providing a method comprising: modifying the routing table to make the external interface the next hop for future packets obtained from the bridge whose source address is the internal address of the container and which are destined for a multicast group; setting an increase in a time-to-live parameter of said future packets; configuring an address change to replace the source address of the future packets with the external address of the host network element; performing the method, The host network element.
32. 1. A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element being addressable on the packet-based data network by an external address, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the container being addressable on a bridge network associated with the bridge by an internal address, and execution of the instructions by the processor causes the host network element to perform a method comprising: modifying the routing table to make the external interface the next hop for future packets obtained from the bridge whose source address is the internal address of the container and which are destined for a multicast group; setting an increase in a time-to-live parameter of said future packets; configuring an address change to replace the source address of the future packets with the external address of the host network element; The non-transitory computer-readable medium performing the method, comprising:
33. 1. A method executed by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in a memory and implementing a container connected to a bridge, the host implementing an internal interface for connecting to the bridge, the method comprising: receiving a packet from the external interface having a destination address that is a multicast group address; increasing a time-to-live parameter of said packet; referencing the routing table to identify the internal interface as a next hop for the packet; sending the packet to the bridge via the internal interface; The method comprising:
34. 34. The method of claim 33, further comprising determining whether the multicast group address is on a list of addresses, and wherein the incrementing of the expiration parameter of the packet is performed only if the multicast group address is on the list.
35. 34. The method of claim 33, wherein increasing the expiration parameter of the packet comprises incrementing a time to live of the packet if the packet is an IPv4 packet or increasing a hop limit of the packet if the packet is an IPv6 packet.
36. 34. The method of claim 33, wherein the container is addressable by an internal address on a bridged network associated with the bridge, and the bridge is configured to send the packet to the container via the bridged network using the container's internal address.
37. 34. The method of claim 33, wherein the bridge is configured to receive a prior request from the container to join a multicast group identified by the multicast group address.
38. 37. The method of claim 36, wherein the container is configured to process the packets upon receipt from the bridge.
39. 40. The method of claim 38, wherein the packets include payloads containing video data, and the container executes a video processing application for processing the video data.
40. 34. The method of claim 33, wherein the packets are IP packets and the routing table is a multicast routing table.
41. 34. The method of claim 33, wherein the container is addressable by an internal address on a bridge network associated with the bridge, and further comprising: (i) obtaining a second packet from the container via the bridge, the second packet having the internal address of the container as its source address and a second multicast group address as its destination address; and (ii) consulting the routing table to identify the external interface as a next hop for the second packet based at least in part on the destination address of the second packet being the second multicast group address.
42. 42. The method of claim 41, wherein the internal address is a MAC address.
43. 42. The method of claim 41, further comprising increasing the expiration parameter of the second packet.
44. 44. The method of claim 43, wherein the incrementing of the expiration parameter of the second packet occurs prior to the referencing of the routing table to identify the external interface as a next hop for the second packet.
45. 44. The method of claim 43, wherein the host network element is addressable by a network element other than the host network element by an external address, the method further comprising setting the source address of the second packet to be the external address of the host network element.
46. 46. The method of claim 45, further comprising transmitting the second packet via the external interface.
47. 34. The method of claim 33, wherein the bridge isolates the container from other host functions.
48. 48. The method of claim 47, wherein the other host functions include a routing process that performs the obtaining, looking up, augmenting, and sending.
49. 48. The method of claim 47, wherein the host network element implements other containers, and the bridge is implemented by a container engine, the container engine further implements a bridge network connecting the container to the other containers while being isolated from the other host functions.
50. A host network element for use in a packet-based data network, comprising: A processor; a memory operatively coupled to the processor; an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network; Including, the memory stores a routing table and non-transitory computer readable instructions; The processor is configured to implement a container, a bridge, and an internal interface for connecting to the bridge, the processor is further configured to execute the instructions, thereby providing a method comprising: receiving a packet from the external interface having a destination address that is a multicast group address; increasing a time-to-live parameter of said packet; referencing the routing table to identify the internal interface as a next hop for the packet; sending the packet to the bridge via the internal interface; performing the method, The host network element.
51. 1. A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the host network element storing a routing table in memory and implementing a container connected to a bridge, the host implementing an internal interface for connecting to the bridge, and execution of the instructions by the processor causes the host network element to perform a method comprising: receiving a packet from the external interface having a destination address that is a multicast group address; increasing a time-to-live parameter of said packet; referencing the routing table to identify the internal interface as a next hop for the packet; sending the packet to the bridge via the internal interface; The non-transitory computer-readable medium for performing the method.
52. 1. A method executed by a processor of a host network element in a packet-based environment in which each packet has a source address and a destination address, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, the method comprising: Implementing a container, a bridge, and a bridge network, wherein the container is addressable on the bridge network by an internal address; a routing process separated from the container by the bridge, obtaining a packet from the bridge, the packet having as its source address the internal address of the container on the bridge network and having as its destination address a multicast group address; increasing a time-to-live parameter of said packet; identifying the external interface of the host network element as a next hop for the packet; replacing the source address of the packet with the address of the host network element; transmitting the packet out of the host network element via the external interface; implementing the routing process, The method comprising:
53. 53. The method of claim 52, wherein the host network element implements other containers, and the bridge network connects the container to the other containers while being isolated from the routing process.
54. 53. The method of claim 52, wherein said identifying comprises referencing a routing table stored in a memory.
55. 53. The method of claim 52, wherein increasing the expiration parameter of the packet comprises incrementing a time to live of the packet if the packet is an IPv4 packet or increasing a hop limit of the packet if the packet is an IPv6 packet.
56. 53. The method of claim 52, further comprising consulting a rules database to determine that the source address of the packet should be replaced with the address of the host network element.
57. 57. The method of claim 56, wherein the host network element is addressable on the packet-based data network by an external address, the address of the host network element being the external address.
58. 57. The method of claim 56, wherein the consulting the rules database includes determining iptables rules to be stored in the rules database.
59. 53. The method of claim 52, wherein the internal address is a MAC address.
60. A host network element for use in a packet-based data network, comprising: A processor; a memory operatively coupled to the processor and configured to store non-transitory computer readable instructions; an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network; Including, The processor is configured to execute the instructions, thereby providing a method comprising: Implementing a container, a bridge, and a bridge network, wherein the container is addressable on the bridge network by an internal address; a routing process separated from the container by the bridge, obtaining a packet from the bridge, the packet having as its source address the internal address of the container on the bridge network and having as its destination address a multicast group address; increasing a time-to-live parameter of said packet; identifying the external interface of the host network element as a next hop for the packet; replacing the source address of the packet with the address of the host network element; transmitting the packet out of the host network element via the external interface; implementing the routing process, configured to carry out the method, The host network element.
61. 1. A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element, the host network element having an external interface for connecting to at least one other network element of a packet-based data network, wherein execution of the instructions by the processor causes the host network element to perform a method comprising: Implementing a container, a bridge, and a bridge network, wherein the container is addressable on the bridge network by an internal address; a routing process separated from the container by the bridge, obtaining a packet from the bridge, the packet having as its source address the internal address of the container on the bridge network and having as its destination address a multicast group address; increasing a time-to-live parameter of said packet; identifying the external interface of the host network element as a next hop for the packet; replacing the source address of the packet with the address of the host network element; transmitting the packet out of the host network element via the external interface; implementing the routing process, The non-transitory computer-readable medium causing the method to be performed.
62. 16. A method executed by a processor of a host network element in a packet-based environment, the host network element implementing a container and a container engine, the container being addressable by an internal address used by the container engine, the method comprising: Obtaining a packet having a source address, a destination address, and a time to live parameter; modifying the packet based on an attribute of the packet and sending the modified packet to an internal interface or an external interface of the host network element; Including, if the packet is obtained from the internal interface, and the source address of the packet is the internal address of the container and the destination of the packet is a multicast group address, the modifying includes incrementing the time-to-live parameter of the packet to set the source address of the packet to be the address of the host, and the sending includes sending the modified packet to the external interface of the host network element. The method.
63. A host network element for use in a packet-based data network, comprising: A processor; a memory operatively coupled to the processor and configured to store non-transitory computer readable instructions; an external interface operatively coupled to the processor for connecting to at least one other network element of the packet-based data network; Including, The processor is configured to implement a container with an internal interface and a container engine, the container being addressable by an internal address stored in the memory, and the processor executes the instructions to thereby perform a method comprising: Obtaining a packet having a source address, a destination address, and a time to live parameter; modifying the packet based on an attribute of the packet and transmitting the modified packet to the internal or external interface of the host network element; Including, if the packet is obtained from the internal interface, and the source address of the packet is the internal address of the container and the destination of the packet is a multicast group address, the modifying includes incrementing the time-to-live parameter of the packet to set the source address of the packet to be the address of the host, and the sending includes sending the modified packet to the external interface of the host network element. further configured to perform the method. The host network element.
64. 1. A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of a host network element in a packet-based environment, the host network element implementing a container and a container engine, the container being addressable by an internal address used by the container engine, and execution of the instructions by the processor to provide the host network element with a method, the method comprising: Obtaining a packet having a source address, a destination address, and a time to live parameter; modifying the packet based on an attribute of the packet and transmitting the modified packet to the internal or external interface of the host network element; Including, if the packet is obtained from the internal interface, and the source address of the packet is the internal address of the container and the destination of the packet is a multicast group address, the modifying includes incrementing the time-to-live parameter of the packet to set the source address of the packet to be the address of the host, and the sending includes sending the modified packet to the external interface of the host network element. The non-transitory computer readable medium causing the method to be performed.
Citation Information
Patent Citations
Multicast VPN support in data centers using edge replication tree
US10999195B1
Bit Indexed Explicit Replication For Professional Media Networks
US20150181309A1
Using a central controller cluster to configure a distributed multicast logical router
US20190182061A1
Hardware based packet replication at tail end node
US20200235959A1
