session {} not running second module

[Matt Nelson - Silverark]

Thanks Alan

> Don't do that.  It's not supported, and was never intended to work.
> You're using a VERY old version of the server.  When you upgrade, this 
> incorrect configuration will stop working.

I'm using the latest stable version and was just following instruction 
on the wiki: https://wiki.freeradius.org/config/Fail-over

[root at host2 etc]# radiusd -X
FreeRADIUS Version 3.0.13


I've just put the python code at the end of the authentication section 
instead, so the user-name gets updated after the auth bit is done but 
before the session section. It works without any issues and I don't have 
to use a group or anything additional. Can you advise what I would need 
to do if I wanted this to work in the session section?

This is a fresh install of 3.0.13, with a fresh config.

Kind Regards, Matt



On 16/03/2017 19:41, Alan DeKok wrote:

>> On Mar 16, 2017, at 3:36 PM, Matt Nelson - Silverark 
>> <matt.nelson at silverark.co.uk> wrote:
>> 
>> Hello All,
>> 
>> Please disregard my last email. I think I've solved it. The debugging 
>> showed me the update in the session code I posted returned noop, so 
>> noop must equal return! I added noop=1 and it kept me in the group. 
>> Just took a while to get my head around how the group bit works. 
>> Didn't realise the update request returned a code too, it must be 
>> numeric rather than return in the accounting section that's why it 
>> kept me in there.
>> 
>> if(config:User-Name) {
>> noop=1
> 
> Don't do that.  It's not supported, and was never intended to work.
> 
> You're using a VERY old version of the server.  When you upgrade, this 
> incorrect configuration will stop working.
> 
> Alan DeKok.
> 
> -
> List info/subscribe/unsubscribe? See 
> http://www.freeradius.org/list/devel.html