radius_xlat:
'/home/barry/log/radius/radacct/165.146.6.102/reply-detail-20070121'
rlm_detail:
/home/barry/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d
expands to
/home/barry/log/radius/radacct/165.146.6.102/reply-detail-20070121
modcall[post-auth]: module reply_log returns ok
That is very odd.
I note you are running custom SQL queries against a union of a password
table and a stored procedure - it is possible something occurs inside
the stored proc that causes a backend to lock up or start behaving
abnormally.
What happens if you execute:
SELECT -1 AS id,
In the eap.conf, tls section, the comments say to use the 'CA_path'
variable in the radiusd.conf file to indicate where the trusted CA
chain will reside. However, this variable isn't in the tls section of
the radiusd.conf file (it is in the LDAP section, but I'm pretty sure that
won't help me) or
Phil Mayers wrote:
That is very odd.
I note you are running custom SQL queries against a union of a
password table and a stored procedure - it is possible something
occurs inside the stored proc that causes a backend to lock up or
start behaving abnormally.
What happens if you execute:
Hi Alan,
Many thanks for your help.
I have followed all the instructions from http://deployingradius.com. I
do not know why I have had the CHAP authentication.
I would like to use MS-CHAP authentication instead of CHAP, and do you
have any tipps for me for this kind of setup (MS-CHAP)?
Any
Hi Alan and everyone,
In message [EMAIL PROTECTED], Alan DeKok
[EMAIL PROTECTED] writes
David Wood wrote:
I am the maintainer of the FreeBSD FreeRADIUS port starting from version
1.1.3. It's probably about time I revealed myself here.
Thanks. There's been the occasional question. Having
I'd like to implement pam_radius module on some of our
Linux boxes but I am worried about password
(pam_radius can only do PAP) being captured and
misused since the radius server is at central office
and clients are all over the place.
I read
Roberto wrote:
I had a fast look at the authentication gateway howto... Sorry, I do not
understand how can it help me...
I want to find a means to authenticate the wireless clients towards the
access point, not towards the rest of the - wired - network.
The wireless client must not be able to
FR: freeradius-1.1.2
OD: FreeBSD 6.0
trying to query LDAP for certain attribute.. if found, then proxy accounting
to other server if not store accounting locally.
trying using rlm_perl as below:-
i) radiusd.conf
perl y5perl {
module = /usr/local/etc/raddb/y5perl.pl
}
David Wood wrote:
I'm not saying that I've got everything yet, but I think the port is now
in good shape. If anyone wants to suggest further changes, or audits the
port and finds any problems, I'm listening. Patches are particularly
welcome, of course.
Thanks. Little changes like that can
Agent Smith wrote:
I'd like to implement pam_radius module on some of our
Linux boxes but I am worried about password
(pam_radius can only do PAP) being captured and
misused since the radius server is at central office
and clients are all over the place.
Don't worry.
I read
John Wan wrote:
I have followed all the instructions from http://deployingradius.com. I
do not know why I have had the CHAP authentication.
See the NAS documentation.
I would like to use MS-CHAP authentication instead of CHAP, and do you
have any tipps for me for this kind of setup
12 matches
Mail list logo