This application discloses example application instance address translation methods. One example method includes receiving, by a control plane device from a mobile edge cloud control device, an address of a target application instance of an application service accessed by a terminal. The control plane device can then send the address of the target application instance to a first user plane device. The control plane device can then instruct the first user plane device to set, as the address of the target application instance, a destination address of an uplink packet that is of the terminal and is associated with the application service.

According to one or more embodiments of this disclosure, a network controller in a data center network establishes a translation table for in-band traffic in a data center network, the translation table resolves ambiguous network addresses based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address. The network controller device receives packets originating from applications and/or an endpoints operating in a network segment associated with a VNID. The network controller device translates, using the translation table, unique loopback addresses and/or routable tenant addresses associated with the packets into routable tenant addresses and/or unique loopback addresses, respectively.

Some embodiments provide a method for a network controller that manages multiple logical networks implemented by multiple managed forwarding elements (MFEs) operating on multiple host machines. The method receives a notification from a particular MFE that an interface corresponding to a logical port of a logical forwarding element has connected to the particular MFE and has a particular logical network address. The method assigns a unique physical network address to the interface. Each of multiple interfaces connected to the particular MFE is assigned a different physical network address. The method provides the assigned unique physical network address to the particular MFE for the particular MFE to convert data messages sent from the particular logical network address to have the unique physical network address.

Some embodiments provide a method for a network controller that manages multiple logical networks implemented by multiple managed forwarding elements (MFEs) operating on multiple host machines. The method receives a notification from a particular MFE that an interface corresponding to a logical port of a logical forwarding element has connected to the particular MFE and has a particular logical network address. The method assigns a unique physical network address to the interface. Each of multiple interfaces connected to the particular MFE is assigned a different physical network address. The method provides the assigned unique physical network address to the particular MFE for the particular MFE to convert data messages sent from the particular logical network address to have the unique physical network address.

Disclosed are an electronic device for wireless communication and a method thereof. The electronic device may include an interface module and a processor. The processor may be configured to establish a first Ethernet tethering connection with an external electronic device by using an Ethernet driver, provide an Internet service to the external electronic device using a first IP address allocated to the external electronic device, deactivate the Ethernet driver in response to identifying that the IP address of the electronic device is changed and the first Ethernet tethering connection is in the bridge mode, reactivate the deactivated Ethernet driver, establish a second Ethernet tethering connection with the external electronic device by using the reactivated Ethernet driver, and provide the Internet service to the external electronic device using a second IP address allocated to the external electronic device.

Disclosed are an electronic device for wireless communication and a method thereof. The electronic device may include an interface module and a processor. The processor may be configured to establish a first Ethernet tethering connection with an external electronic device by using an Ethernet driver, provide an Internet service to the external electronic device using a first IP address allocated to the external electronic device, deactivate the Ethernet driver in response to identifying that the IP address of the electronic device is changed and the first Ethernet tethering connection is in the bridge mode, reactivate the deactivated Ethernet driver, establish a second Ethernet tethering connection with the external electronic device by using the reactivated Ethernet driver, and provide the Internet service to the external electronic device using a second IP address allocated to the external electronic device.

A communication device, in which a protocol is workable, the protocol enabling formation of a redundancy configuration including a plurality of communication devices by use of a virtual IP address, includes: a table storage unit configured to store a table in which, for each of a plurality of destination networks connected to the communication device through a path, the virtual IP address and the destination network are associated with each other; and a control unit configured to identify, in response to detection of a failure in the path connected to one of the destination networks, the virtual IP address associated with the destination network by reference to the table and cause the identified virtual IP address to transition to another communication device, the another communication device forming the redundancy configuration with the communication device.

In general, this disclosure describes a cloud exchange (or “cloud exchange”) that offers a cloud-to-cloud interface (CCI) for interconnecting cloud services to tenants within public clouds. As described herein, the cloud exchange may be configured with a cloud-to-cloud interface that enables tenant applications of a public cloud to subscribe to and communicate with cloud services, using an end-to-end layer 3 path, in some cases without requiring a separate routing protocol session with a public edge device for the public cloud. In some examples, the public cloud provides a virtual layer 2 connection from a tenant within a public cloud to a routing instance of the cloud exchange, and the cloud exchange uses the routing instance to route service traffic between the tenant and the cloud services.

In general, this disclosure describes a cloud exchange (or “cloud exchange”) that offers a cloud-to-cloud interface (CCI) for interconnecting cloud services to tenants within public clouds. As described herein, the cloud exchange may be configured with a cloud-to-cloud interface that enables tenant applications of a public cloud to subscribe to and communicate with cloud services, using an end-to-end layer 3 path, in some cases without requiring a separate routing protocol session with a public edge device for the public cloud. In some examples, the public cloud provides a virtual layer 2 connection from a tenant within a public cloud to a routing instance of the cloud exchange, and the cloud exchange uses the routing instance to route service traffic between the tenant and the cloud services.

A configuration of a cloud application exposed via a public IP address is duplicated with modifications to include a private IP address to expose the application internally. The original configuration is updated so that external network traffic sent to the application is redirected to and distributed across agents running on nodes of a cloud cluster by which web application firewalls (WAFs) are implemented. A set of agents for which the respective WAFs should inspect the redirected network traffic are selected based on cluster metrics, such as network and resource utilization metrics. The redirected network traffic targets a port allocated to the agents that is unique to the application, where ports are allocated on a per-application basis so each of the agents can support WAF protection for multiple applications. Network traffic which a WAF allows to pass is directed from the agent to the application via its private IP address.