hi, simple and short question:
when using radrelay and there is the possibility that accounting packtets of the same session can come through different radius servers and then are relayed to each other then i think that the module configuration of acct_unique should be used without the Client-IP-Address Atrribute, cause the unique id could be different even though its the same real session, is this right? furthermore i realized that in the sql.conf accounting_stop_query no "where"-statement with AcctUniqueId exists. if a accounting stop paket is injected and more than 1 session with the AcctSessionId, UserName, NASIPAddress and AcctStopTime=0 is open then this will be result in a duplicate session update and will fail. iam not 100% sure if iam correct but if, what should be the best solution of handling this problem? thanks for any answer - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html