Ryan Williams wrote:
The difficulty arises when trying to run a distributed session table and also trying to implement some sort of replication so the slaves can push their radacct table back up to the master while avoiding PK conflicts.
Don't. The database doesn't know how to do conflict resolution for RADIUS sessions. The RADIUS server does. Let it do the conflict resolution.
I’m considering one of the two solutions
Both will work, but will create duplicate sessions in the DB, one for each slave.
Does anyone have any experience with either or does anyone have any thoughts on the matter?
radrelay. Copy the accounting packets to ONE radius server, and have it write to the DB. It does conflict resolution, and there are no problems. Alan DeKok.