Hi all,
Is possible to send some extra cisco VSA attribute in
AccessResponse Packet?
This is what i want to include in the packet:
Cisco VSA(252):
GWname/option//CalledID//CallerID/GWip:172
I tried in user file with the following configuration
but it doesnot seems to work
12122 Auth-Type :=
Hi All,
I'm keen to start using the rlm_perl module now that it has been made
stable. However I find that the documentation relating to the module is
sparse. Is there any official documentation on this module that anyone
knows of? I would also like to know whether the perl module loaded is
On Thursday 16 February 2006 11:20, [EMAIL PROTECTED] wrote:
Hi All,
I'm keen to start using the rlm_perl module now that it has been made
stable. However I find that the documentation relating to the module is
sparse. Is there any official documentation on this module that anyone
knows of?
Dear All,
i would like to insert Accounting-Information in different tables for
different NASs.
Therefor i would use different sql-Instances and the acct_users file.
The instances would only differ in acct_tabl1 and acct_table2. I tryed
to set the variables in the sections of every instance
Mark Martinec wrote:
It would be helpful to document explicitly what comments in rlm_ldap.c
indicate:
* Module should default to LDAP authentication if no Auth-Type
* specified. Note that we do this ONLY if configured, AND we
* set the Auth-Type to our module
Hi Boian,
Thanks for the response. The example.pl is easy enough to understand. From
the rlm_perl source code am I to understand that the radiusd.conf
configuration defaults if written out would look something like:
perl INSTANCE {
module = /etc/raddb/example.pl
func_authorize =
Dear all,
The user gets logged out exactly after the time set in Session Time
Out.
But I am trying to create package like 4hours per day, 2 hours
perday.
If I put 4hours in Session time and after using 3 hours , if he
disconnects and then reconnects, he can again use 4 hours.
Is there a way
On Thursday 16 February 2006 12:54, [EMAIL PROTECTED] wrote:
Hi Boian,
Thanks for the response. The example.pl is easy enough to understand. From
the rlm_perl source code am I to understand that the radiusd.conf
configuration defaults if written out would look something like:
Yes it is
You can use daily limit with Session Timeout.
On 2/16/2006, Rupesh Amatya [EMAIL PROTECTED] wrote:
Dear all,
The user gets logged out exactly after the time set in Session Time
Out.
But I am trying to create package like 4hours per day, 2 hours
perday.
If I put 4hours in Session time and
Abdul Lateef [EMAIL PROTECTED] wrote:
This is what i want to include in the packet:
Cisco VSA(252):
GWname/option//CalledID//CallerID/GWip:172
Ok...
I tried in user file with the following configuration
but it doesnot seems to work
12122 Auth-Type := Login-User
Andreas Engler [EMAIL PROTECTED] wrote:
Is there a possibility to set the variables acct_table1 and acct_table2
in the sections for the different instances in radiusd.conf? Or have i
to provide for every instance an own sql.conf.
I think you have to have multiple SQL instances.
Or, you
Rupesh Amatya [EMAIL PROTECTED] wrote:
If I put 4hours in Session time and after using 3 hours , if he
disconnects and then reconnects, he can again use 4 hours.
Is there a way that he can no more log in after he uses 4 hours/day ?
rlm_counter.
Alan DeKok.
-
List
Hi all,
I'm at a bit of a loss. I'm currently trying to load test the
authentication proxy performance of freeRADIUS 1.0.1 in preparation for
a deployment this weekend.
Unfortunately, I'm running into this error Error: FATAL! Server is too
busy to process requests.
My scenario is:
Mitchell, Michael J [EMAIL PROTECTED] wrote:
I'm at a bit of a loss. I'm currently trying to load test the
authentication proxy performance of freeRADIUS 1.0.1 in preparation for
a deployment this weekend.
Unfortunately, I'm running into this error Error: FATAL! Server is too
busy to
On Wed, February 15, 2006 1:15 pm, Alan DeKok wrote:
Jay Lee [EMAIL PROTECTED] wrote:
My last task is to allow Wireless authentication only to
members of a given LDAP Group.
... i.e. to reject wireless for everyone else.
So the glass is half empty? :-)
If I empty out /etc/raddb/users
It seems that the features says it can be done, but I have no idea how.
Basically I'm just wondering if I can take the service-name of the PPPoE
server and have freeradius proxy out depending on which service name.
Does anybody have any suggestions on where I might start looking for
= 0x020e01616e6f6e796d6f7573
Message-Authenticator = 0x61efabf1e39ae3a5983e1b7c7ed39037
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module preprocess returns ok for request 0
radius_xlat: '/var/log/radius/radacct/192.168.0.1/auth-detail-20060216
Title: dictionary.cablelabs[168]: dict_addvalue: value name too long
Hello,
In order to correctly link to libssl.so.0.9.7 and libcrypto.so.0.9.7 at run time. I set LDFLAGS=-R/usr/local/openssl-0.9.7/lib at compile time. When I execute the bin I get the following error:
Thu Feb 16 18:39:40
Johan Arens [EMAIL PROTECTED] wrote:
I cannot authenticate with the radius, I got this error when the handheld
try to auth :
Wed Feb 15 15:27:42 2006 : Info: Ready to process requests.
Wed Feb 15 15:28:21 2006 : Error: TLS_accept:error in SSLv3 read client
certificate A
Wed Feb 15
Ryan Melendez [EMAIL PROTECTED] wrote:
Thu Feb 16 18:39:40 2006 : Error: Errors reading dictionary: dict_init:
//usr/local/share/freeradius/dictionary.cablelabs[168]: dict_addvalue:
value name too long
The only way you get that error is if you're running an old version
of FreeRADIUS against
Mark Martinec [EMAIL PROTECTED] wrote:
In my case the solution was to replace the:
authenticate {
...
Auth-Type LDAP {...}
Which worked because of a bug in the server. It was a bug, no question.
It would be helpful to document explicitly what comments in rlm_ldap.c
indicate:
As
I was on the impression that radiusd -X would produce the debug log, I pasted it in the previous mail.
On 2/16/06, Alan DeKok [EMAIL PROTECTED] wrote:
Johan Arens [EMAIL PROTECTED] wrote: I cannot authenticate with the radius, I got this error when the handheld try to auth : Wed Feb 15 15:27:42
Hey Alan,
I am using 1.1.0. Sorry I left that out.
read_config_files: reading dictionary
Errors reading dictionary: dict_init:
//usr/local/share/freeradius/dictionary.cablelabs[168]: dict_addvalue: value
name too long
Errors reading radiusd.conf
[andreadoria:520 ~] /usr/local/sbin/radiusd -v
Hi Folks,
I've been tasked at my work w/ getting a radius backend working with our Cisco
3000 concentrators to do certificate auth. We're currently running an old
version of gnu radius for our standard radius auth, but I'd like to move to
freeradius so that we can eventually use some features
Ryan Melendez [EMAIL PROTECTED] wrote:
I am using 1.1.0. Sorry I left that out.
That message isn't produced when running the stock 1.1.0. What else
is going on in your machine? Do you have multiple versions of
FreeRADIUS installed?
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Johan Arens [EMAIL PROTECTED] wrote:
I was on the impression that radiusd -X would produce the debug log, I
pasted it in the previous mail.
shrug The message I responded to did not have the debug log.
If you're not going to supply it, then good luck solving the
problem. I wish you the
Geoff Silver [EMAIL PROTECTED] wrote:
Forgive me if I'm missing something incredibly obvious, but I absolutely can't
get auth to work. ever. For starters, here's what I see when running
'radiusd -AX':
rad_recv: Access-Request packet from host 127.0.0.1:34193, id=136, length=61
Johan Arens wrote:
Hi
I cannot authenticate with the radius, I got this error when the
handheld try to auth :
Wed Feb 15 15:27:42 2006 : Info: Ready to process requests.
Wed Feb 15 15:28:21 2006 : Error: TLS_accept:error in SSLv3 read
client certificate A
Wed Feb 15 15:28:21 2006 :
The debug log has been attached at the end of my first message.On 2/16/06, Alan DeKok [EMAIL PROTECTED] wrote:
Johan Arens [EMAIL PROTECTED] wrote:
I was on the impression that radiusd -X would produce the debug log, I pasted it in the previous mail.shrugThe message I responded to did not have
of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module preprocess returns ok for request 0
radius_xlat: '/var/log/radius/radacct/192.168.0.1/auth-detail-20060216'
rlm_detail:
/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands
to /var/log/radius/radacct
On Thu, February 16, 2006 11:07 am, Alan DeKok wrote:
Mitchell, Michael J [EMAIL PROTECTED] wrote:
I'm at a bit of a loss. I'm currently trying to load test the
authentication proxy performance of freeRADIUS 1.0.1 in preparation for
a deployment this weekend.
Unfortunately, I'm running into
31 matches
Mail list logo
