Re: radius accounting proxy usage

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
> 
> Please confirm for me:
> - the RADIUS authentication message still go to the native RADIUS server
> - only the RADIUS accounting messages are sent to my kannel server for
> proxy to the real RADIUS server
> 
> For the setup with no native RADIUS to proxy too, this is my config:
> group = radius-acct
> secret-nas = test
> our-port = 1813
> 
> For the setup with the native RADIUS server, my setup is:
> group = radius-acct
> secret-radius = tester1234
> secret-nas = test
> our-port = 1813
> remote-host = 10.10.10.10
> remote-port = 1813

so far ok, as far as the MD5 secrets "test" and "tester1234" are also set on the 
APN resp. RADIUS daemon side. Which I suppose you have.

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/
-------------------------------------------------------------------