Soory guys, I didn't check the code right, it zap the data out, the comment is the wrong thing..... ... can we remove it? there is no zap at radutmp_lookup...
again, sorry... []s ------------------------------------------------------------ Marcelo Ferreira Canbras TVA Cabo Ltda Canbras Acesso - STA Phone: +5511-4993-8728 ------------------------------------------------------------ ----- Original Message ----- From: "Marcelo Ferreira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 31, 2002 8:18 AM Subject: Re: Error: Accounting: logout: entry for NAS cnet-bsn port 1929379840 has wrong ID > Miquel, > > In my case, the port won't change for eache new user because my B-Ras dosn't > have fisical ports, > just logical ones. > > but you're right saying that. let's do something different, let's make > another module > (rlm_radutmp_session) and the adm could choose what module to use at > radiusd.conf. > > I made the hack for rlm_radutmp last night and I'll try it this morning. > If it runs good, I'll work at the new module. > > BTW, at radzap.c code, I didn't see the code for 'radzap' the data, just a > comment "Match it, Zap it" and then close(fd), return(0). So I added it from > a cistron radzap. > > []s > > Marcelo Costa > > ----- Original Message ----- > From: "Miquel van Smoorenburg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, January 30, 2002 8:16 PM > Subject: Re: Error: Accounting: logout: entry for NAS cnet-bsn port > 1929379840 has wrong ID > > > > 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 > > > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
