You can't do much about it. The portmaster can delay accounting packets
if it wants, or if you happen to have some packetloss. Consider the
following scenario:
1. luser logs in on port S8
2. accounting packet for S8 gets a bit delayed
3. luser logs in on port S10
4. accounting packets for S8 and S10 hit radiusd a bit later
It could be solved by adding a small, short-lived authentication cache
that is also checked for double logins (with the extra OOB SNMP check).
That would also catch these cases. However I'm not sure if that's
worth the trouble.
Mike.
-- Miquel van | Cistron Internet Services -- Alphen aan den Rijn. Smoorenburg, | mailto:info@cistron.nl http://www.cistron.nl/ miquels@cistron.nl | PTT's Het Net: Surfen in de gootsteen! <*>-- The From: and Reply-To: addresses are internal mail2news gateway addresses. Reply to the list or to miquels@cistron.nl (Miquel van Smoorenburg) - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.