Re: radius accounting proxy usage

Hi Deon,

Deon van der Merwe wrote:

> Hi Stipe,
> 
> Yes- you are correct in your assumptions of my broken explanation of
> the setup.  "with parent" is that there is a native RADIUS server.
> 
> I will do a build using the cvs versions of the radius code and test it again.
> 
> This is how our setup also looks (as you have it):
>   APN <--acct pdu--> kannel <--acct pdu--> RADIUS

yep.

> Please confirm for me:
> - the RADIUS authentication message still go to the native RADIUS server

this depends on your APN setup. Our Ascend MAX that we used has _two_ points in 
defining the RADIUS server, one for _auth_, and one for _acct_. So it acts as 
follows:

   APN <--auth pdu-->                       RADIUS
       <--acct pdu--> kannel <--acct pdu-->

which means the auth PDUs are directly going to the RADIUS daemon, only the acct 
PDUs are proxied via kannel.

> - only the RADIUS accounting messages are sent to my kannel server for
> proxy to the real RADIUS server

yep.

But this has to be confired on the APN side of course.

Stipe

mailto:stolj_{at}_wapme-group.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------