Hi, I am using the freeradius server 2.1.1 as the Radius server in the network to authenticate a wimax user. It seems that it could support the wimax VSA, since I found the dictionary.wimax in the dictionary directory. However, in my application, in the Access Accept message, the freeradius server Include the attributes of vendor-id 311 (microsoft), not having the expected attributes of wimax (such as MSK attribute). I want to how the radius server determine which dictionary it should use to response the incoming request? What I should do to make the freeradius server set the wimax specified attribute in the access-accept msg? Thanks ASTRI - Hong Kong Applied Science and Technology Research Institute tel:+852 <tel:+852> 3406 2918 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ying DONG wrote:
I am using the freeradius server 2.1.1 as the Radius server in the network to authenticate a wimax user.
It seems that it could support the wimax VSA, since I found the dictionary.wimax in the dictionary directory.
If you look at the *rest* of the configuration files, you'll see more references to WiMAX. Also, the release announcements, the web page...
However, in my application, in the Access Accept message, the freeradius server Include the attributes of vendor-id 311 (microsoft), not having the expected attributes of wimax (such as MSK attribute).
Because you have to configure it to do that.
I want to how the radius server determine which dictionary it should use to response the incoming request?
That's not how RADIUS works. It doesn't "determine" a dictionary to use.
What I should do to make the freeradius server set the wimax specified attribute in the access-accept msg?
Read raddb/modules/wimax. This is documented. Alan DeKok.
Hi, thanks for your quick reply. I have seen the documents related with wimax in the freeradius, files in rlm_wimax directory, dictionary.wimax, /modules/wimax. However, I didn't figure out how to configure it to let it use the wimax vender specified attribute. I also find the MSK is set to 32 bytes length. I am a little confused. Why not set the length to 64 bytes as the standard specified? In this case, how to generate 64-byte MSK in the access accept msg? Thanks, ying -----Original Message----- From: freeradius-users-bounces+ydong=astri.org@lists.freeradius.org [mailto:freeradius-users-bounces+ydong=astri.org@lists.freeradius.org] On Behalf Of Alan DeKok Sent: 2008年12月10日 16:48 To: FreeRadius users mailing list Subject: Re: wimax support Ying DONG wrote:
I am using the freeradius server 2.1.1 as the Radius server in the network to authenticate a wimax user.
It seems that it could support the wimax VSA, since I found the dictionary.wimax in the dictionary directory.
If you look at the *rest* of the configuration files, you'll see more references to WiMAX. Also, the release announcements, the web page...
However, in my application, in the Access Accept message, the freeradius server Include the attributes of vendor-id 311 (microsoft), not having the expected attributes of wimax (such as MSK attribute).
Because you have to configure it to do that.
I want to how the radius server determine which dictionary it should use to response the incoming request?
That's not how RADIUS works. It doesn't "determine" a dictionary to use.
What I should do to make the freeradius server set the wimax specified attribute in the access-accept msg?
Read raddb/modules/wimax. This is documented. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ying DONG wrote:
I have seen the documents related with wimax in the freeradius, files in rlm_wimax directory, dictionary.wimax, /modules/wimax. However, I didn't figure out how to configure it to let it use the wimax vender specified attribute.
You add them to the reply, with values, just like any other attribute.
I also find the MSK is set to 32 bytes length. I am a little confused. Why not set the length to 64 bytes as the standard specified?
The code generates the MSK as 64 bytes. If you see it as 32, then something is wrong. Perhaps you could post the debug output. Alan DeKok.
I also find the MSK is set to 32 bytes length. I am a little confused. Why not set the length to 64 bytes as the standard specified?
The code generates the MSK as 64 bytes. If you see it as 32, then something is wrong.
He probabaly means this (raddb/modules/wimax): # # Some useful things to remember: # # WiMAX-MSK = EAP MSK, but is 32 octets. Ivan Kalik Kalik Informatika ISP
Hi,again, I have figured out that the Freeradius server use the MS_MPPE_Recv_Key and MS_MPPE_Send_Key to transport the MSK to the ASN after successful EAP authentication. I find the rlm_wimax.c which computes the MIP key using wimax_postauth() function. However, I don't think the wimax module has been included in the freeradius since I could not get any information of mobility keying material generation when I tried to print out some information in the wimax_postauth() function. Is the wimax module included in the freeradius? Do I have to configure it to let it work? Then how to configure it? I have compiled the module and added the wimax lib to the freeradius lib. However, it doesn't work. Thanks, ying -----Original Message----- From: freeradius-users-bounces+ydong=astri.org@lists.freeradius.org [mailto:freeradius-users-bounces+ydong=astri.org@lists.freeradius.org] On Behalf Of Alan DeKok Sent: 2008年12月10日 16:48 To: FreeRadius users mailing list Subject: Re: wimax support Ying DONG wrote:
I am using the freeradius server 2.1.1 as the Radius server in the network to authenticate a wimax user.
It seems that it could support the wimax VSA, since I found the dictionary.wimax in the dictionary directory.
If you look at the *rest* of the configuration files, you'll see more references to WiMAX. Also, the release announcements, the web page...
However, in my application, in the Access Accept message, the freeradius server Include the attributes of vendor-id 311 (microsoft), not having the expected attributes of wimax (such as MSK attribute).
Because you have to configure it to do that.
I want to how the radius server determine which dictionary it should use to response the incoming request?
That's not how RADIUS works. It doesn't "determine" a dictionary to use.
What I should do to make the freeradius server set the wimax specified attribute in the access-accept msg?
Read raddb/modules/wimax. This is documented. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ying DONG wrote:
I have figured out that the Freeradius server use the MS_MPPE_Recv_Key and MS_MPPE_Send_Key to transport the MSK to the ASN after successful EAP authentication.
That is the normal EAP process.
I find the rlm_wimax.c which computes the MIP key using wimax_postauth() function.
Yes. It works.
However, I don't think the wimax module has been included in the freeradius since I could not get any information of mobility keying material generation when I tried to print out some information in the wimax_postauth() function.
You need to list "wimax" in the "postauth" section. This is documented in the "raddb/modules/wimax" file.
Is the wimax module included in the freeradius? Do I have to configure it to let it work? Then how to configure it? I have compiled the module and added the wimax lib to the freeradius lib. However, it doesn't work.
You need to configure it as instructed in the documentation. Alan DeKok.
participants (3)
-
Alan DeKok -
tnt＠kalik.net -
Ying DONG