Just one thought:
I haven't been reading this thread in all its detail, but this might be
of some value. Some time back, I believe when we transitioned from USR
to Cisco NASes, we started getting log entries such as:
*** Received from X.X.X.X on port 1645
when we were definitely only listening
That was probably happening, because unless you set the Cisco
NAS in the config to send Auth/Accounting on 1812 and 1813, the default
is 1645 and 1646. The RFC has been changed to 1812 and 1813, but a lot
of NASs keep their default to 1645 and 1646 for compatibility purposes.
1645 used to
Hello Elias -
This looks like a different error on the production machine. Does the SQL
database operate correctly prior to the error you show below?
I would suggest you upgrade to Radiator 2.19 in any case, and let me know if
that makes a difference (there have been some SQL modifications).
Hello Dave -
Here is the message:
Sat Mar 9 09:37:10 2002: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 33555
and yes - it is telling you the *source* IP address and UDP port number from
which this request was received.
I have been thinking about adding the *destination* IP ad
Hugh or anyone else,
What NAS types are known to implement the Radius Disconnect-Request ?
Does anyone know how to enable it for 3com and/or Ascend equipment?
Ross Kusler
Senior Database Administrator
InReach Internet Communications LLC
[EMAIL PROTECTED]
- Original Message -
From: "
Hi,
Can anyone help with the Check Item Perl expression to enable us to
ensure that certain users cannot login via particular NAS?
That is, we want some users to be able to dial in via any NAS except
aaa.bbb.ccc.ddd and www.xxx.yyy.zzz .
Barry Andersson
===
Archive at http://www.open.com.au/
