Igor wrote:
>I have tried 2.1.7 and got same error. I will try to compile it with
>--enable-developer and see if i can find out anything from gdb output.
>I realy don't know why would this happen because exactly the same setup worked
>on
>older releases. All i did was to compile the new version (
On Sat, 25 Jul 2009 12:26:42 , sent:
>
>
>On Sat, 25 Jul 2009 00:01 , 'Garber, Neal' neal.gar...@energyeast.com> sent:
>
>>Igor: Can you rebuild FR and look at the output of rlm_perl on
>>your system to see if you see similar errors?
>
I have tried
On Sat, 25 Jul 2009 00:01 , 'Garber, Neal' sent:
>Igor: Can you rebuild FR and look at the output of rlm_perl on
>your system to see if you see similar errors?
I will setup testing 2.1.6 freeradius and try the same configuration on it.
After that i will setup 2.1.7pre and try
> Two perl instances running different perl scripts! I would suggest
> following instructions in doc/bugs to find out what is causing the
> segfault.
rlm_perl is acting very strangely on my 2.1.6 test system (beyond what
I've already mentioned). I have two instances of a
-include-dir=/usr/kerberos/include \
> --with-rlm-krb5-lib-dir=/usr/kerberos/lib \
> --with-logdir=/var/log/radius
Slackware 12.1, perl 5.8.7.
I am afraid I can't emulate this. test1 and test2 run copies of
example.pl. I have edited them so they are not identical (just in case).
Res
Garber, Neal wrote:
> Igor,
>
> What version of perl and what O/S are you using? I'm using FreeBSD 7.2 with
> perl 5.8.9. The reason I hadn't submitted this sooner is I wanted to rule
> out an issue with perl (our Productions servers are running an older version
> of FreeBSD and perl).
perl, v
Igor,
What version of perl and what O/S are you using? I'm using FreeBSD 7.2 with
perl 5.8.9. The reason I hadn't submitted this sooner is I wanted to rule out
an issue with perl (our Productions servers are running an older version of
FreeBSD and perl).
-
List info/subscribe/unsubscribe? Se
Ivan Kalik wrote:
>> It ends with freeradius crashing. If i disable all other perl calls and
>> leave only dummy.pl works with no problems. Same goes for other way
>> around. Basicaly, any combination that involves only one perl script
>> works without any problems. If i use two perl scripts in a
Here's a small excerpt from debug output I have showing this problem:
Tue Jul 21 09:32:36 2009 : Error: rlm_perl: perl_embed:: module =
/usr/local/etc/raddb/write_log_data.pl , func = post_auth_reject exit status=
Undefined subroutine &main::post_auth_reject called.
Segmentation fault:
> It ends with freeradius crashing. If i disable all other perl calls and
> leave only dummy.pl works with no problems. Same goes for other way
> around. Basicaly, any combination that involves only one perl script
> works without any problems. If i use two perl scripts in any combination
> freerad
arber=energyeast@lists.freeradius.org]
On Behalf Of Igor Smitran
Sent: Friday, July 24, 2009 8:30 AM
To: freeradius-users@lists.freeradius.org
Subject: rlm_perl problems]
I am using Freeradius 2.1.6.
I have a working setup of freeradius with perl scripts inside authorize
and accounting sec
Ivan Kalik wrote:
>> perl perl_script_1 {
>> module = ${confdir}/config_dialup/perl_script_1.pl
>> func_authorize = authorize_check_username
>> func_accounting = accounting_check_username
>> }
>>
>> perl perl_script_2 {
>>
>> module = ${confdir}/config_dialup/perl_
> Ivan Kalik wrote:
>> Have you defined func_post_auth?
>>
>> Ivan Kalik
>> Kalik Informatika ISP
>>
> Left everything by default. Made script by using example.pl as template.
> Both scripts are looking exactly the same, except that i don't use
> default function names for perl_script_1.
>
> perl p
Ivan Kalik wrote:
> Have you defined func_post_auth?
>
> Ivan Kalik
> Kalik Informatika ISP
>
Left everything by default. Made script by using example.pl as template.
Both scripts are looking exactly the same, except that i don't use
default function names for perl_script_1.
perl perl_script_1
ction i get errors in log and freeradius dies.
>
> Error i get is:
> Error: rlm_perl: perl_embed:: module =
> /etc/raddb/config_dialup/perl_script_2.pl , func = post_auth exit
> status= Undefined subroutine &main::post_auth called.
Have you defined func_post_auth?
Ivan Kalik
Kali
freeradius dies.
Error i get is:
Error: rlm_perl: perl_embed:: module =
/etc/raddb/config_dialup/perl_script_2.pl , func = post_auth exit
status= Undefined subroutine &main::post_auth called.
My perl setup is like this:
perl perl_script_1 {
module = ${confdir}/config_dialup/perl_script_
adius
> and then do 'show processlist' on the MySQL server I see no connections
> from the radius server. If I then send a single update from radclient I
> get a connection in show processlist, and a timely response to my
> request.
You might try the rlm_perl module from
I'm having a few issues with FreeRadius 2.1.4 (2.1.6 isn't in ports yet)
and MySQL 5.1 on FreeBSD 6.2.
Specifically, I am using the CLONE method in my perl script to create my
database handles every time a new thread is spawned. If I start radius
and then do 'show processlist' on the MySQL server
> I browsed the mailing list for possible solutions to the problem I have
> but unfortunately I didn't find any (or something I missed I dunno)
>
> We have this Cisco ISG 7301 router that we are using that are passing the
> Remote-ID av pair as its User-Name (just a copy not that it matters)
> Now,
then passing the result string to
> ldap for authentication? Or will we use ldap inside rlm_perl?
First, define what you want to do. Do you want to treat that string
as a user id in LDAP, and do uid lookups based on it, or do you want
to do something else?
> Just to add, we also want t
s substring
is always fixed (18 bytes) so we only want the part after 18 bytes.
is it possible to parse this string in perl then passing the result string to
ldap for authentication? Or will we use ldap inside rlm_perl?
Just to add, we also want to check the first 4 bytes (079d) if it is not
i threaded, then rlm_perl will also be and so you
should create all resources which should be private (DB / File handles
etc) in the CLONE subroutine of your rlm_perl module. This way each
thread gets its separate DB handle
[as far as I can remember you Perl wasn't multi threaded but anywa
To: FreeRadius users mailing list
Subject: RE: rlm_perl DBI problems
> Back to my problem with perl
> Then I comment my own module rejectlog in sites-enable/mysite FR begin to
> work fine at least 18 hours.
> Some ideas why it can bring an error in DBI if it's sub function in perl
&
> Back to my problem with perl
> Then I comment my own module rejectlog in sites-enable/mysite FR begin to
> work fine at least 18 hours.
> Some ideas why it can bring an error in DBI if it's sub function in perl
> don't use DBI at all?
Please don't ask perl debugging questions on this list.
> An
Hi.
Back to my problem with perl
Then I comment my own module rejectlog in sites-enable/mysite FR begin to
work fine at least 18 hours.
Some ideas why it can bring an error in DBI if it's sub function in perl
don't use DBI at all?
Any other offers how to log reject users in special format?
I do
dorkusmonkey wrote:
> I am running FreeRADIUS Version 2.1.5, for host i686-pc-linux-gnu,
> have successfully configured rlm_perl and have it working with a
> modified example.pl file. I have noticed that the authorize callback
> in example.pl gets called before the authenticat
I am running FreeRADIUS Version 2.1.5, for host i686-pc-linux-gnu,
have successfully configured rlm_perl and have it working with a
modified example.pl file. I have noticed that the authorize callback
in example.pl gets called before the authentication callback. From
http://www.mail
(2.2.x or
something)?
They will show up in the next release, whatever that is.
i.e. "next after the changes have been made".
I suppose Apostolos Pantsiopoulos ment the multiple rlm_perl
instances ( modules { perl inst1 { } perl inst2 { } } capability
inside each thread, that we
next release, whatever that is.
i.e. "next after the changes have been made".
I suppose Apostolos Pantsiopoulos ment the multiple rlm_perl instances
( modules { perl inst1 { } perl inst2 { } } capability inside each
thread, that we discussed a lot some time ago. Just to clarify.
Apostolos Pantsiopoulos wrote:
> If any changes are to be made to the current
> implementation to support multiple interpreters (one per thread)
> would they show up in a 2.1.x release or a future one (2.2.x or something)?
They will show up in the next release, whatever that is.
i.e. "next af
manages min/max spare threads, idle threads, etc.
I hope this implementation will satisfy Borislav too. Will he be
able to
instantiate different perl scripts for different needs?
So, when do I start testing :)
Just to say, we're currently using FreeRadius 2.1.3 with rlm_perl in a
project curr
Hi,
> Ok, but if I do not filter out the extra slashes then after the perl
> module returns, freeradius gives the error that the User-Name field does
> not match the peap identity. Then it shows the User-Name with too many
> slashes (four slashes). If, in my perl module, I filter out two slash
On Apr 21, 2009, at 5:21 AM, t...@kalik.net wrote:
I think I may have found a bug in rlm_perl?
No, you broke it.
#The following line cleans two of the slashes
"\\"
out of the user-name before we return from the
#perl module. These two s
> I think I may have found a bug in rlm_perl?
No, you broke it.
> #The following line cleans two of the slashes "\\"
> out of the user-name before we return from the
> #perl module. These two slashes get added in. I&#
Josh Hiner wrote:
I think I may have found a bug in rlm_perl? I have written script with
the aid of another freeradius list member that checks to see if a user
is in a certain samba windows group. If they are not in the group (the
wireless group) the module rejects the login. The module works
I think I may have found a bug in rlm_perl? I have written script with
the aid of another freeradius list member that checks to see if a user
is in a certain samba windows group. If they are not in the group (the
wireless group) the module rejects the login. The module works perfectly
except
ipts for different needs?
> >
> > So, when do I start testing :)
Just to say, we're currently using FreeRadius 2.1.3 with rlm_perl in a
project currently in active development, and having read this i'm
holding off upgrading to 2.1.4 as we also use the multiple perl threads
fu
Borislav Dimitrov wrote:
> Sacrificing the *_clones flexibility for lower memory footprint, better
> performance and more importantly code is certainly worth doing it, if
> people are still able to have multiple rlm_perl instances.
If we update the module to have one Perl thread p
I hope this implementation will satisfy Borislav too. Will he be
able to
instantiate different perl scripts for different needs?
So, when do I start testing :)
Hi,
Yes, being able to instantiate and use several rlm_perl instances with
different scripts to take care of different
the
multiple instances feature of rlm_perl.
We don't need that limit. The server should not be running more Perl
threads than system threads. It also should not be running less Perl
threads than system threads.
My point exactly.
It should be running one Perl thread per system t
ing support for tagged
> attributes in rlm_perl?
Nope. As always, patches are welcome.
> 3. Is there any workaround to make it work?
Edit the source code.
> 4. Which of these modules: rlm_python, rlm_exec, rlm_ user programmable> support tagged attributes?
The python module looks lik
the
> multiple instances feature of rlm_perl.
We don't need that limit. The server should not be running more Perl
threads than system threads. It also should not be running less Perl
threads than system threads.
It should be running one Perl thread per system thread. The server
c
From my point of view we should have pool of perl clones per each
module instance.
This way we could have multiple perl instances (each with its own perl
script to run).
Limiting on perl clone or interp per server thread will limit the
multiple instances feature of rlm_perl.
Again playing
Yes, that would be great. One perl interpreter
per freeradius thread, that is. And I suppose the
CLONE function would work again as expected (i.e. each
freeradius thread would have its own perl interpreter and
each script relaying on this interpreter would have its
own connection to the DB). And t
On Thu, Apr 16, 2009 at 1:34 PM, Alan DeKok wrote:
> Alexandr Kovalenko wrote:
>> I've already asked about the very same problem with tagged attributes
>> and rlm_perl in FreeRADIUS 1.1.7, and Ivan Kalik told
>> me that he tested it on 2.1.4, so I've upgraded
Alexandr Kovalenko wrote:
> I've already asked about the very same problem with tagged attributes
> and rlm_perl in FreeRADIUS 1.1.7, and Ivan Kalik told
> me that he tested it on 2.1.4, so I've upgraded to new version:
It doesn't support tagged attributes, either.
oblem with tagged attributes
> and rlm_perl in FreeRADIUS 1.1.7, and Ivan Kalik told
> me that he tested it on 2.1.4, so I've upgraded to new version:
>
> FreeRADIUS Version 2.1.4, for host i386-portbld-freebsd7.1, built on
> Apr 16 2009 at 10:42:09
>
> But the problem persist
Hello!
I've already asked about the very same problem with tagged attributes
and rlm_perl in FreeRADIUS 1.1.7, and Ivan Kalik told
me that he tested it on 2.1.4, so I've upgraded to new version:
FreeRADIUS Version 2.1.4, for host i386-portbld-freebsd7.1, built on
Apr 16 2009 at 10:
Hi,
On 15.04.2009, at 20:31, Alan DeKok wrote:
Borislav Dimitrov wrote:
Anyways my main trouble is being unable to use multiple rlm_perl
instances like this (I've put the comments to illustrate the
flexibility
of using *_clones which is now gone):
Ah... OK. That was *not* the inte
Borislav Dimitrov wrote:
> Anyways my main trouble is being unable to use multiple rlm_perl
> instances like this (I've put the comments to illustrate the flexibility
> of using *_clones which is now gone):
Ah... OK. That was *not* the intent of the change. I'll take a lo
Apostolos Pantsiopoulos wrote:
> I understand that there may some benefits in the current
> implementation (2.1.x) such as less threads, smaller memory
> footprint etc. but why change something that has been tested
> and working in the first place?
A quest to make it better. If we were satisfie
Hi,
The lack of the _clones options is not my (primary) problem but I
think it was a good functionality. I understand that simplifying,
refactoring and optimizing the code is important and that the changes
done are probably for the better but being unable to instantiate
several rlm_perl
rful product - there's no question why you're
> No 1! For the past years of using and developing rlm_perl modules for
> FreeRADIUS, I've only been astonished and happy because of the new
> functionalities etc that the development team have been adding to the
> new releases.
Yes this was the main reason but there are others too.
С поздрави
Борислав Димитров
e-mail: b.dimit...@ngsystems.net
GSM: 0889 28 54 57
NG Systems
Лавеле 32, ет: 4,
София, България
On 15.04.2009, at 11:06, Apostolos Pantsiopoulos wrote:
Were you also depending on the rlm_perl threads to
question
why you're No 1! For the past years of using and developing rlm_perl
modules for FreeRADIUS, I've only been astonished and happy because of
the new functionalities etc that the development team have been adding
to the new releases. This all ended with this crippling of the
Were you also depending on the rlm_perl threads to
make connections to multiple DBs? I know that I can
make an array of db handlers within one perl thread
and use them interchangeably, but the functionality
I had in the 2.0.x release where every perl thread
had its own connection to the DBs and
question
why you're No 1! For the past years of using and developing rlm_perl
modules for FreeRADIUS, I've only been astonished and happy because of
the new functionalities etc that the development team have been adding
to the new releases. This all ended with this cripplin
Hello Freeradius-users,
FreeRADIUS Version 2.1.5
(it was downloaded as 2.1.4, but it writes about itself as 2.1.5)
Portion from "radiusd -X" output
Module: Linked to module rlm_perl
Module: Instantiating erxlogontime
perl erxlogontime {
module = "/usr/local/freer
> Or, the module could be updated to have one
>> perl interpreter per child thread.
>
> This requires that I alter the rlm_perl module code, right?
Yes.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
bug mode it what that time will work
> normally, the truth only any.
>
>
>
> - Original Message -
> From: "Anatoly S. Zimin"
> To: "FreeRadius users mailing list"
> Sent: Tuesday, April 07, 2009 3:45 PM
> Subject: Re: Problem with rlm_perl
&
.
- Original Message -
From: "Anatoly S. Zimin"
To: "FreeRadius users mailing list"
Sent: Tuesday, April 07, 2009 3:45 PM
Subject: Re: Problem with rlm_perl
Привет!
На самом деле, весьма _неудобно_ искать проблемы просто по дебагу +
конфиг.
Уж лучше описать её хоть на &qu
Привет!
На самом деле, весьма _неудобно_ искать проблемы просто по дебагу + конфиг.
Уж лучше описать её хоть на "ломаном" англ.
Это так отступление...
А вообще, у rlm_perl весьма много глюков.
Например при работе с разными модулями, типа IO::Socket::.
Попробуйте все засунуть в о
entry DEFAULT at line 7
[files] users: Matched entry DEFAULT at line 19
++[files] returns ok
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user. Authentication
may fail because of this.
++[pap] returns noop
Found Auth-Type = PPPOE_AUTH
+- entering
entry DEFAULT at line 7
[files] users: Matched entry DEFAULT at line 19
++[files] returns ok
++[logintime] returns noop
[pap] WARNING! No "known good" password found for the user. Authentication
may fail because of this.
++[pap] returns noop
Found Auth-Type = PPPOE_AUTH
+- entering
mysql server from the moment radiusd was up.
Yes.
Was the behavior of rlm_perl altered in any way? I want to have multiple
instances of rlm_perl so that I can connect to different databases
simultaneously and spread the load.
The perl module no longer manages its own thread pool. This
mysql server from the moment radiusd was up.
Yes.
Was the behavior of rlm_perl altered in any way? I want to have multiple
instances of rlm_perl so that I can connect to different databases
simultaneously and spread the load.
The perl module no longer manages its own thread pool. This
0 connections to my
> mysql server from the moment radiusd was up.
Yes.
> Was the behavior of rlm_perl altered in any way? I want to have multiple
> instances of rlm_perl so that I can connect to different databases
> simultaneously and spread the load.
The perl module no lo
I updated my server from 2.0.x to 2.1.4
and found out that the rlm_perl config now resides
in the /module directory.
I noticed that the following directives :
max_clones = 10
start_clones = 5
min_spare_clones = 1
max_spare_clones = 5
max_request_per_clone
>[Update: fixed script so that it won't set incorrect attributes, but
>problem persist]
>
>I'm trying to set up FreeRADIUS with rlm_perl module to have ability
>to interoperate with our billing/provisioning system.
>
>FreeRADIUS version:
>
># radiusd -v
>rad
Hello
[Update: fixed script so that it won't set incorrect attributes, but
problem persist]
I'm trying to set up FreeRADIUS with rlm_perl module to have ability
to interoperate with our billing/provisioning system.
FreeRADIUS version:
# radiusd -v
radiusd: FreeRADIUS Version 1.1.7
On Mon, Mar 30, 2009 at 12:53 PM, Alexandr Kovalenko
wrote:
> On Mon, Mar 30, 2009 at 12:08 PM, wrote:
>>>Using perl at 0x592370
>>>rlm_perl: $VAR1 = {};
>>>rlm_perl: defined
>>>rlm_perl: Added pair ERX-Qos-Parameters = internet_tr_value 2097152
>&
On Mon, Mar 30, 2009 at 12:08 PM, wrote:
>>Using perl at 0x592370
>>rlm_perl: $VAR1 = {};
>>rlm_perl: defined
>>rlm_perl: Added pair ERX-Qos-Parameters = internet_tr_value 2097152
>>rlm_perl: Added pair ERX-Service-Activate = telesys (1048576)
>>rlm_p
>Using perl at 0x592370
>rlm_perl: $VAR1 = {};
>rlm_perl: defined
>rlm_perl: Added pair ERX-Qos-Parameters = internet_tr_value 2097152
>rlm_perl: Added pair ERX-Service-Activate = telesys (1048576)
>rlm_perl: Added pair ERX-Qos-Profile-Name = SP_Tele_Internet
>rlm_perl: A
Hello
I'm trying to set up FreeRADIUS with rlm_perl module to have ability
to interoperate with our billing/provisioning system.
FreeRADIUS version:
# radiusd -v
radiusd: FreeRADIUS Version 1.1.7, for host amd64-portbld-freebsd6.3,
built on Jan 15 2009 at 18:36:52
Perl version:
# pe
selinux was the culprit,
thank you very much!
On Wed, Jan 7, 2009 at 2:22 PM, nes pa wrote:
> I've changed the example.pl perl script so it 'use DBI;' to query a Sybase
> server via freetds.
>
> Any hints welcome for solution or better tools to debug/strace into the
> perl script.
>
>
>
>
>
>
>
hi,
do you have eg SELINUX running on this system? if so,
then it may be blocking access between the processes.
check your selinux log (or change the mode to permissive
and check logs!) and then edit the selinux config to allow
operation
alan
-
List info/subscribe/unsubscribe? See http://www.free
t;connect("dbi:Sybase:server=*", $user, $passwd,
{PrintError => 0});
Error: rlm_perl: perl_embed:: module = /etc/raddb/myperlscript.pm , func =
authenticate exit status= Unable for connect to server OpenClient message:
LAYER = (0) ORIGIN = (0) SEVERITY = (78) NUMBER = (41) Server **
Quoting t...@kalik.net:
Using rlm_perl, if a request is received and I want to accept the
login without performing any normal auth (in authorize()), what would
I need to return?
Auth-Type Accept.
Thanks Ivan. I eventually figured out by trial and error that the
following needs to be
>Using rlm_perl, if a request is received and I want to accept the
>login without performing any normal auth (in authorize()), what would
>I need to return?
>
Auth-Type Accept.
Ivan Kalik
Kalik Informatika ISP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
as a module in my radiusd.conf file.
>
> I don't file the rlm_perl*.so file in /usr/local/lib/ where all the other
> rlm_*.so files are located.
>
> What am I missing?
>
>
> Maybe you are missing development files for perl. Install them and then
> rebuild your freerad
On Dec 17, 2008, at 11:54 PM, al pat wrote:
I am trying to use perl module, but when I can't start my server.
I have put "perl" as a module in my radiusd.conf file.
I don't file the rlm_perl*.so file in /usr/local/lib/ where all the
other rlm_*.so files are located.
Hi,
>
> I have put "perl" as a module in my radiusd.conf file.
>
> I don't file the rlm_perl*.so file in /usr/local/lib/ where all the other
> rlm_*.so files are located.
>
> What am I missing?
have you edited experimental.conf to enable PERL an
Perhaps if I try another approach:
Using rlm_perl, if a request is received and I want to accept the
login without performing any normal auth (in authorize()), what would
I need to return?
Constructing the $RAD_REPLY packet is no problem.
What to return to force an Access-Accept has me
hi,
I am building freeradius 2.1.3 on ubuntu (configure/make/make install)
I am trying to use perl module, but when I can't start my server.
I have put "perl" as a module in my radiusd.conf file.
I don't file the rlm_perl*.so file in /usr/local/lib/ where all the othe
Greetings, and thanks to Ivan and Alan for their feedback.
I've been dumping variables, etc, in my rlm_perl script (using
Devel::Symdump and Data::Dumper) trying to figure out where to change
the Packet-Type from Access-Reject to Access-Accept without success.
I've also gon
Henry wrote:
> I'm wondering though: during that small window period when the
> Packet-Type is changed and returned, would it be possible that it would
> affect other sessions running concurrently (separate threads)?
No.
When you do an LDAP query for a request, or process a request through
Quoting t...@kalik.net:
So check the "circumstances" before changing the Packet-Type.
Of course, you are right :p, thanks.
I'm wondering though: during that small window period when the
Packet-Type is changed and returned, would it be possible that it
would affect other sessions running c
>Changing freeradius.internal Packet-Type from Access-Reject to
>Access-Accept would affect ALL logins - even logins which *should* be
>rejected.
>
>I'm referring to changing Access-Reject to Access-Accept under certain
>circumstances only -- not globally for all logins.
>
So check the "circumstan
Quoting t...@kalik.net:
Is there a way to change the reply from Access-Reject, to Access-Accept?
Change freeradius.internal attribute Packet-Type in Post-Auth-Type Reject
section.
Changing freeradius.internal Packet-Type from Access-Reject to
Access-Accept would affect ALL logins - even l
Quoting t...@kalik.net:
Is there a way to change the reply from Access-Reject, to Access-Accept?
There is a way to change the packet type but it is a bad idea. Placing
unauthorized users in something like a guest VLAN should be the part of
your NAS functionality, rather than (deliberately) bre
>Is there a way to change the reply from Access-Reject, to Access-Accept?
>
There is a way to change the packet type but it is a bad idea. Placing
unauthorized users in something like a guest VLAN should be the part of
your NAS functionality, rather than (deliberately) breaking
authentication on t
Greets,
Using freeradius 2.0.5 and rlm_perl.
Let's say we have a username which is locked in /etc/shadow.
Normal authentication will prevent this user from logging in.
I would like to override this behaviour in either authorize() or
post_auth() and allow the user to login (but with mod
Saeed Akhtar wrote:
> Hi all,
>I want to use perl for authorize and accounting function in
> freeradius. I have successfully configured perl. Now I have a little
> problem, I don't know how to tell freeradius that reply with
> Access-Accept message. Because rlm_module_ok tells that this module
Hi all,
I want to use perl for authorize and accounting function in freeradius. I
have successfully configured perl. Now I have a little problem, I don't know
how to tell freeradius that reply with Access-Accept message. Because
rlm_module_ok tells that this module executed successfully. Now I w
> I have problem in rlm_perl module I found a documentation which says
>that rlm_perl is not in default modules of freeradius so you have to add a
>value "rlm_perl" in src/modules/stable before configuring freeradius. I
>added that. Now in wiki of freeradius, I read rlm
Hi all,
I have problem in rlm_perl module I found a documentation which says
that rlm_perl is not in default modules of freeradius so you have to add a
value "rlm_perl" in src/modules/stable before configuring freeradius. I
added that. Now in wiki of freeradius, I read rlm_perl a
Eric Martell wrote:
> Also I followed everything in http://wiki.freeradius.org/Rlm_perl
You should add the "Auth-Type" text to the authenticate section of
both raddb/sites-available/default, and raddb/sites-available/inner-tunnel.
Alan DeKok.
-
List info/subscribe/unsubscr
Hi
I am having similar problems like this thread
http://lists.freeradius.org/mailman/htdig/freeradius-users/2008-August/msg00273.html
Also I followed everything in http://wiki.freeradius.org/Rlm_perl
Here is my radiusd -X log.
Please let me know if I miss anything.
Thanks and Regards
Sewell, Adam W wrote:
> Thanks for the help guys, but I don't think that's going to work
> for me. I was doing some testing today and it doesn't seem like
> I can add a filter-id to the access-accept packet from the
> post-auth function.
Uh... no. You can add almost anything to the Access-Accep
something here?
- Original Message -
From: [EMAIL PROTECTED]
Sent: Fri, 8/22/2008 3:10am
To: FreeRadius users mailing list
Subject: Re: NAS-IP-Address, rlm_perl, and loopback
Hi,
> Which explains what's going on. PEAP is really two things: an outer
> TLS session, and inner EAP-MSCHAPv2
301 - 400 of 812 matches
Mail list logo
