Specifications
Configuring AAA for Users of Third-Party APs
RoamAbout Mobility System Software Configuration Guide 17-37
Configuring AAA for Users of Third-Party APs
ARoamAboutSwitchcanprovidenetworkaccessforusersassociatedwithathird‐partyAPthat
hasauthenticatedtheuserswithRADIUS.Youcanconnectathird‐partyAPtoaRoamAbout
SwitchandconfiguretheRoamAboutSwitchtoprovideauthorizationforclientswho
authenticateandaccessthenetworkthroughthe
AP.Figure 17‐3showsanexample.
Figure 17-3 RoamAbout Switch Serving as RADIUS Proxy
1. MSSusesMACauthenticationtoauthenticatetheAP.
2. TheusercontactstheAPandnegotiatestheauthenticationprotocoltobeused.
3. TheAP,actingasaRADIUSclient,sendsaRADIUSaccess‐requesttothe RoamAboutSwitch.
Theaccess‐requestincludestheSSID,theuser’s
MACaddress,andtheusername.
4. For802.1Xusers,theAPuses802.1Xtoauthenticatetheuser,usingtheRoamAboutSwitchas
itsRADIUSserver.TheRoamAboutSwitchproxiesRADIUSrequestsfromtheAPtoareal
RADIUSserver,dependingontheauthenticationmethodspecifiedintheproxy
authenticationruleforthe
user.
•Fornon‐802.1Xusers,theAPdoesnotuse802.1X.TheRoamAboutSwitchsendsa
RADIUSqueryforthespecialusernameweb‐portal‐ssidorlast‐resort‐ssid,wheressidis
theSSIDname.Thefallthruauthenticationtype(web‐portalorlast‐resort)specifiedfor
thewiredauthentication
portconnectedtotheAPdetermineswhichusernameisused.
•ForanyusersofanAPthatsendsSSIDtraffictotheRoamAboutSwitchonanuntagged
VLAN,theRoamAboutSwitchdoesnotuse802.1X.TheRoamAboutSwitchsendsa
RADIUSqueryforthespecialusernameweb‐portal‐wiredorlast‐
resort‐wired,
dependingonthefallthruauthenticationtype specifiedforthewiredauthenticationport.
5. AftersuccessfulRADIUSauthentication oftheuser(orspecialusername,fornon‐802.1X
users),MSSassignsauthorizationattributestotheuserfromtheRADIUSserver’saccess‐
acceptresponse.
6. Whentheuser’ssessionends,thethird‐partyAP
sendsaRADIUSstop‐accountingrecordto
theRoamAboutSwitch.TheRoamAboutSwitchthenremovesthesession.
RoamAbout switch
Wired Layer 2
connection
RADIUS server
Layer 2
or Layer 3