Hi Hugh & all,
Well, the problem is that when sending Session-Timeouts, the Cisco machine is not giving the IP address back in the 'disconnect' reply. You can see it at http://bgd.icomag.de/cisco/radius.txt The cisco configuration can be found at: http://bgd.icomag.de/cisco/cisco_as5300.txt The session that you see in radius.txt is basically a user which already dialed in twice in the last 24hrs, so he is not allowed to enter the system no more. So I am sending him a session-timeout of 1 second. After 1 second, he is disconnecting, and I get a reply from the cisco machine, reply which doesn't include the IP address of the disconnected client (like for a normal pppRcvTerminate). So I cannot update my pool table because I don't have the IP. I have thought abuot adding an additional column to the 'pools' table, which keeps the NASPort, and to delete based on that, but I am wondering if there isn't any other way of convincing the Cisco machine to send the IP address even for session-timeouts. Thanks, bogdan ---------------------------- iCom Media AG Kirchweg 36 Koln, 50858 Germany Phone: +49-(0)221-485-689-16 Fax : +49-(0)221-485-689-20 Mobile:+49-(0)173-906-46-01 On Tue, 25 Feb 2003, Hugh Irvine wrote: > > Hello Bogdan - > > This sounds like the Cisco is not sending a Stop when the session is > disconnected. > > Could you send me a copy of your configuration file (no secrets) > together with trace 4 debug showing what is happening with the access > request and the subsequent accounting requests? > > regards > > Hugh > > > On Monday, Feb 24, 2003, at 20:25 Australia/Melbourne, Bogdan TARU > wrote: > > > > > Hi everyone, > > > > And thanks a lot for your replies regarding how to use SQL functions > > inside a PostAuthHook! > > > > Right now I have another problem, unfortunately. I am sending > > Session-Timeouts for some of our customers, and they get disconnected > > indeed, but they are not deleted from the 'pools' table (in my case) up > > until the moment 'DefaultLeasePeriod' is reached. This is really > > happening > > for all those customers, so I think I can rule out network problems > > (like > > lost UDP packets that the cisco dialin machine sends to the radiator > > port). > > > > I am using one Cisco AS5300 which authentificates the clients to a > > Radiator 2.19. > > > > Thank you, > > bogdan > > > > > > ---------------------------- > > iCom Media AG > > Kirchweg 36 > > Koln, 50858 > > Germany > > > > Phone: +49-(0)221-485-689-16 > > Fax : +49-(0)221-485-689-20 > > Mobile:+49-(0)173-906-46-01 > > > > === > > Archive at http://www.open.com.au/archives/radiator/ > > Announcements on [EMAIL PROTECTED] > > To unsubscribe, email '[EMAIL PROTECTED]' with > > 'unsubscribe radiator' in the body of the message. > > > > > > NB: have you included a copy of your configuration file (no secrets), > together with a trace 4 debug showing what is happening? > > -- > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. > - > Nets: internetwork inventory and management - graphical, extensible, > flexible with hardware, software, platform and database independence. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.