config checker appears over-anxious (with incorrect? result) #1696

Open
alanbuxey opened this Issue Aug 28, 2016 · 2 comments

Projects

None yet

2 participants

@alanbuxey
Member
alanbuxey commented Aug 28, 2016 edited

hi,

un Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[41]: Please change attribute reference to '&Chargeable-User-Identity := ...'
Sun Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[52]: Please change attribute reference to '&Chargeable-User-Identity = ...'
Sun Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[41]: Please change attribute reference to '&Chargeable-User-Identity := ...'
Sun Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[52]: Please change attribute reference to '&Chargeable-User-Identity = ...'
Sun Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[41]: Please change attribute reference to '&Chargeable-User-Identity := ...'
Sun Aug 28 19:48:50 2016 : Warn  : /etc/raddb/policy.d/cui[52]: Please change attribute reference to '&Chargeable-User-Identity = ...'

but, the section with line 41

cui.authorize {
        if ("%{client:add_cui}" == 'yes') {
                update request {
                        &Chargeable-User-Identity := 0x00
                }
        }
}

the section with line 52

cui.pre-proxy {
        if (("%{request:Packet-Type}" == 'Access-Request') && ("%{client:add_cui}" == 'yes')) {
                update proxy-request {
                        &Chargeable-User-Identity = 0x00
                }
        }
}

also, noted in greater debug, this sort of things appears just before the Warn output:

hex: src/lib/radius_decode.c:915   : -- fr_radius_decode_pair_value --
hex: src/lib/radius_decode.c:915   : 0000: 00 
msg: src/lib/radius_decode.c:917   : Parent Chargeable-User-Identity len 1 ... 1
msg: src/lib/radius_decode.c:1069  : Type "octets" (2)
@arr2036
Member
arr2036 commented Aug 29, 2016

please use triple backticks around config sections, grrrr.

@alanbuxey
Member

:) sorry!

@arr2036 arr2036 added this to the 4.0.0 release milestone Aug 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment