Abstract: A method of creating containers in a physical host that includes a managed forwarding element (MFE) configured to forward packets to and from a set of data compute nodes (DCNs) hosted by the physical host. The method creates a container DCN in the host. The container DCN includes a virtual network interface card (VNIC) configured to exchange packets with the MFE. The method creates a plurality of containers in the container DCN. The method, for each container in the container DCN, creates a corresponding port on the MFE. The method sends packets addressed to each of the plurality of containers from the corresponding MFE port to the VNIC of the container DCN.

Abstract: A method of creating containers in a physical host that includes a managed forwarding element (MFE) configured to forward packets to and from a set of data compute nodes (DCNs) hosted by the physical host. The method creates a container DCN in the host. The container DCN includes a virtual network interface card (VNIC) configured to exchange packets with the MFE. The method creates a plurality of containers in the container DCN. The method, for each container in the container DCN, creates a corresponding port on the MFE. The method sends packets addressed to each of the plurality of containers from the corresponding MFE port to the VNIC of the container DCN.

Abstract: A method of creating containers in a physical host that includes a managed forwarding element (MFE) configured to forward packets to and from a set of data compute nodes (DCNs) hosted by the physical host. The method creates a container DCN in the host. The container DCN includes a virtual network interface card (VNIC) configured to exchange packets with the MFE. The method creates a plurality of containers in the container DCN. The method, for each container in the container DCN, creates a corresponding port on the MFE. The method sends packets addressed to each of the plurality of containers from the corresponding MFE port to the VNIC of the container DCN.

Abstract: A method of creating containers in a physical host that includes a managed forwarding element (MFE) configured to forward packets to and from a set of data compute nodes (DCNs) hosted by the physical host. The method creates a container DCN in the host. The container DCN includes a virtual network interface card (VNIC) configured to exchange packets with the MFE. The method creates a plurality of containers in the container DCN. The method, for each container in the container DCN, creates a corresponding port on the MFE. The method sends packets addressed to each of the plurality of containers from the corresponding MFE port to the VNIC of the container DCN.

Abstract: A method of creating containers in a physical host that includes a managed forwarding element (MFE) configured to forward packets to and from a set of data compute nodes (DCNs) hosted by the physical host. The method creates a container DCN in the host. The container DCN includes a virtual network interface card (VNIC) configured to exchange packets with the MFE. The method creates a plurality of containers in the container DCN. The method, for each container in the container DCN, creates a corresponding port on the MFE. The method sends packets addressed to each of the plurality of containers from the corresponding MFE port to the VNIC of the container DCN.

Abstract: A method of communicating packets in a physical host that includes a managed forwarding element (MFE) configured to communicate packets to a set of containers in a data compute node (DCN) hosted by the physical host. The method receives a packet from a particular container in the container DCN. The packet includes a tag that includes an identification of the particular container. The method uses the identification of the particular container included in the tag to identify a port of the MFE that correspond to the particular container. The method removes the tag from the packet. The method forwards the un-tagged packet to the port of the MFE that corresponds to the particular container.

Abstract: Processing a connection request is disclosed. The connection request is received. It is determined whether the connection request identifies a Transport Layer Security (TLS) ticket that identifies a previously load balanced session. In the event it is determined that the TLS ticket identifies the previously load balanced session, (1) the previously load balanced session that corresponds to the connection request is identified, wherein the previously load balanced session is load balanced to a selected server among a plurality of servers, and (2) the connection request is associated with the identified previously load balanced session.

Abstract: A method of communicating packets in a physical host that includes a managed forwarding element (MFE) configured to communicate packets to a set of containers in a data compute node (DCN) hosted by the physical host. The method receives a packet from a particular container in the container DCN. The packet includes a tag that includes an identification of the particular container. The method uses the identification of the particular container included in the tag to identify a port of the MFE that correspond to the particular container. The method removes the tag from the packet. The method forwards the un-tagged packet to the port of the MFE that corresponds to the particular container.

Abstract: Processing a connection request is disclosed. The connection request is received. It is determined whether the connection request identifies a Transport Layer Security (TLS) ticket that identifies a previously load balanced session. In the event it is determined that the TLS ticket identifies the previously load balanced session, (1) the previously load balanced session that corresponds to the connection request is identified, wherein the previously load balanced session is load balanced to a selected server among a plurality of servers, and (2) the connection request is associated with the identified previously load balanced session.

Abstract: Processing a connection request is disclosed. The connection request is received. It is determined whether the connection request identifies a Transport Layer Security (TLS) ticket that identifies a previously load balanced session. In the event it is determined that the TLS ticket identifies the previously load balanced session, (1) the previously load balanced session that corresponds to the connection request is identified, wherein the previously load balanced session is load balanced to a selected server among a plurality of servers, and (2) the connection request is associated with the identified previously load balanced session.

Abstract: An access request is transmitted from a first device to a second device causing one or more security functions to be executed on the first device. Whether to grant the access request is based on a result of the executed one or more security functions.

Abstract: Adaptive failover occurs between a Layer Three (L3) based network tunnel and a Layer Four (L4) based network tunnel. An example of a L4 based network tunnel is a Secure Sockets Layer (SSL) tunnel and an example of a L3 based network tunnel is an Internet Protocol Security (IPSec) tunnel. SSL tunnels work through most firewalls and proxies, but may introduce latency and other performance problems. IPSec tunnels provide a more efficient performance, but may not work through some firewalls and proxies. The techniques include dynamically selecting a tunneling protocol in order to achieve a more efficient network tunnel performance when possible while maintaining consistent L3 connectivity from a variety of remote network environments.

Abstract: An access request is transmitted from a first device to a second device causing one or more security functions to be executed on the first device. Whether to grant the access request is based on a result of the executed one or more security functions.