Changes to safe-characters list not honoured

2012-05-31 Thread Jack Patmos
Hi, I am using FreeRADIUS 2.1.10 to write accounting data to a postgres database. The usernames are email addresses and therefore might contain characters that are not included in the default safe-characters list (for example, '+'). I am also writing user-agents, which contain other characters

Re: Changes to safe-characters list not honoured

2012-05-31 Thread Jack Patmos
This has worked- thank you, Alan. I have multiple servers configured that use different databases- changing the safe-characters list in each of these db configs has fixed the issue. On 31 May 2012 12:03, Alan DeKok al...@deployingradius.com wrote: Jack Patmos wrote: I have modified the safe

Can translation of RADIUS packet attributes (e.g., NAS-Port-Type) be configured?

2011-08-17 Thread Jack Patmos
I am running FreeRADIUS 2.1.7. I am attempting to write accounting data to Postgres database. In the database the NAS port type from the request is stored as the integer value that defines the port type in RFC2865 (e.g., 19 - 'Wireless - IEEE 802.11'). The database table is fixed and cannot be

Re: Can translation of RADIUS packet attributes (e.g., NAS-Port-Type) be configured?

2011-08-17 Thread Jack Patmos
curious if it's possible to configure the behaviour of FreeRADIUS in this regard? Jack. On 17 August 2011 09:56, Jack Patmos jack.pat...@googlemail.com wrote: I am running FreeRADIUS 2.1.7. I am attempting to write accounting data to Postgres database. In the database the NAS port type from

Re: Can translation of RADIUS packet attributes (e.g., NAS-Port-Type) be configured?

2011-08-17 Thread Jack Patmos
10:59, Fajar A. Nugraha l...@fajar.net wrote: On Wed, Aug 17, 2011 at 4:13 PM, Jack Patmos jack.pat...@googlemail.com wrote: Guess I should have persevered for another 10 minutes. I have found a solution to my problem, which is to change my accounting_*_query from: [...] '%{NAS-Port-Type