On Tue, 2 Nov 2004, gp wrote: > because I was looking into so many things in our network. I am still > looking into what Radius we have. Thanks for the email. >
btw, here's two heuristic methods you can code in to know if there are stale logins in the radius database without using RAS probes: 1) if a radius authentication request suddenly comes in from a certain RAS IP:Port, then any logged-in user in the radius dbase with a matching RAS IP:Port is stale. how can a user be logged in on that port if someone on that port came in requesting for authentication? drawback: if you dont have a busy RAS, this wont be too effective. 2) some RAS have reboot session IDs which increment each reboot (or after a very long uptime). with this you will know which users are stale in case a RAS reboot (or roll-over) happens because new users coming in will have a different reboot session ID from the stale users. drawback: usually only useful after power-failures. pong -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
