Hello Griff -
On Thursday 10 May 2001 10:51, Griff Hamlin wrote:
Hello all,
In using an SQL session database, and then a DefaultSimultaneousLogin
with 3 servers (2 for authentication and 1 for accounting) I find that
sometimes a stop record does not make it to the accounting server and
Hello Alex -
As usual, I will need to see a copy of your configuration file (no secrets)
together with a trace 4 debug from Radiator showing what is happening.
The most common cause of this is not returning a Service-Type = Framed-User
reply attribute in the Access-Accept.
hth
Hugh
On
Greetings all,
We are receiving the following error in Radiator Attribute Number 55
(vendor) is not defined in your dictionary
It is using an ERX Broadband Concentrator (Unisphere attributes)
Does anyone know what Attribute 55 would be so I can add it to my
dictionary.
Thanks in advance.
Griff,
We have run into this problem as well. We use our session database for
downstream customers to view their port usage. it is imperative that the
session database is accurate and does not contain stale entries. in response
I wrote a check program that polls the NAS units and find it's
El 10 May 2001, a las 10:25, Hugh Irvine escribió:
Hello Mariano -
Is the problem with AuthLog just because you are only logging failures (the
default)?
Nope... it's logging both (it is so set in the config file that I
attached to the other message)... and besides, I'm also radpwtsting
Hello Griff -
You can only specifiy the program.
You will have to check the output from both programs, as Radiator only knows
how to parse the output from the UCD version. The simplest thing is just to
download the recommended package and build it on your machine.
hth
Hugh
On Friday 11
Hello Leon -
You will need a packet sniffer, the Radiator log file and considerable
patience to track down this sort of problem.
Possible causes include (non-exhaustive list):
saturated links
NAS bugs or upstream network problems (or underpowered NAS)
slow SQL
Hello Anton -
To put a hard limit in each Realm, use the MaxSessions parameter.
See section 6.15.3 in the Radiator 2.18.1 reference manual.
If instead you want to limit sessions on a per user basis, you would use
DefaultSimultaneousUse in the AuthBy clause and Simultaneous-Use check items
HI If instead you want to limit sessions on a per user basis, you would use
HI DefaultSimultaneousUse in the AuthBy clause and Simultaneous-Use check items
HI in your user definitions.
How would this be done?
Saludos
Anton Krall
Director de Tecnologia
Inter.net Mexico
(www.mx.inter.net)
Hello Anton -
On Friday 11 May 2001 10:07, Anton Krall wrote:
HI If instead you want to limit sessions on a per user basis, you would
use HI DefaultSimultaneousUse in the AuthBy clause and Simultaneous-Use
check items HI in your user definitions.
How would this be done?
Sections 6.16.14
Hello James -
Use different Handlers, one for your news server and one for your other
authentication with appropriate AuthBy's and DefaultSimultaneousUse.
hth
Hugh
On Friday 11 May 2001 12:15, James Laszko wrote:
We use authentication on our news servers for our customers. When a
With AuthLDAP2 and OpenLDAP, the out-of-box performace was *horrible*
(like well under 10requests/sec). This was identified as
inefficiencies in the LDAP lookups, using BaseDN=ou=foo,o=bar,c=au.
In testing the ldap lookup, it was found that using
BaseDN=uid=user,ou=foo,o=bar,c=au resulted in
12 matches
Mail list logo
