<[EMAIL PROTECTED]> wrote: > When a NAS fails the telco will failover the the other NAS > when a Radius server fails the NAS will select it's twin-sister. > > The only thing this doesn't work for is Accounting.
You might want to take a look at 'radrelay', from the Cistron distribution. It's the preferred method for replicating accounting data. If you can come up with a patch to add it to FreeRADIUS, that would help a lot. > Then an accounting loop start that adds about 220KB to the detail file > for every packet received from a NAS. Probably the loop ends when a packet > get too large. (Some Proxy-xxxx fields are added to every hop). Yes. And you can't rely on the Proxy-State attribute to discover loops, as some RADIUS servers destroy the Proxy-State attribute. I believe that radrelay *should* take care of a lot of these issues. > When is Client-IP-Address added to the packet? (probably too late) It's not. It's a server-side attribute that's adding to the REQUEST data structure, but rlm_preprocess. > Why can't Client-IP-Address be used as a check-item? (if it is in the request) It can. > I've a patched freeradius to get it to work on AIX and I not aware > that the patches sent to the list have been incorporated or not. They haven't been incorporated. Quite frankly, I'm reluctant to do so. If you just patched it to *add* functionality or include files specifically for AIX, then I would have applied the patch. However, the patch *removes* functionality and include files which are currently used on other platforms. I'm not going to break the build on many platforms just to make it work on another one. So until I get time to edit the patch to fix it, or until you can supply a better patch, it won't get committed. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
