Join us at this session to hear from Facebook on how they enabled easy to use, secure remote access solution for thousands of teleworkers. We will discuss how to design wireless access for mobile devices, wired access for VoIP phones - some with 4G cellular data for WAN backup.
To learn more, visit us at http://www.arubanetworks.com/wlan. Join the discussion at https://community.arubanetworks.com
To understand more, let’s take a look at the RAP architecture:On one side, the RAP looks like a VPN client-in-a-box. Plug in to any network, it gets an address, then “dials” up a VPN tunnel to the data center so you don’t have to. VPN-in-a-box is not new – “hard clients” have been around for a while. But they usually stop at a simple connectivity model of attaching one or more wired ports to a VPN tunnel. The RAP is much more than that.On the LAN side that faces the end user, we provide wired and wireless connectivity options. The wireless side delivers the full enterprise-grade security, management, and control that Aruba is known for in its campus WLAN deployments. The wireless also provides full wireless intrusion prevention services to control rogue APs and misconfigured clients.In the middle is the most important part - our “secret sauce” – a technology we call PEF, or policy enforcement firewall. PEF is a technology we developed originally for our wireless LAN platform. It is a per user/device/session state access forwarding engine. What it does is function as a policy enforcement switch, controlling who/what can get in, who can do what, and even controls prioritization. Best of all it does this based on users and dynamic policies versus ports and subnets, thus dramatically simplifying and virtualizing service delivery and security policies to users. PEF is the key feature that makes the RAP different than simple “VPN-in-a-box.”