Where did you create the user and password cisco? A copy of your users configuration file would be great On Thu, Dec 10, 2009 at 12:05 PM, g <gerardocb@gmail.com> wrote:
Where did you create the user and password cisco?
A copy of your users configuration file would be great.
On Thu, Dec 10, 2009 at 11:03 AM, Alex Bahoor <alexbahoor@sbcglobal.net>wrote:
Alan,
Radius -X is always on, and I went through the clients.conf file. -Xgives a lot information, since you asked here is my understanding. I'm not a programmer so some of them are cryptic to me. I put in comments to what I think they are, but they are only guesses. I would be very thankful if you can shed lights on them.
Also, there is file experimental.conf stated in eap.conf, but did not exist. It may have some useful information.
root@Crest raddb]# radtest cisco cisco 127.0.0.1 200 testing123
Sending Access-Request of id 187 to 127.0.0.1 port 1812
User-Name = "cisco"
User-Password = "cisco"
NAS-IP-Address = 127.0.0.1
NAS-Port = 200
rad_recv: Access-Request packet from host 127.0.0.1 port 43663, id=187, length=57
User-Name = "cisco"
User-Password = "cisco"
NAS-IP-Address = 127.0.0.1
NAS-Port = 200
+- entering group authorize {...}
++[preprocess] returns ok ;what is preprocess and what does it do?
++[chap] returns noop ;I can tell that chap was not selected as aprotocol, right?
++[mschap] returns noop ;as above
[suffix] No '@' in User-Name = "cisco", looking up realm NULL ;why @ is expected in a name or password?
[suffix] No such realm "NULL" ;what this mean?
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP ;eap is not auth protocol.
++[eap] returns noop
++[unix] returns notfound ;what is this?
++[files] returns noop ?
++[expiration] returns noop ?
++[logintime] returns noop ?
[pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ;I do have a password (cisco).
++[pap] returns noop
No authenticate method (Auth-Type) configuration found for the request: Rejecting the user ;this look like authentication protocol is a must before the process can work, however, eap.conf file is there and eap is uncommented out with it’s arguments. ?
Failed to authenticate the user.
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject] expand: %{User-Name} -> cisco
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 5 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 5
Sending Access-Reject of id 187 to 127.0.0.1 port 43663
Waking up in 4.9 seconds.
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=187, length=20
[root@Crest raddb]# Cleaning up request 5 ID 187 with timestamp +411
Ready to process requests.
Rgrds,
Alex
-----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@ lists.freeradius.org [ mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org<freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org>] On Behalf Of Alan Buxey Sent: Thursday, December 10, 2009 2:07 AM To: FreeRadius users mailing list Subject: Re: Testing radius server
Hi,
Now I know it's a config issue in the clients.conf, as radtest is failing. I
set user name and password, but radius is sending a reject. This is the
first time I'm using radius. So please bear with me. Can some one mail me
example of the minimum required configuration that needed for the radius to
work, no EAP or MSCAP ..etc.
hey, guess what - 'radiusd -X' this will be far more useful than
throwing random recommendations to you.
have you followed basic guidance regarding hwo to use clients.conf
eg
testuser Cleartext-Password := "testpassword"
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4674 (20091209) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Gera _____ From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of gera Sent: Thursday, December 10, 2009 11:07 AM To: FreeRadius users mailing list Subject: Re: Testing radius server Where did you create the user and password cisco? in the /etc/raddb/clients.conf. A copy of your users configuration file would be great Which config files do you need, radiusd.conf, or clients.conf? There is also, /etc/raddb/users which I have not even touched, cuz I did not see it readily on the wiki, and I did not know about till now. I'm not clear on the purpose of the attachment you mailed? This file is not accessible: http://wiki.freeradius.org/FAQ Alex On Thu, Dec 10, 2009 at 12:05 PM, g <gerardocb@gmail.com> wrote: Where did you create the user and password cisco? A copy of your users configuration file would be great. On Thu, Dec 10, 2009 at 11:03 AM, Alex Bahoor <alexbahoor@sbcglobal.net> wrote: Alan, Radius -X is always on, and I went through the clients.conf file. -X gives a lot information, since you asked here is my understanding. I'm not a programmer so some of them are cryptic to me. I put in comments to what I think they are, but they are only guesses. I would be very thankful if you can shed lights on them. Also, there is file experimental.conf stated in eap.conf, but did not exist. It may have some useful information. root@Crest raddb]# radtest cisco cisco 127.0.0.1 200 testing123 Sending Access-Request of id 187 to 127.0.0.1 port 1812 User-Name = "cisco" User-Password = "cisco" NAS-IP-Address = 127.0.0.1 NAS-Port = 200 rad_recv: Access-Request packet from host 127.0.0.1 port 43663, id=187, length=57 User-Name = "cisco" User-Password = "cisco" NAS-IP-Address = 127.0.0.1 NAS-Port = 200 +- entering group authorize {...} ++[preprocess] returns ok ;what is preprocess and what does it do? ++[chap] returns noop ;I can tell that chap was not selected as a protocol, right? ++[mschap] returns noop ;as above [suffix] No '@' in User-Name = "cisco", looking up realm NULL ;why @ is expected in a name or password? [suffix] No such realm "NULL" ;what this mean? ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ;eap is not auth protocol. ++[eap] returns noop ++[unix] returns notfound ;what is this? ++[files] returns noop ? ++[expiration] returns noop ? ++[logintime] returns noop ? [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ;I do have a password (cisco). ++[pap] returns noop No authenticate method (Auth-Type) configuration found for the request: Rejecting the user ;this look like authentication protocol is a must before the process can work, however, eap.conf file is there and eap is uncommented out with it's arguments. ? Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> cisco attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 5 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 5 Sending Access-Reject of id 187 to 127.0.0.1 port 43663 Waking up in 4.9 seconds. rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=187, length=20 [root@Crest raddb]# Cleaning up request 5 ID 187 with timestamp +411 Ready to process requests. Rgrds, Alex -----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of Alan Buxey Sent: Thursday, December 10, 2009 2:07 AM To: FreeRadius users mailing list Subject: Re: Testing radius server Hi,
Now I know it's a config issue in the clients.conf, as radtest is failing. I
set user name and password, but radius is sending a reject. This is the
first time I'm using radius. So please bear with me. Can some one mail me
example of the minimum required configuration that needed for the radius to
work, no EAP or MSCAP ..etc.
hey, guess what - 'radiusd -X' this will be far more useful than throwing random recommendations to you. have you followed basic guidance regarding hwo to use clients.conf eg testuser Cleartext-Password := "testpassword" alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4674 (20091209) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
Alex, Where did you create the user and password cisco? in the /etc/raddb/clients.conf. <tim> That's the problem. You configure RADIUS clients in the clients.conf file. A RADIUS client is a network device like a NAS or a wireless Access Point. A copy of your users configuration file would be great Which config files do you need, radiusd.conf, or clients.conf? There is also, /etc/raddb/users which I have not even touched, cuz I did not see it readily on the wiki, and I did not know about till now. <tim> users are defined in the "users" file. Read the comments in the users file. Generally, when you install and configure FR, you start with the radiusd.conf file, then clients.conf and finally users. Yes, the documentation is in many different places. Start here: 1. FreeRADIUS v2 Documentation http://freeradius.org/doc/ 2. Read the comments in the config files - radiusd.conf, clients.conf and users. 3. Check out this page from Alan's online book - http://deployingradius.com/documents/configuration/pap.html Tim
Hi,
Where did you create the user and password cisco?
in the /etc/raddb/clients.conf.
A copy of your users configuration file would be great
Which config files do you need, radiusd.conf, or clients.conf? There is also, /etc/raddb/users which I have not even touched, cuz I did not see it readily on the wiki, and I did not know about till now.
no no no (cries!) cleints.conf is for NAS devices to talk to the FreeRADIUS server user accounts/passwords go into the users file....this is so clear and well documented! please just READ the users file and see - eg 'John Doe' example account in that file.. once you look you will truly understand! alan
Alan, Where is the user file? Why the wiki did not list this file. How would I know about the file. From the wiki, I don't see any talk about this file you talking about. Alex Background RADIUS is a protocol spoken between an access server, typically a device connected to several modems or ISDN lines, and a radius server. When a user connects to the access server, (s)he is asked for a loginname and a password. This information is then sent to the radius server. The server replies with "access denied", or "access OK". In the latter case login information is sent along, such as the IP address in the case of a PPP connection. The access server also sends login and logout records to the radius server so accounting can be done. These records are kept for each terminal server seperately in a file called detail, and in the wtmp compatible logfile /var/log/radwtmp. Command Line Options radiusd [-a acct_dir] [-d db_dir] [-l log_dir] [-i address] [-p port] [-AcfnsSvXxyz] -A Write a file detail.auth in addition to the standard detail file in the same directory. This file will contain all the authentication-request records. This can be useful for debugging, but not for normal operation. This command line option is accepted only for backwards compatibility. It no longer does anything. See the configuration for the detail module in radiusd.conf. -S Write the stripped usernames (without prefix or suffix) in the detail file instead of the raw record as received from the terminal server. This command line option is deprecated. See the log_stripped_names configuration item in the radiusd.conf file. -a accounting directory This defaults to /var/log/radacct. If that directory exists, radiusd will write an ascii accounting record into a detail file for every login/logout recorded. The location of the detail file is acct_dir/terminal_server/detail. This command line option is deprecated. See the radacctdir configuration item in the radiusd.conf file. -l logging directory This defaults to /var/log. Radiusd writes a logfile here called radius.log. It contains informational and error messages, and optionally a record of every login attempt (for aiding an ISP's helpdesk). The special arguments stdout and stderr cause the information to get written to the standard output, or standard error instead. The special argument syslog sends the information with syslog(3). This command line option is deprecated. See the log_dir configuration item in the radiusd.conf file. -g facility Specifies the syslog facility to be used with -l syslog. Default is daemon. Another reasonable choice would be authpriv. -d config directory Defaults to /etc/raddb. Radiusd looks here for its configuration files such as the dictionary and the users files. -i ip-address Defines which IP addres to bind to for sending and receiving packets - useful for multi-homed hosts. This command line option is deprecated. See the bind_address configuration item in the radiusd.conf file. -b If the radius server binary was compiled with dbm support, this flag tells it to actually use the database files instead of the flat users file. This command line option is deprecated, and does not do anything. -c This is still an experimental feature. Cache the password, group and shadow files in a hash-table in memory. This makes the radius process use a bit more memory, but username lookups in the password file are much faster. After every change in the real password file (user added, password changed) you need to send a SIGHUP to the radius server to let it re-read its configuration and the password/group/shadow files! This command line option is deprecated. See the cache configuration item for the unix module in the radiusd.conf file. -f Do not fork, stay running as a foreground process. -p port Normally radiusd listens on the ports specified in /etc/services (radius and radacct). With this option radiusd listens on the specified port for authentication requests and on the specified port +1 for accounting requests. This command line option is deprecated. See the port configuration item in the radiusd.conf file. -s Run in "single server" mode. The server normally runs with multiple threads and/or processes, which can lower its response time to requests. Some systems have issues with threading, however, so running in "single server" mode may help to address those issues. In single server mode, the server will also not "daemonize" (auto-background) itself. -v Print server version information and exit. -x Debug mode. In this mode the server will print details of every request on its stderr output. Most useful in combination with -s. You can specify this option 2 times (-x -x or -xx) to get a bit more debugging output. -X Extended debug mode. Equivalent to -sfxx, but simpler to explain. -y Write details about every authentication request in the radius.log file. This command line option is deprecated. See the log_auth configuration item in the radiusd.conf file. -z Include the password in the radius.log file even for successful logins. This is very insecure! This command line option is deprecated. See the log_auth_badpass and the log_auth_goodpass configuration items in the radiusd.conf file. Configuration Radiusd uses a number of configuration files. Each file has it's own manpage describing the format of the file. These files are: radiusd.conf The main configuration file, which sets the administrator-controlled items. dictionary This file is usually static. It defines all the possible RADIUS attributes used in the other configuration files. You don't have to modify it. It includes other dictionary files in the same directory. clients [ Deprecated in favor of clients.conf ] clients.conf Contains the IP address and a secret key for every client that wants to connect to the server. naslist [ Deprecated in favor of clients.conf ] Contains an entry for every NAS (Network Access Server) in the network. This is not the same as a client, especially if you have radius proxy server in your network. In that case, the proxy server is the client and it sends requests for different NASes. It also contains an abbreviated name for each terminal server, used to create the directory name where the detail file is written, and used for the /var/log/radwtmp file. Finally it also defines what type of NAS (Cisco, Livingston, Portslave) the NAS is. hints Defines certain hints to the radius server based on the users's loginname or other attributes sent by the access server. It also provides for mapping user names (such as Pusername -> username). This provides the functionality that the Livingston 2.0 server has as "Prefix" and "Suffix" support in the users file, but is more general. Of course the Livingston way of doing things is also supported, and you can even use both at the same time (within certain limits). huntgroups Defines the huntgroups that you have, and makes it possible to restrict access to certain huntgroups to certain (groups of) users. users Here the users are defined. On a typical setup, this file mainly contains DEFAULT entries to process the different types of logins, based on hints from the hints file. Authentication is then based on the contents of the UNIX /etc/passwd file. However, it is also possible to define all users, and their passwords, in this file. See -----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of Alan Buxey Sent: Thursday, December 10, 2009 1:43 PM To: FreeRadius users mailing list Subject: Re: Testing radius server Hi,
Where did you create the user and password cisco?
in the /etc/raddb/clients.conf.
A copy of your users configuration file would be great
Which config files do you need, radiusd.conf, or clients.conf? There is also, /etc/raddb/users which I have not even touched, cuz I did not see it readily on the wiki, and I did not know about till now.
no no no (cries!) cleints.conf is for NAS devices to talk to the FreeRADIUS server user accounts/passwords go into the users file....this is so clear and well documented! please just READ the users file and see - eg 'John Doe' example account in that file.. once you look you will truly understand! alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
Where is the user file? Why the wiki did not list this file. How would I know about the file. From the wiki, I don't see any talk about this file you talking about.
Read the documentation included with the server. Start with doc/README. Ivan Kalik
Arrogant. -----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.o rg] On Behalf Of tnt@kalik.net Sent: Thursday, December 10, 2009 2:37 PM To: FreeRadius users mailing list Subject: RE: Testing radius server
Where is the user file? Why the wiki did not list this file. How would I know about the file. From the wiki, I don't see any talk about this file you talking about.
Read the documentation included with the server. Start with doc/README. Ivan Kalik - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
"Alex Bahoor" <alexbahoor@sbcglobal.net> writes:
Arrogant.
http://catb.org/~esr/faqs/smart-questions.html#keepcool You probably should read the rest of this document as well, but it seems that this particular section was written specifically for you. Bjørn
"Alex Bahoor" <alexbahoor@sbcglobal.net> writes:
Arrogant.
http://catb.org/~esr/faqs/smart-questions.html#keepcool
You probably should read the rest of this document as well, but it seems that this particular section was written specifically for you.
Bjørn
[JK] Bjorn, thanks for the posting. Excellent write-up. It should be mandatory reading before joining this community. This message is confidential to Prodea Systems, Inc unless otherwise indicated or apparent from its nature. This message is directed to the intended recipient only, who may be readily determined by the sender of this message and its contents. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient:(a)any dissemination or copying of this message is strictly prohibited; and(b)immediately notify the sender by return message and destroy any copies of this message in any form(electronic, paper or otherwise) that you have.The delivery of this message and its information is neither intended to be nor constitutes a disclosure or waiver of any trade secrets, intellectual property, attorney work product, or attorney-client communications. The authority of the individual sending this message to legally bind Prodea Systems is neither apparent nor implied,and must be independently verified.
Hi,
Alan,
Where is the user file? Why the wiki did not list this file. How would I know about the file. From the wiki, I don't see any talk about this file you talking about.
/etc/raddb/users ? /usr/local/raddb/users ? /opt/freeradius/users? whereever you installed the server config files. http://wiki.freeradius.org/CONFIGURATION_FILES lookee there. 'users; file clearly shown and explained. and thats just one obvious example but i think you're there now alan PS in your email you actually wrote....
users Here the users are defined. On a typical setup, this file mainly contains DEFAULT entries to process the different types of logins, based on hints from the hints file. Authentication is then based on the contents of the UNIX /etc/passwd file. However, it is also possible to define all users, and their passwords, in this file.
Alex, you don't create users on the clients.conf file. You create users on the users file (among other most important things). You configure radius clients on the clients.conf. For what you're trying to accomplish, users file is fine. There's tons of help on the man pages for each file, including very easy examples. man users man clients.conf Greetings. On Thu, Dec 10, 2009 at 12:56 PM, Alex Bahoor <alexbahoor@sbcglobal.net>wrote:
Gera
------------------------------
*From:* freeradius-users-bounces+alexbahoor=sbcglobal.net@ lists.freeradius.org [mailto:freeradius-users-bounces+alexbahoor<freeradius-users-bounces%2Balexbahoor> =sbcglobal.net@lists.freeradius.org] *On Behalf Of *gera *Sent:* Thursday, December 10, 2009 11:07 AM
*To:* FreeRadius users mailing list *Subject:* Re: Testing radius server
Where did you create the user and password cisco?
in the /etc/raddb/clients.conf.
A copy of your users configuration file would be great
Which config files do you need, radiusd.conf, or clients.conf? There is also, /etc/raddb/users which I have not even touched, cuz I did not see it readily on the wiki, and I did not know about till now.
I’m not clear on the purpose of the attachment you mailed?
This file is not accessible: http://wiki.freeradius.org/FAQ
Alex
On Thu, Dec 10, 2009 at 12:05 PM, g <gerardocb@gmail.com> wrote:
Where did you create the user and password cisco?
A copy of your users configuration file would be great.
On Thu, Dec 10, 2009 at 11:03 AM, Alex Bahoor <alexbahoor@sbcglobal.net> wrote:
Alan,
Radius -X is always on, and I went through the clients.conf file. -X gives a lot information, since you asked here is my understanding. I'm not a programmer so some of them are cryptic to me. I put in comments to what I think they are, but they are only guesses. I would be very thankful if you can shed lights on them.
Also, there is file experimental.conf stated in eap.conf, but did not exist. It may have some useful information.
root@Crest raddb]# radtest cisco cisco 127.0.0.1 200 testing123
Sending Access-Request of id 187 to 127.0.0.1 port 1812
User-Name = "cisco"
User-Password = "cisco"
NAS-IP-Address = 127.0.0.1
NAS-Port = 200
rad_recv: Access-Request packet from host 127.0.0.1 port 43663, id=187, length=57
User-Name = "cisco"
User-Password = "cisco"
NAS-IP-Address = 127.0.0.1
NAS-Port = 200
+- entering group authorize {...}
++[preprocess] returns ok ;what is preprocess and what does it do?
++[chap] returns noop ;I can tell that chap was not selected as a protocol, right?
++[mschap] returns noop ;as above
[suffix] No '@' in User-Name = "cisco", looking up realm NULL ;why @ is expected in a name or password?
[suffix] No such realm "NULL" ;what this mean?
++[suffix] returns noop
[eap] No EAP-Message, not doing EAP ;eap is not auth protocol.
++[eap] returns noop
++[unix] returns notfound ;what is this?
++[files] returns noop ?
++[expiration] returns noop ?
++[logintime] returns noop ?
[pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ;I do have a password (cisco).
++[pap] returns noop
No authenticate method (Auth-Type) configuration found for the request: Rejecting the user ;this look like authentication protocol is a must before the process can work, however, eap.conf file is there and eap is uncommented out with it’s arguments. ?
Failed to authenticate the user.
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject] expand: %{User-Name} -> cisco
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 5 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 5
Sending Access-Reject of id 187 to 127.0.0.1 port 43663
Waking up in 4.9 seconds.
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=187, length=20
[root@Crest raddb]# Cleaning up request 5 ID 187 with timestamp +411
Ready to process requests.
Rgrds,
Alex
-----Original Message----- From: freeradius-users-bounces+alexbahoor=sbcglobal.net@ lists.freeradius.org [ mailto:freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org<freeradius-users-bounces+alexbahoor=sbcglobal.net@lists.freeradius.org>] On Behalf Of Alan Buxey Sent: Thursday, December 10, 2009 2:07 AM To: FreeRadius users mailing list Subject: Re: Testing radius server
Hi,
Now I know it's a config issue in the clients.conf, as radtest is failing. I
set user name and password, but radius is sending a reject. This is the
first time I'm using radius. So please bear with me. Can some one mail me
example of the minimum required configuration that needed for the radius to
work, no EAP or MSCAP ..etc.
hey, guess what - 'radiusd -X' this will be far more useful than
throwing random recommendations to you.
have you followed basic guidance regarding hwo to use clients.conf
eg
testuser Cleartext-Password := "testpassword"
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4674 (20091209) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4676 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4677 (20091210) __________
The message was checked by ESET NOD32 Antivirus.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (7)
-
Alan Buxey -
Alex Bahoor -
Bjørn Mork -
gera -
John Kane -
Tim Sylvester -
tnt＠kalik.net