Hi all,
Firstly, no, this isn't the usual crypt question ( I think:)
We're using Radiator 2.18.4 authenticating users against LDAP entries.
Usernames and passwords in LDAP have a length between 3 and 63
characters, these limitations are due to policy. In this case we use
PAP.
I've noticed a pec
Hello Richard,
Unfortunately, it's a limitation of the Authen::SMB module (or is it more
on the smbval library).
As of now, the only thing I can think of is install RADIUS on the NT
machine. But this might not be an option to you.
Regards,
Neil D. Quiogue "Information and attachments
-- Forwarded Message --
Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [Virgil
<[EMAIL PROTECTED]>]
Date: Wed, 17 Jul 2002 22:38:57 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
>From [EMAIL PROTECTED] Wed Jul 17 22:38:57 2002
Received: from bnc.webce
Neil Thanks for the reply. Yes we are using Redhat 7.3 Do you know of a work around? Hugh It sounds like Neil has hit the nail on the head. ThanksRichard -"neil d. quiogue" <[EMAIL PROTECTED]> wrote: -To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>From: "neil d. quiogue" <[EMAIL PROTECTED]
Hello Richard,
Are you running it in a UNIX-based system? If so then NT Global
Groups (Group check item) are not enforced.
FYI, The Group check item does not work with Local Groups.
Regards,
Neil D. Quiogue "Information and attachments herein are
intended for the named recipientsonly.
Hugh Here is the copy the trace 4 debug. As you can see we are using a user called "radius". This user is not a member of the group "Dialup" and should be rejected. We downloaded the updated file AuthNT.pm. We have not tested this yet but will soon and I will feed back our success to you for expire
Hi Henry,
On Thu, 18 Jul 2002 11:55, Henry Su wrote:
> Thanks, Mike. I think tried to subscribe the mail-list yesterday and I did
> get confirmation from [EMAIL PROTECTED] with subject "Majordomo
> results: subscribe", but I still did receive any email from mailing list.
You were not subscribed,
Hello Henry,
On Thu, 18 Jul 2002 11:27, Henry Su wrote:
> Thanks a lot, Mike. I tried to re-install the CA on XP machine, it seems
> worked on the radius side. I have 10 frames for eap-tls auth, and radius
> send access-accept packet (see it in the attachment). I also have an dhcp
> server runnin
Hello Claudio -
There is an example of how to do this in the file "goodies/hooks.txt".
Two hooks are used, a StartupHook to load some definitions, and a
PostAuthHook to translate the reply attributes.
regards
Hugh
At 18:45 -0300 17/7/02, Claudio Lapidus wrote:
>Hi all,
>
>We have NASes of
Salut Jeje -
Comment va la vie?
The first question is "have you also applied all the patches for 3.1?".
The second question is the usual "can you please send me a copy of
the configuration file (no secrets) together with a trace 4 debug
showing what is happening?".
BTW - in what you show be
Hello Gilbert -
We have recently introduced vendor-specific attributes for Radiator,
so you could use the OSC-AVPAIR attribute to do this. If you are
wnating to do something special with your own dialer, I suggest you
write your own AuthBy module. You should start with the
"Radius/AuthTEST.p
Hi all,
Here is a patch for the AuthTACACSPLUS package (attached to this mail).
Before, the authentication type was selected according to the version of
the package (except CHAP).
I added a keyword in order to force the authentication type. Here is an
example of a radiator config file:
Hi all,
We have NASes of different brands (Cisco and Lucent, might be a third in the
future) and they are intermixed in the network, i.e. any call can go to any
NAS. Then we proxy the request to a remote radius, which is responsible for
authenticate the end user, but is unaware of the technolo
Hi,
I will be developping a dialer and am looking for a radius server that
will allow me to make sure that my users will only be able to connect if
they use my dialer. Does or can Radiator do this? If so how? If I wanted to
push updates and communicate with the dialer after the user auths ca
When upgrading from 2.19 to. 3.1, I had a strange problem that made me
cancel the upgrade.
this code (some hidden for security purpose):
# accepte toutes les requetes venant du proxy
AcceptIfMissing
Filename /dev/null
Ad
15 matches
Mail list logo
