remember my posting from 16th October?
The situation has improved dramatically since using RADIUS to validate
the dial-in users. The RADIUS authentication request forces the ISDN to
dial, so the line is open when the message is sent from the remote site to
the central syslog.
The problem is still present if the user does not actively log off, but
is timed out by the Portmaster. In that case the ISDN is long timed out
(unless another user is holding it open) and the "disconnected" message
does not get through to the central site's syslog.
Is there some way to configure the Portmaster to actively connect again
(perhaps to RADIUS, because the protocol will almost guarantee a
connection being made) to transmit the disconnection info?
Does accounting do this? How do I activate accounting, if this is the
case?
Am I a victim of old versions?
ComOS - Cayman GatorAccess MP
login: !root
Password:
Command> ver
Cayman Systems GatorAccess MP Version 3.0.3
Command> exit
RADIUS (also from Cayman) 1.9
Regards,
Phil
PLUS COMMUNICATIONS, Vienna, Austria
http://www.plus.at
-----------------------------16th October--------------------------------------
I don't get every activity written into syslog. This has happened since
installing a second PortMaster at a remote location.
Remote Portmaster --ethernet-- Cisco 2503i --ISDN dial on demand-- Cisco 2503i
Apparantly the latency of ISDN dialling causes the packets to get lost. I can
see the user logout if he actively did this (because the ISDN connection is
still open). I cannot see this if he is timed-out for inactivity because the
ISDN connection times out sooner (unless the ISDN is open because of other
users' activities).
Is there a way to wait for the connection, or to delay the sending of the
logging info?
-----------------------------16th October--------------------------------------