Hello Michael -
A copy of the snmpwalk would be useful. I will also need to know the
Portmaster model number and the firmware/software version.
thanks
Hugh
On Wed, 9 Jan 2002 10:59, Michael Bellears wrote:
> Replacing the Nas.pm does not seem to fix the snmp problem to the PM3
> (See debug
Replacing the Nas.pm does not seem to fix the snmp problem to the PM3
(See debug output below).
If you like I can do an snmpwalk on the pm3's to get correct oid's...
The original users session is now deleted if another session is started,
it is not denied.
Wed Jan 9 09:16:31 2002: DEBUG: Query
Thanks for the reply Hugh - That certainly clears things up!
Side Note: I also noticed that there was a bug in Nas.pm (Discussed on
the list: (RADIATOR) IMPORTANT - NasType Livingston on Radiator 2.18,
dated Mon, 19 Mar 2001), which was affecting NasType Livingston - I have
applied the patched ve
Hello Michael -
The SNMP query is not run for every access request - it is only run if there
is a session limit exceeded according to the session database. The problem
with simultaneous use checking is that in many cases the information received
from the NAS in the radius accounting requests
Hi,
This has been discussed on the list before, but I cannot seem to find a
resolution ;)
One of our clients has Radiator 2.18 with Radmin 1.5 running on Debian
Linux 2.2, using PM3 NAS's.
Denying Simultaneous use has never worked when clients connect with
multilink ISDN connections - I now se
