----- Original Message ----- From: "Boian Jordanov" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, March 23, 2005 9:56 AM
Subject: Re: rlm_perl hash issue



On Wed, Mar 23, 2005 at 05:13:14AM +0200, Chris Knipe wrote:
Lo all,

This has been to the perl mailing lists as well, there is nothing wrong
with the code as far as every one knows... rlm_perl just doesn't like this
for some reason....


Snipets of the script in question:
       $RAD_REPLY{'Acct-Interim-Interval'} = "300";
       $RAD_REPLY{'MS-MPPE-Encryption-Policy'} = "1";
       $RAD_REPLY{'MS-MPPE-Encryption-Types'} = "LS";
       $RAD_REPLY{'Rate-Limit'} = "256k/512k";
       $RAD_REPLY{'Recv-Limit'} = $BytesAvail - $BytesUsed;
       $RAD_REPLY{'Xmit-Limit'} = $BytesAvail - $BytesUsed;
       $RAD_REPLY{'Reply-Message'} = "You have " .
$za->format_bytes($BytesAvail - $BytesUsed) . " available.";
       $RAD_REPLY{'Session-Timeout'} = "86400";

Righty. From the above, EVERYTHING gets returned (radiusd -X reports that
rlm_perl added the values) with the EXCEPTION of Recv-Limit and Xmit-Limit.
*IF* I add physical values to Recv-Limit, Xmit-Limit, then radiusd -X finds
the attributes and add them to the reply packet.



Basically rlm_perl expects in a hash value - string not number. for example '1' instead 1. It is well known issue and will be fixed soon.

AHA!

Alrighty, thanks :)

--
Chris.


- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to