Module Creation and Incoming request identification

Rajkumar R rajkumar.r at aricent.com
Wed Jan 5 08:04:28 CET 2011 

Thanks all for your inputs. Is it the account type listen section in radiusd.conf file you are referencing about(to include new module)?

-Raj

________________________________________
De: freeradius-devel-bounces+lscrlstld=gmail.com at lists.freeradius.org
[mailto:freeradius-devel-bounces+lscrlstld=gmail.com at lists.freeradius.org]
Em nome de Rajkumar R
Enviada em: ter?a-feira, 4 de janeiro de 2011 08:59
Para: freeradius-devel at lists.freeradius.org
Assunto: Module Creation and Incoming request identification
> 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.

You can create a perl module e call it in accounting section, it is possible
to filter acct stop and start using ulang.




------------------------------

Message: 2
Date: Tue, 4 Jan 2011 12:56:54 +0000
From: Alexander Clouter <alex at digriz.org.uk>
Subject: Re: Module Creation and Incoming request identification
To: freeradius-devel at lists.freeradius.org
Message-ID: <m1ibv7-mk8.ln1 at chipmunk.wormnet.eu>

Rajkumar R <rajkumar.r at aricent.com> wrote:
>
> 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:
>
rlm_perl

Cheers

--
Alexander Clouter
.sigmonster says: Today is the last day of your life so far.



------------------------------

Message: 3
Date: Wed, 5 Jan 2011 07:58:52 +1000
From: Nikki Watt <nikki.watt at qut.edu.au>
Subject: RE: Module Creation and Incoming request identification
To: FreeRadius developers mailing list
        <freeradius-devel at lists.freeradius.org>
Message-ID:
        <6D78B4DCFF9785409FE29BE1F01B3A6BA8179461 at QUTEXMBX03.qut.edu.au>
Content-Type: text/plain; charset="us-ascii"

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

Nikki Watt | Network Programmer | Network Operations Centre | ITS | Level 3, Synergy Building (88 Musk Avenue, Kelvin Grove)  | Ph: 3138 6858 | nikki.watt at qut.edu.au<mailto:nikki.watt at qut.edu.au> | www.its.qut.edu.au<http://www.its.qut.edu.au> | CRICOS No 00213J

From: freeradius-devel-bounces+nikki.watt=qut.edu.au at lists.freeradius.org [mailto:freeradius-devel-bounces+nikki.watt=qut.edu.au at lists.freeradius.org] On Behalf Of Rajkumar R
Sent: Tuesday, 4 January 2011 8:59 PM
To: freeradius-devel at 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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freeradius.org/pipermail/freeradius-devel/attachments/20110105/95043135/attachment-0001.html>

------------------------------

Message: 4
Date: Wed, 5 Jan 2011 11:44:50 +0530
From: Rajkumar R <rajkumar.r at aricent.com>
Subject: RE: Module Creation and Incoming request identification
To: "freeradius-devel at lists.freeradius.org"
        <freeradius-devel at lists.freeradius.org>
Message-ID:
        <5610394F5AEAD84BB43E1F94901321C1A682FA20 at GUREXMB02.ASIAN.AD.ARICENT.COM>

Content-Type: text/plain; charset="us-ascii"

Could anyone please provide your inputs on this?

thanks,
Raj

From: Rajkumar R
Sent: Tuesday, January 04, 2011 4:29 PM
To: 'freeradius-devel at 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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freeradius.org/pipermail/freeradius-devel/attachments/20110105/3121e0d7/attachment.html>

------------------------------

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html


End of Freeradius-Devel Digest, Vol 69, Issue 2
***********************************************

"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."

More information about the Freeradius-Devel mailing list