Hi Raj,

I’ve written a similar module for freeradius (except that it does asynchronous HTTP interaction with another server rather than UDP) by following the instructions on the freeradius wiki. There’s also an excellent example module included in the freeradius source code (<freeradius source directory>/src/modules/rlm_example/rlm_example.c) that I used as a guide. If you’re comfortable with the C language, perhaps that’s the way to go? If not, as others have suggested, rlm_perl may be better for you.

In either case, you just need to reference the module in the accounting section of your config and freeradius will call the module whenever it receives an accounting packet.

Regards,

Nikki

From: freeradius-devel-bounces+nikki.watt=qut.edu.au@lists.freeradius.org [mailto:freeradius-devel-bounces+nikki.watt=qut.edu.au@lists.freeradius.org] On Behalf Of Rajkumar R
Sent: Tuesday, 4 January 2011 8:59 PM
To: freeradius-devel@lists.freeradius.org
Subject: Module Creation and Incoming request identification

Hi,

I need to create a new module, which should send a UDP msg to another application server upon a Account-Start/Stop message request from a NAS. For this, request you to provide your inputs on the below queries:

1. I read in the wiki link that rlm approach to be used for creating a new module. Any examples available on the same?

2. How do I make the new procedure(to send UDPmsg to other application) aware that a new Acc-Start/Stop message has arrived? This is because, sending a msg to other application should be instantaneous.

Appreciate your inputs.

thanks,

Raj

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."