Wap Slb With Radius Static Session Entries - Radware Alteon Application Manual

WAP supports most wireless networks and is supported by all operating systems, with the goal of
inter-operability. A WAP gateway translates Wireless Markup Language (WML) (which is a WAP
version of HTML) into HTML/HTTP so that requests for information can be serviced by traditional Web
servers.
To load balance WAP traffic among available parallel servers, Alteon must provide persistency so
that the clients can always go to the same WAP gateway to perform WAP operation.
Figure 46 - Load Balancing WAP Gateways, page 301
by the remote access server. In this example, the RADIUS servers are integrated with the WAP
gateways:
Figure 46: Load Balancing WAP Gateways
You can configure Alteon to select a WAP gateway for each client request based on one of the
following three methods:
• WAP SLB with RADIUS Static Session Entries, page 301
• WAP SLB with RADIUS Snooping, page 304
• WAP SLB with RADIUS/WAP Persistence, page 306

WAP SLB with RADIUS Static Session Entries

RADIUS, a proposed IETF standard, is a client/server protocol that enables remote access servers to
communicate with a central server to authenticate dial-in users and authorize their access to the
requested network or service. RADIUS allows a company to maintain user profiles in a central
database that all remote servers can share. It provides better security, allowing a company to set up
a policy that can be applied at a single-administered network point.
The RADIUS server uses a static session entry to determine which real WAP gateway should receive
the client sessions. Typically, each WAP gateway is integrated with a RADIUS server on the same
host, and a RADIUS request packet is allowed to go to any of the RADIUS servers. Upon receiving a
Document ID: RDWR-ALOS-V2900_AG1302
Alteon Application Switch Operating System Application Guide
illustrates how the user is first authenticated
Load Balancing Special Services
301