That service profile does not look at all correct. It's a mixed bag of pre-provisioned services and AAA provisioned services. Here is a sample service definition that works with our ASN-GW: WiMAX-QoS-Id := 101 WiMAX-Service-Class-Name := DATA WiMAX-Schedule-Type := Best-Effort WiMAX-Traffic-Priority := 1 WiMAX-Maximum-Sustained-Traffic-Rate := 512000 WiMAX-Reduced-Resources-Code := 1 WiMAX-QoS-Id += 102 WiMAX-Service-Class-Name += DATA WiMAX-Schedule-Type += Best-Effort WiMAX-Traffic-Priority += 1 WiMAX-Maximum-Sustained-Traffic-Rate += 20971520 WiMAX-Reduced-Resources-Code += 1 We're using Wichorus, but in working with other vendors and service providers in the past who were using the Alvarion ASN-GW I don't recall that there were significant differences in QOS assignment at least. Looking back through my notes it does appear that most of them were using the proprietary Filter-ID method of service assignment. Using the Filter-Id might help rule out any strange EAP issues. Studying the table of attributes in the WiMAX forum stage three docs (Tables in section 5) also helps explain which TLVs are required and which are not when generating the appropriate responses. Ben
-----Original Message----- From: freeradius-users- bounces+wiechman.lists=gmail.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@lists.freeradius.org] On Behalf Of Anup krishnan A Sent: Wednesday, October 06, 2010 3:11 AM To: FreeRadius users mailing list Subject: Re: WiMax VSA Support
Hi Alan,
Thank you for your quick response.
We have already checked the dictionary and found that wimax dictionary is available in the freeradius server.
Actually we are using Freeradius server 2.1.9 and Alvarion base-station and Alvarion ASN GW. Initially we created a service profile in Alvarion ASN GW for the user "test" using their management software 'AlvariStar'. And 'users' file in the freeradius has been updated to add the user "test" as follows,
test Cleartext-Password := "test" Auth-Type = Local, Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 192.168.0.33, Framed-IP-Netmask = 255.255.255.0, Framed-Routing = Broadcast-Listen, Filter-Id = "servprof2"
where "servprof2" is the name of the service profile created in Alvarion ASN GW. In this case the authentication was successful and MS has got the IP as well.
Then we tried to create the service profile for the user "test" from the Freeradius by using WiMAX attributes found in the file dictionary.wimax'.The entries for the user in the 'users' file is as shown below.
test Cleartext-Password := "test" Auth-Type = Local, Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IP-Address = 192.168.0.33, Framed-IP-Netmask = 255.255.255.0, WiMAX-Service-Profile-Id=1, WiMAX-Media-Flow-Type=Streaming-Video, WiMAX-Schedule-Type = Best-Effort, WiMAX-QoS-Id=01, WiMAX-Media-Flow-Type=Robust-Browser, WiMAX-Traffic-Priority=0, WiMAX-Maximum-Sustained-Traffic-Rate=512000
In this case Freeradius has sent the Access-Accept, but the authentication process is not successful and MS is showing an error message as "EAP supplicant transferring error".
I hope you understand the problem
Regards, Anup
Anup wrote:
Hi, I would like to know whether latest Freeradius version has the support for WiMax VSAs?
The server comes with documentation and dictionary files. Please read them.
Also please tell me how to send the WiMAX Qos Descriptors in Access-Accept
VSAs are just attributes. They can be added / edited like anything else.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
----------------------------------------- This email was sent using SquirrelMail. "Webmail for nuts!" http://squirrelmail.org/
______________________________________ Scanned and protected by Email scanner - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html