Shankar Ganesh wrote:
How can i make freeradius listen to different UDP ports?
Hi Shankar,
This is very clearly explained in the radiusd.conf configuration file.
Search for listen
regards,
Mike
-
List info/subscribe/unsubscribe? See
From: Guilherme FrancoSent:
Wednesday, 30 August 2006 10:05 AMTo:
freeradius-users@lists.freeradius.orgSubject: 4 servers
implementation
Please, anybody can help me?
Help you
with what? You'll need to be a bit more
specific.
-
List info/subscribe/unsubscribe? See
Please tell me, how can i write a module of my own in c.
Also, tell me how can i compile it and use with
freeradius(also say the
config file changes)
Take a look at:
src/modules/rlm_example
doc/module_interface
To get your module to be compiled with radiusd, either add it to
Yes, you certainly can. If you mean the same version, then its quite easy.
If you mean different versions, it's a little more involved, but still
possible.
Of course they must be running on different ports (eg 1645, 1646, 1647 and
1812, 1813, 1814).
You can specify different configuration
Hi Dennis,
First, before I forget again, this link:
http://www.freeradius.org/radiusd/doc/
Yep, same for me too..
Is it possible to do this?
network1 Client-IP-Address == 192.168.2.5
network1 Client-IP-Address == 192.168.2.6
network2 Client-IP-Address ==
Have you got core dumps enabled in radiusd.conf?
regards,
Mike
-Original Message-
From:
[EMAIL PROTECTED]
eeradius.org
[mailto:freeradius-users-bounces+mitchell.michael=bigpond.com@
lists.freeradius.org] On Behalf Of Qin Zhen
Sent: Thursday, 22 December 2005 1:12 PM
To:
Hi Frank,
Take a look at 'configurable_failover' in the doc directory. This describes
how to do what you want.
regards,
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Frank Bonnet
Sent: Friday, 16 December 2005 3:38 AM
To: FreeRadius
Hi Martin,
reply from Mitchell, Michael J [EMAIL PROTECTED]:
I've actually been looking at this over the weekend. Have
written some
code, but haven't tested it yet. I'm hoping to get to that today
sometime. I based it largely on what was done in the sql
module, so it
may need a
freeRADIUS *DOES* authorize a user prior to performing authentication.
I think your terminology is probably backwards. Perhaps you could tell us
more about what you want to achieve, and someone can help you more easily
without having to go back and forth with questions.
regards,
Mike
Yes, but you missed one important little detail...
use =~
not ==
and as Alan suggested, read the man page where you'll find all sorts of
usefull information like:
Attribute =~ Expression
As a check item, it matches if the request contains an
attribute which matches
Hi NanO,
You may want something like this. (there are probably other ways of
detecting the realm, but it will depend of which modules you are using in
authorize, and which order)..
In users:
DEFAULT User-Name =~ , Autz-Type := AUTZ_SQL1
DEFAULT User-Name =~ , Autz-Type := AUTZ_SQL2
Hi Christopher,
I do something like this (YMMV as I've made changes to the code to support
stuff I want to do, this could have been one of those changes? ;-) )
In acct_users:
DEFAULT Acct-Status-Type == Alive, Acct-Type := ACK
And in radiusd.conf:
modules {
...
always
I know I can configure which directories radusd uses in
radiusd.conf, but is there any way to make radiusd look in
/usr/radius/etc for radiusd.conf without rebuilding?
radiusd -d /usr/radius/etc/raddb
You could have trouble with the radius module libraries though. I see there
is a
Hi Marc,
can freeradius work as a radius server and at the same time
as a proxy radius server? if this is possible, has anyone
Yes.
found good links/resources on how to set this up?
Have you read the docs that come with freeradius? Looked at the example
configuration files? Done any
As you have observed, the first huntgroup that is matched will always be
used. Its not a bug, or a feature, its just the way it is ;-)
You can however specify more than one attribute to match per line, for
example:
xDSLNAS-IP-Address == 1.1.1.1, NAS-Port-Type == Async
AdminA
15 matches
Mail list logo