Some questions about freeradius for WiMAX

[Ben Wiechman]

Since I see this from time to time I've attached a fairly functional virtual
server and policy for use with a WiMAX ASN-GW. 

Some notes:
- You may want to merge some of the configuration files
(dictionary/policy.conf/etc) to avoid overwriting any site local updates
that already exist.
- We use EAP-TTLS so this is more tested, however EAP-TLS should be more or
less functional.
- Configure your requests from your ASN-GW to use this virtual server.

HA-RK and associated lifetimes need to be calculated using some method of
your choice. We don't use Mobile IP or a Home Agent so I have not developed
policy to calculate and retrieve the required key context. Note that at this
time FR is not able to properly generate the RRQ-MN-HA-Key and will not be
able to do so without code updates.

It has been my experience while testing several different ASN-GWs that using
the standard default/inner-tunnel virtual servers will result in a
successful network entry. Some ASN-GWs may require additional work, and if
you plan to use MIP you will have additional requirements to generate and
retrieve the appropriate key context. 

Ben

-----Original Message-----
From: freeradius-users-bounces+wiechman.lists=gmail.com at lists.freeradius.org
[mailto:freeradius-users-bounces+wiechman.lists=gmail.com at lists.freeradius.o
rg] On Behalf Of WWF
Sent: Tuesday, June 08, 2010 2:29 AM
To: freeradius-users
Subject: Some questions about freeradius for WiMAX

Hi,all! 

I have several questions about fr 2.19 for WiMAX systems. 

1. My network is a private network and does not need accounting.Then if I
reply access accept with "Accounting-capabilities = 0", whether the ms can
know about it and won't send accounting packets to my freeradius? 

2. How to set values for these attributes: 
WiMAX-AAA-Session-ID = ?  
WiMAX-HA-RK-SPI = ?  
WiMAX-HA-RK-Lifetime = ?  

3. How to add support for the "Error-Cause" attribute defined in rfc 3576.
It seems no code for it in current implementation of 2.1.9 fr.

4. What the "disconnect request message" for? (for accounting?) I found in
wiki that current implementation does not support this message.

Thanks for your relpy.

2010-06-08 

-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freeradius-wimax-policy.tar.gz
Type: application/octet-stream
Size: 12680 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20100614/ce0c9943/attachment.obj>