-----Original Message----- From: dave anderson Sent: February 13, 2009 5:14 PM To: freeradius-users Subject: FW: wimax.c I have the Wimax FreeRadius (2.1.3) working but I am a bit unclear on a few key reply parameters: In the default server I have added update "reply"{ WiMAX-MSK = �%{reply:EAP-MSK}� Which successfully produces the right length MSK in the reply. However to populate these other variable into the reply such as Session reply, it is not clear how to do so: WiMAX-AAA-Session-ID = ? WiMAX-HA-RK-SPI = ? WiMAX-HA-RK-Lifetime = ? How to I get the reply to include these with correct values ? Further, putting WiMAX-MN-NAI = �%{User-Name}� in the default config prior to calling the wimax function still results in the WiMAX module warning that WiMAX-MN-NAI has not been set. Would anyone have advice on how to resolve these two issues? Thanks Dave Anderson
dave anderson wrote:
However to populate these other variable into the reply such as Session reply, it is not clear how to do so:
WiMAX-AAA-Session-ID = ? WiMAX-HA-RK-SPI = ? WiMAX-HA-RK-Lifetime = ?
The WiMAX specifications really aren't clear how most of those are calculated. i.e. it says "up to local administrator".
How to I get the reply to include these with correct values ?
Further, putting WiMAX-MN-NAI = “%{User-Name}” in the default config prior to calling the wimax function still results in the WiMAX module warning that WiMAX-MN-NAI has not been set.
That's fixed in git, and will be in 2.1.4. Alan DeKok.
Ok thanks, so for the first item I can just put some function in to calculate it as I want or static code them. -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: February 14, 2009 10:32 AM To: FreeRadius users mailing list Subject: Re: FW: wimax.c dave anderson wrote:
However to populate these other variable into the reply such as Session reply, it is not clear how to do so:
WiMAX-AAA-Session-ID = ? WiMAX-HA-RK-SPI = ? WiMAX-HA-RK-Lifetime = ?
The WiMAX specifications really aren't clear how most of those are calculated. i.e. it says "up to local administrator".
How to I get the reply to include these with correct values ?
Further, putting WiMAX-MN-NAI = �%{User-Name}� in the default config prior to calling the wimax function still results in the WiMAX module warning that WiMAX-MN-NAI has not been set.
That's fixed in git, and will be in 2.1.4. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Also the raddact table has empty field for calling station-id for wimax. I know wimax has this field in hex rather than ascii which is a problem addressed wimax.c for auth. Changing the library to octet instead sting solves it for auth. Can you tell me which module or .c to look at for repairing this for accting and I will make the change. DA -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: February 14, 2009 10:32 AM To: FreeRadius users mailing list Subject: Re: FW: wimax.c dave anderson wrote:
However to populate these other variable into the reply such as Session reply, it is not clear how to do so:
WiMAX-AAA-Session-ID = ? WiMAX-HA-RK-SPI = ? WiMAX-HA-RK-Lifetime = ?
The WiMAX specifications really aren't clear how most of those are calculated. i.e. it says "up to local administrator".
How to I get the reply to include these with correct values ?
Further, putting WiMAX-MN-NAI = %{User-Name} in the default config prior to calling the wimax function still results in the WiMAX module warning that WiMAX-MN-NAI has not been set.
That's fixed in git, and will be in 2.1.4. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
dave anderson wrote:
Also the raddact table has empty field for calling station-id for wimax. I know wimax has this field in hex rather than ascii which is a problem addressed wimax.c for auth. Changing the library to octet instead sting solves it for auth.
Don't. Instead, list the "wimax" module in the "authorize" and "preacct" sections. It will re-write the Calling-Station-Id to something sane. This issue has been brought to the attention of the WiMAX forum, and after some pushing, it will be fixed in a future revision of their specifications. Alan DeKok.
Wimax.c needs a small fix in order to print the right debug message content. DEBUG2("rlm_wimax: Fixing WiMAX binary Calling-Station-Id to %17s",vp->vp_octets); Rather than as written DEBUG2("rlm_wimax: Fixing WiMAX binary Calling-Station-Id to %s",buffer); -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: February 15, 2009 12:09 AM To: FreeRadius users mailing list Subject: Re: wimax.c dave anderson wrote:
Also the raddact table has empty field for calling station-id for wimax. I know wimax has this field in hex rather than ascii which is a problem addressed wimax.c for auth. Changing the library to octet instead sting solves it for auth.
Don't. Instead, list the "wimax" module in the "authorize" and "preacct" sections. It will re-write the Calling-Station-Id to something sane. This issue has been brought to the attention of the WiMAX forum, and after some pushing, it will be fixed in a future revision of their specifications. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I would like to write the Wimax Freeradius Wiki but need an account. Can you help me get a log in. -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: February 17, 2009 6:15 AM To: FreeRadius users mailing list Subject: Re: wimax.c dave anderson wrote:
Wimax.c needs a small fix in order to print the right debug message content.
Fixed, thanks. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
Alan DeKok -
dave anderson