Hi All,
I've installed FreeRadius 2.2.0 in Oracle Solaris 10 1/13, and I'm getting Access-Reject when tried using 'radtest' tool. When debugging is enabled I'm getting the following message
Debug: ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user
I've... (0 Replies)
Hello,
I am trying to authenticate through PEAP/mschap with freeradius 2.x and Active Directory.
I have followed this guide: Deploying RADIUS: Configuring Authentication with Active Directory
wbinfo works:
# wbinfo -a LOGIN%PASSWORD
plaintext password authentication failed
Could not... (0 Replies)
I have an RS/6000 running AIX 5.3. I would like to get either dhcp client working or assigning it an ip would be fine as well. I have tried using smit to do it many times trying different things, and I can get an ip assigned but it doesn't communicate with the network or internet. I haven't been... (3 Replies)
HEllo,
I try to Launch OOO, but I have X configuration problem.
I 'm searching in man pages but if someone can help me...
Of course I set the DISPLAY as explain in the man page but with no more result: setenv DISPLAY myws:0
Thanks in advance (1 Reply)
Can anyone please tell me anything about the following:
AIX O/S - IBM RS6000 server
I want to know where I can go to check and see how much RAM is intalled in the server, how many Processors are installed in the server, and how I can run a sar command to show me processor statistics?
I... (4 Replies)
radiusd.conf(5) FreeRADIUS configuration file radiusd.conf(5)NAME
radiusd.conf - configuration file for the FreeRADIUS server
DESCRIPTION
The radiusd.conf file resides in the radius database directory, by default /etc/raddb. It defines the global configuration for the FreeRA-
DIUS RADIUS server.
CONTENTS
There are a large number of configuration parameters for the server. Most are documented in the file itself as comments. This page docu-
ments only the format of the file. Please read the radiusd.conf file itself for more information.
The configuration file parser is independent of the server configuration. This means that you can put almost anything into the configura-
tion file. So long as it is properly formatted, the server will start.
When the server parses the configuration file, it looks only for those configurations it understands. Extra configuration items are
ignored. This "feature" can be (ab)used in certain interesting ways.
FILE FORMAT
The file format is line-based, like many other Unix configuration files. Each entry in the file must be placed on a line by itself,
although continuations are supported.
The file consists of configuration items (variable = value pairs), sections, and comments.
Variables
Variables can be set via:
name = value
Single and double-quoted strings are permitted:
string1 = "hello world"
string2 = 'hello mom'
Sections
A section begins with a section name, followed on the same line by an open bracket '{'. Section may contain other sections, com-
ments, or variables. Sections may be nested to any depth, limited only by available memory. A section ends with a close bracket
'}', on a line by itself.
section {
...
}
Sections can sometimes have a second name following the first one. The situations where this is legal depend on the context. See
the examples and comments in the radiusd.conf file for more information.
section foo {
...
}
Comments
Any line beginning with a (#) is deemed to be a comment, and is ignored. Comments can appear after a variable or section defini-
tions.
# comment
foo = bar # set variable 'foo' to value 'bar'
section { # start of section
...
} # end of section
Continuations
Long lines can be broken up via continuations, using '' as the last character of the line. For example, the following entry:
foo = "blah
blah
blah"
will set the value of the variable "foo" to "blah blah blah". Any CR or LF is not turned into a space, but all other whitespace is
preserved in the final value.
REFERENCES
The value of a variable can reference another variable. These references are evaluated when the configuration file is loaded, which means
that there is no run-time cost associated with them. This feature is most useful for turning long, repeated pieces of text into short
ones.
Variables are referenced by ${variable_name}, as in the following examples.
foo = bar # set variable 'foo' to value 'bar'
who = ${foo} # sets variable 'who' to value of variable 'foo'
my = "${foo} a" # sets variable 'my' to "bar a"
If the variable exists in a section or subsection, it can be referenced as ${section.subsection.variable}. Forward references are not
allowed. Relative references are allowed, by pre-pending the name with one or more period.
blogs = ${.foo}
Will set variable blogs to the value of variable foo, from the current section.
blogs = ${..foo}
Will set variable blogs to the value of variable foo, from the section which contains the current section.
blogs = ${modules.detail.filename}
Will set variable blogs to the value of variable filename, of the detail module, which is in the modules section of the configuration file.
Properties of anonymous parent sections may also be referenced, currently name and instance are supported.
modules { example foo { file = ${.:name} } } Will set variable file to the name of the
containing section (example).
modules { example foo { file = ${.:instance} } } Will set variable file to the instance
name of the containing section (foo).
modules { example foo { file = ${..:name} } } Will set variable file to the name of the
parent of the containing section (modules).
FILES
/etc/raddb/radiusd.conf
SEE ALSO radiusd(8)unlang(5)AUTHOR
Alan DeKok <aland@freeradius.org>
28 Jun 2013 radiusd.conf(5)