In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote: >"Marcelo Ferreira" <[EMAIL PROTECTED]> wrote: >> I think that the index of radutmp file is port number and when FR >> receives a STOP accounting packet, the session ID at port position >> is not the same because many others subscribers has logged in before >> and, logically, the session ID at that port number position is not >> the same of the STOP package. > > Ah, of course. > > Hmm... I guess that the only way around this is to hack the radutmp >module to use the session ID as the key, not the port. > I think that change will even be backwards compatible.
The reason why it didn't do that is that by using nas/port you can detect it if a stop packet gets lost - a start packet on an active nas/port provides a clue that something is wrong. So it would probably be a good idea to make this configurable. Mike. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
