Re: [bgd@icomag.de: Re: (RADIATOR) integer disconnect causes]

2003-11-17 Thread Hugh Irvine
Hello Bogdan - I have already responded to this question by suggesting you download the source tarball to make sure you are running the correct code. I would be interested to see the results and startup message when you do this: cd /your/Radiator/src/directory perl radiusd -log_stdout -foreg

[bgd@icomag.de: Re: (RADIATOR) integer disconnect causes]

2003-11-17 Thread Bogdan TARU
Hi Hugh & all, Upgraded to Radiator-3.7.1, but still the same problem. When disconnecting, this is what I see in the log file: Fri Nov 14 10:50:47 2003: DEBUG: Packet dump: *** Received from 192.168.0.10 port 1646 Code: Accounting-Request Identifier: 188 Authentic: <0>MM<18

Re: (RADIATOR) integer disconnect causes

2003-11-13 Thread Hugh Irvine
Hello Bogdan - This should be fixed in the latest version Radiator 3.7.1. From the history file: รข Improvements to storage of VALUE in dictionary allows decoding based on the attribute name rather than the number, which allows correct unpacking of attributes with synonyms, such as Ascend-Di

(RADIATOR) integer disconnect causes

2003-11-13 Thread Bogdan TARU
Hi everyone, I have a problem with a Cisco AS5300 and the disconnect causes. They appear as integers (Ascend-Disconnect-Cause = 45) in the log file, and they are inserted into the database as integers as well. The radiator is started with -dictionary-file pointing to the 'generic' d