Yes, it's me again. :p I have found out that when using freeradius as a radius proxy, the requests get transformed while going through Freeradius. The most notable change is that cisco_vsa_hack applies to proxied requests. As some radius software do not understand hacked requests, the proxy fails in unexpected ways. Removing cisco_vsa_hack from radiusd.conf fixes this, but makes working with SQL impossible as the table names change from Start/StopVoip to Start/Stoph323-request-type=Voip which cause errors.
The only way I found to fix this in an acceptable way was to remove from the dictionary.cisco file the attributes that I do not want hacked, but this effectively removes them from the SQL queries as freeRadius doesn't recognise them as attributes anymore. Is there some other way to fix this in a more ellegant manner? Like a configuration option that makes freeradius send the original request to the end-radius? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
