Abstract: Systems and methods are provided for prevent network outages and improve communication effectiveness by implementing an automatic discovery method that enables the AP to act dynamically to determine its persona as a WAN AP or LAN AP. Based on the determination, the AP can receive the appropriate configuration settings in a configuration file from the central controller (e.g., Aruba central config service) for its dynamic persona. In some examples, the administrator user may define an AP identifier (e.g., MAC addresses) of the network devices in the corresponding microbranch for authentication and authorization.

Abstract: Systems and methods are provided for authenticating client devices in microbranch deployment. In response to a client device connecting to a LAN AP, a first client-entry associated with the client device can be created to indicate that the client device is local to the LAN AP. An authentication request can be transmitted to a WAN AP to be forwarded to an authentication server. A second client-entry associated with the client device at the WAN AP can be created based on the authentication request. Upon successful authentication, the second client-entry can be designated as being foreign to the WAN AP based on the first client-entry being local to the LAN AP. Accordingly, data packets from the client device can be analyzed via a first firewall of the LAN AP, while bypassing a second firewall of the WAN AP based on the foreign designation of the second client-entry at the WAN AP.

Abstract: Systems and methods are provided for prevent network outages and improve communication effectiveness by implementing an automatic discovery method that enables the AP to act dynamically to determine its persona as a WAN AP or LAN AP. Based on the determination, the AP can receive the appropriate configuration settings in a configuration file from the central controller (e.g., Aruba central config service) for its dynamic persona. In some examples, the administrator user may define an AP identifier (e.g., MAC addresses) of the network devices in the corresponding microbranch for authentication and authorization.

Abstract: Network address translation (NAT) flow migration between wireless access points (APs) in a manner that ensures that client devices can seamlessly roam between APs is described. An AP on which a NAT flow is first created is designated as an anchor NAT flow AP for that NAT flow during the lifetime of the NAT flow. When a non-anchor AP to which a client has roamed receives a packet that matches an active NAT flow, the non-anchor AP forwards the packet to the anchor AP for that NAT flow. The roamed AP may consult NAT flow uplink session information to identify the anchor AP as a next hop for the matching packet. Upon receipt, the anchor AP source NATs the packet with its own IP address and routes the packet towards the Internet. Downlink packets that match the NAT flow are routed in a similar manner through the anchor AP.