I've just upgraded to 0.8 and have found various errors in my log
telling me that the op field for various attributes is NULL or
non-existent:
Error: rlm_sql: The 'op' field for attribute 'Framed-IP-Address =
192.168.0.1' is NULL, or non-existent.
I've cross referenced the `describe rad(check | reply);` output from
that of the 0.8 sql schema and there are differences, obviously.
My current radius database was created from the schema from 0.6 with no
customizations. I'm wondering if anyone knows what the effects would be
if I re-ran the current schema against the existing database. Would it
break everything or would it do what one would hope; update the
differences and keep the data intact?
Also, on a separate note, I posted a couple of days ago about usage
based accounting and got some replies about turning on alive accounting
update packets on my nas. I've done this, and it's sending the alive
packets, but some of the info from the packets isn't being put into the
database. Looking through the output from -X, it appears as though the
sql module is seeing the alive packets and parsing them against the
accounting_update_query variable from sql.conf. The variable doesn't
include the session time and in/out octets, which is what I want to have
updated the accounting record incrementally via the alive packets. If I
modify the variable to include AcctSessionTime = '%{Acct-Session-Time}',
AcctInputOctets = '%{Acct-Input-Octets}', AcctOutputOctets =
'%{Acct-Output-Octets}' is that supported (will it work?!) or do I need
to attack it from a different angle.
I'm not very sql savvy and making custom changes like that sorta scare
me as I don't want to blow the entire thing to pieces.
Any info is appreciated.
--
Regards,
Jason A. Lixfeld Fastvibe Corporation
Senior IP Network Engineer 220-156 Front St. W
[EMAIL PROTECTED] Toronto, ON M5V-2L6
-------------------------------------------------------------
tel://416.341.0099:223 fax://416.341.0088
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
