On 28 August 2013 09:09, Alan DeKok <aland@deployingradius.com> wrote:
See the debug output. If it's in the debug output, you can use it. If it's not in the debug output, it doesn't exist. And you can't use it.
You can always reference the outer tunnel from the inner one.
OK. So, I found a couple of *key* statements in the debug output; and running the server with -X gives me [f_ticks] expand: %{proxy-reply:Packet-Type} -> [f_ticks] ... expanding second conditional [f_ticks] expand: f_ticks.%{%{proxy-reply:Packet-Type}:-format} -> f_ticks.format WARNING: No such configuration item .f_ticks.format [f_ticks] No such entry ".f_ticks.format" ++[f_ticks] returns noop But I don't seem to be writing any output at all from the f_ticks module (whether in debug mode or not). It looks like this: linelog f_ticks { filename = ${logdir}/f-ticks format = "%{outer.User-Name}#%{User-Name}#%{Packet-Src-IP-Address}#" reference = "f_ticks.%{%{proxy-reply:Packet-Type}:-format}" f_ticks { Access-Accept = "F-TICKS/eduroam/1.0#REALM=%{Realm}#VISCOUNTRY=EU#VISINST=%{Operator-Name}#CSI=%{Calling-Station-Id}#RESULT=OK#" Access-Reject = "F-TICKS/eduroam/1.0#REALM=%{Realm}#VISCOUNTRY=EU#VISINST=%{Operator-Name}#CSI=%{Calling-Station-Id}#RESULT=FAIL#" } }
Alan DeKok.
Cheers, Andrej