Interesting rlm_acct_unique situation

[Mike Atkinson]

I'm having a rather interesting problem with the rlm_acct_unique module 
for freeradius.    I'm finding situations where the value returned is 
not actually unique, but the components configured to build it are all 
unique.   The relevant lines from radiusd.conf are:

key = "User-Name, Acct-Session-Id, NAS-IP-Address, NAS-Port-Id, 
Client-IP-Address"

I have about 900 records in my accounting table now where each of these 
entities are unique, but the returned MD5 hash is not.  

For example, I have many records where the User-Name, Acct-Session-Id, 
NAS-IP-Address, and Client-IP-Address are the same, but the NAS-Port-Id 
is different, yet the hash is computed the same.  Originally I had the 
NAS-Port-Id and Client-IP-Address reversed (as they were in the original 
file provided with freeradius) but reversed them while testing to see if 
this made a difference or not.

This is using freeradius version 0.8.1.  I realize that there is a new 
version available, but wanted to ask and see if anyone has seen similar 
situations before going through the pains of an upgrade.   I did search 
the list and did not find anything that seemed related to a fix or 
report of anything like this.

Thanks in advance,
Mike Atkinson


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