Hello again!
Forgiveness for having reached this situation, the result of several
unfortunate
events.
Thank you for reply and your time
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
This was asked many, many, times. And answered.
Ok, sorry to ask about that one more time.
I though that if I can work with Codigo-Reject attribute in Post-Auth
type Reject for EAP-TTLS-PAP and EAP-TTLS-MsCHAPv2, I would do the same in
PEAP.
I read
Hello,
I'm using FreeRADIUS Version 2.1.10 and I would like to know if I can
change the swith result to make something like that:
/etc/freeradius/sites-enable/default
...
switch %{Realm} {
case 'a' {
sql {
fail = 5
}
}
case 'b' {
ldap
english
:: Ana Gallardo Gómez ::
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hello again,
I can't reolve my problem and I don't know if is a bug o a configuration
error...
update reply {
Codigo-Reject = Imposible-Contactar-Backend
}
Operator = act like :=
¿ideas?
thanks very much
:: Ana Gallardo Gómez
* Packet-Type := Access-Reject*
}
reply_log
reject
}
Thank you very much and sorry for my english.
:: Ana Gallardo Gómez ::
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Which attribute should I be using to store the same 'from client' that the
radius.log is storing?
I think that what you want is clientname %C
:: Ana Gallardo Gómez ::
-
List info/subscribe/unsubscribe? See http
- Freeradius 1.1.7
- Debian Sarge (kernel 2.6.18-5-686)
- IBM x3550
Hello!
When I run freeradius in debug mode the Access-Reject is sent after the delay
time indicated by the reject_delay setting.
When I run freeradius as a daemos, the Access-Reject is delayed too many time
when reject_delay
I think you have to use the attribute Stripped-User-Name to authenticate the
user. Date: Wed, 24 Jan 2007 14:21:59 +0800 From: [EMAIL PROTECTED] To:
freeradius-users@lists.freeradius.org Subject: Proxying based on SSID Hi,
Sorry if the questions have been asked. I have done a lot of searches,
Hello!I want to use Freeradius as a proxy Radius server, and I think that my
Freeradius don´t have to do authorize and authenticate: my Freeradius have to
proccess request with realm @unex.es, the others request have to be proxyed.
My configuration is:radiusd.conf:
authorize {
preprocess
OK, use the perl module to re-write the attribute. There is an
example.pl distributed with the server that should be a good start.
Alan DeKok.
I 'm trying to use the perl module to authenticate users removing white spaces
from NT-Password. This is my remove_white_spaces.pl:
use
Date: Thu, 28 Dec 2006 08:44:22 -0800
From: [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Subject: Re: problem with NT-Password and LDAP
Ana Gallardo Gómez wrote:
Well, I can not modify the LDAP server, I only can use
Ana Gallardo Gómez wrote:
Hello, my problem is, i have a Freeradius server that retrieves the
authentication information from an OpenLDAP server; in this server the
NT-Password atributte has 252 characters (32 characters from NT-hash +
white spaces)
Why not just update the entries
Hello, my problem is, i have a Freeradius server that retrieves the
authentication information from an OpenLDAP server; in this server the
NT-Password atributte has 252 characters (32 characters from NT-hash + white
spaces), and the NT-Password generated in ms-chap has 32 characters. How can I
Sorry for my english...I had the same problem with Freeradius-OpenSSL. I´m running a Debian Sarge 3.1. My installation is:/usr/local/openssl -- OpenSSL binaries/usr/local/radius -- Freeradius binaries/usr/local/freeradius-1.1.3 -- Freeradius source/usr/local/openssl-0.9.7k -- OpenSSL
15 matches
Mail list logo