Alan DeKok wrote:
Mike O'Connor wrote:
I wrote the attached patch for Freeradius 1.1.7 to enabled calling
python in the post-proxy, it compiles but will not run when the hook is
listed in post-proxy because Freeradius complains that there is no
support for post-proxy in rlm_python.
Mike O'Connor wrote:
Maybe I'm not getting your but even the lastest cvs does not have any
post-proxy or post-auth support.
That's not what I meant.
My code added the post-proxy but when I tried to use it freeradius would
complain that rlm_python did not support being called from the
Hi,
I have a problem with the Filter-ID attribute :
When a switch (Enterasys) gets the filter-ID in an 'access-accept' reply,
its value is written twice :
.
AVP: l=6t=Service-Type(6): Framed-User(2)
AVP: l=39t=Filter-ID(11): Enterasys:version=1:policy=test-policy
Filter-ID:
Our Novell experts have looked into the LDAP database and found that the
affected accounts do indeed have the sasDefaultLoginSequence attribute, in fact
only a handful of accounts have it.
They are testing now. I will let you all know what happens.
---
Barry Dean
Networks Team
VM wrote:
I have a problem with the Filter-ID attribute :
When a switch (Enterasys) gets the filter-ID in an 'access-accept' reply,
its value is written twice :
Because you told the server to do that.
Run it in debugging mode to see why.
Do you know where this may come from ?
It's
Hello list,
doesn't freeradius-1.1.7 no longer compile on Debian sarge (oldstable)?
I get these errors on after ./configure and make:
[...]
Making all in rlm_perl...
make[6]: Entering directory
`/usr/local/src/freeradius-1.1.7/src/modules/rlm_perl'
/usr/local/src/freeradius-1.1.7/libtool
Hi,
Do I then remove ldap from the authorize section so that it doesn't call
it every packet? I did a bunch of testing and it seems that I have to
do that to reduce the number of calls to our eDirectory servers.
yes - only call it from the INNER check. otherwise you are in exactly
the same
This fixed the problem for these users. Thanks to the list, and special thanks
to Alan for solving this.
---
Barry Dean
Networks Team
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean, Barry
Sent: 13 November 2007 09:31
To: FreeRadius
oz wrote:
doesn't freeradius-1.1.7 no longer compile on Debian sarge (oldstable)?
I get these errors on after ./configure and make:
...
rlm_perl.c: In function `perl_xlat':
rlm_perl.c:658: parse error before `*'
The weird thing is that the typedef it's complaining about is defined
in
Thanks for your reply!
I did an apt-get dist-upgrade of the oldstable/sarge system to have the
latest versions of the sarge-packages. The compilation succeeded now!
Now I will see if I can do the transition from freeradius 1.0.0 to 1.1.7 ...
Oliver
Alan DeKok wrote:
oz wrote:
doesn't
Hi,
I'm new to Freeradius, and the concepts behind Radius and network
security in general also, so I'm not sure if this is normal or not. I've
configured Freeradius so that I can authenticate Windows XP clients on
our wireless network through a Linux server's /etc/passwd file.
The problem is
Eduardo Lima wrote:
Hi, I've been using Freeradius 1.1.3
Please upgrade to 1.1.7...
with PEAP/MSCHAPv2 authentication
with no problem. But now, I need to use it with LDAP too and it doesn't
work at all.
The client is windows xp without a domain. The LDAP is for the email
directory.
Allan Riordan Boll wrote:
The problem is that authenticating takes around 20 seconds. While
running the server in a terminal with the -X flag, I see that my Windows
XP client first makes one TLS request, then waits ~20 seconds, then
makes two more TLS requests and four TTLS requests all
Allan,
Maybe I missed it, but what client do you use? Windows does not yet
support TTLS natively.
Artur
On 13 Nov 2007, at 16:23, Alan DeKok wrote:
Allan Riordan Boll wrote:
The problem is that authenticating takes around 20 seconds. While
running the server in a terminal with the -X
Hi,
Windows doesn't natively, but with the help of SecureW2
(http://www.securew2.com) it does quite well. Install it and select it
as a EAP Type on the Authenication Tab when you setup your wireless
connection.
Cheers,
Rupes
On 13/11/2007, Artur Hecker [EMAIL PROTECTED] wrote:
Allan,
Maybe
Maybe I missed it, but what client do you use? Windows does not yet
support TTLS natively.
yes sorry, i forgot to say. I am already using SecureW2 of course. And
it does work, it's just very slow at authenticating... Also, I'm using
FreeRADIUS 1.1.7.
If it works...
If it doesn't
On Wed, 2007-11-14 at 00:15 +0100, Allan Riordan Boll wrote:
Maybe I missed it, but what client do you use? Windows does not yet
support TTLS natively.
yes sorry, i forgot to say. I am already using SecureW2 of course. And
it does work, it's just very slow at authenticating... Also, I'm
Hi Alan
I think I have worked it out, some how I got my self confused during my
testing.
The model was there but I think each time I did not have everything
configured.
Thanks as always for your time
Mike
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi All,
Not sure if anyone else saw this.
I’m using freeradius-server-pre-2.0.0-8.1 and have got everything to work so
far. The backend is a MySQL database.
From a debug instance of FreeRADIUS, it reads
Sending Access-Accept of id 44 to 10.152.54.138 port 3129
Framed-IP-Address :=
19 matches
Mail list logo