Hi, I want to use CHAP for authenticating the user. When I am sending CHAP-Password to FreeRADIUS, I am getting the following error. Found Auth-Type = CHAP +- entering group CHAP {...} [chap] rlm_chap: password supplied has wrong length ++[chap] returns invalid Failed to authenticate the user. What could be wrong? Please help. Thanks in advance. Logs: ===== FreeRADIUS Version 2.1.8, for host i686-pc-linux-gnu, built on May 10 2010 at 16:37:47 Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License v2. Starting - reading configuration files ... including configuration file /usr/local/etc/raddb/radiusd.conf including configuration file /usr/local/etc/raddb/proxy.conf including configuration file /usr/local/etc/raddb/clients.conf including files in directory /usr/local/etc/raddb/modules/ including configuration file /usr/local/etc/raddb/modules/unix including configuration file /usr/local/etc/raddb/modules/exec including configuration file /usr/local/etc/raddb/modules/echo including configuration file /usr/local/etc/raddb/modules/wimax including configuration file /usr/local/etc/raddb/modules/mac2ip including configuration file /usr/local/etc/raddb/modules/perl including configuration file /usr/local/etc/raddb/modules/sradutmp including configuration file /usr/local/etc/raddb/modules/pap including configuration file /usr/local/etc/raddb/modules/counter including configuration file /usr/local/etc/raddb/modules/expr including configuration file /usr/local/etc/raddb/modules/ippool including configuration file /usr/local/etc/raddb/modules/smsotp including configuration file /usr/local/etc/raddb/modules/realm including configuration file /usr/local/etc/raddb/modules/always including configuration file /usr/local/etc/raddb/modules/otp including configuration file /usr/local/etc/raddb/modules/policy including configuration file /usr/local/etc/raddb/modules/krb5 including configuration file /usr/local/etc/raddb/modules/files including configuration file /usr/local/etc/raddb/modules/detail.log including configuration file /usr/local/etc/raddb/modules/pam including configuration file /usr/local/etc/raddb/modules/etc_group including configuration file /usr/local/etc/raddb/modules/detail including configuration file /usr/local/etc/raddb/modules/inner-eap including configuration file /usr/local/etc/raddb/modules/smbpasswd including configuration file /usr/local/etc/raddb/modules/digest including configuration file /usr/local/etc/raddb/modules/attr_rewrite including configuration file /usr/local/etc/raddb/modules/linelog including configuration file /usr/local/etc/raddb/modules/expiration including configuration file /usr/local/etc/raddb/modules/detail.example.com including configuration file /usr/local/etc/raddb/modules/chap including configuration file /usr/local/etc/raddb/modules/passwd including configuration file /usr/local/etc/raddb/modules/logintime including configuration file /usr/local/etc/raddb/modules/mac2vlan including configuration file /usr/local/etc/raddb/modules/sql_log including configuration file /usr/local/etc/raddb/modules/radutmp including configuration file /usr/local/etc/raddb/modules/ldap including configuration file /usr/local/etc/raddb/modules/acct_unique including configuration file /usr/local/etc/raddb/modules/attr_filter including configuration file /usr/local/etc/raddb/modules/checkval including configuration file /usr/local/etc/raddb/modules/preprocess including configuration file /usr/local/etc/raddb/modules/mschap including configuration file /usr/local/etc/raddb/modules/sqlcounter_expire_on_login including configuration file /usr/local/etc/raddb/modules/ntlm_auth including configuration file /usr/local/etc/raddb/modules/cui including configuration file /usr/local/etc/raddb/eap.conf including configuration file /usr/local/etc/raddb/policy.conf including files in directory /usr/local/etc/raddb/sites-enabled/ including configuration file /usr/local/etc/raddb/sites-enabled/default including configuration file /usr/local/etc/raddb/sites-enabled/control-socket including configuration file /usr/local/etc/raddb/sites-enabled/inner-tunnel main { allow_core_dumps = no } including dictionary file /usr/local/etc/raddb/dictionary main { prefix = "/usr/local" localstatedir = "/usr/local/var" logdir = "/usr/local/var/log/radius" libdir = "/usr/local/lib" radacctdir = "/usr/local/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 pidfile = "/usr/local/var/run/radiusd/radiusd.pid" checkrad = "/usr/local/sbin/checkrad" debug_level = 0 proxy_requests = yes log { stripped_names = no auth = no auth_badpass = no auth_goodpass = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } radiusd: #### Loading Realms and Home Servers #### proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } home_server localhost { ipaddr = 127.0.0.1 port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 require_message_authenticator = no zombie_period = 40 status_check = "status-server" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 irt = 2 mrt = 16 mrc = 5 mrd = 30 } home_server_pool my_auth_failover { type = fail-over home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { } radiusd: #### Loading Clients #### client localhost { ipaddr = 127.0.0.1 require_message_authenticator = no secret = "testing123" nastype = "other" } client 192.168.1.109 { require_message_authenticator = no secret = "secret" } radiusd: #### Instantiating modules #### instantiate { Module: Linked to module rlm_exec Module: Instantiating exec exec { wait = no input_pairs = "request" shell_escape = yes } Module: Linked to module rlm_expr Module: Instantiating expr Module: Linked to module rlm_expiration Module: Instantiating expiration expiration { reply-message = "Password Has Expired " } Module: Linked to module rlm_logintime Module: Instantiating logintime logintime { reply-message = "You are calling outside your allowed timespan " minimum-timeout = 60 } } radiusd: #### Loading Virtual Servers #### server inner-tunnel { modules { Module: Checking authenticate {...} for more modules to load Module: Linked to module rlm_pap Module: Instantiating pap pap { encryption_scheme = "auto" auto_header = no } Module: Linked to module rlm_chap Module: Instantiating chap Module: Linked to module rlm_mschap Module: Instantiating mschap mschap { use_mppe = yes require_encryption = no require_strong = no with_ntdomain_hack = no } Module: Linked to module rlm_unix Module: Instantiating unix unix { radwtmp = "/usr/local/var/log/radius/radwtmp" } Module: Linked to module rlm_eap Module: Instantiating eap eap { default_eap_type = "md5" timer_expire = 60 ignore_unknown_eap_types = no cisco_accounting_username_bug = no max_sessions = 4096 } Module: Linked to sub-module rlm_eap_md5 Module: Instantiating eap-md5 Module: Linked to sub-module rlm_eap_leap Module: Instantiating eap-leap Module: Linked to sub-module rlm_eap_gtc Module: Instantiating eap-gtc gtc { challenge = "Password: " auth_type = "PAP" } Ignoring EAP-Type/tls because we do not have OpenSSL support. Ignoring EAP-Type/ttls because we do not have OpenSSL support. Ignoring EAP-Type/peap because we do not have OpenSSL support. Module: Linked to sub-module rlm_eap_mschapv2 Module: Instantiating eap-mschapv2 mschapv2 { with_ntdomain_hack = no } Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_realm Module: Instantiating suffix realm suffix { format = "suffix" delimiter = "@" ignore_default = no ignore_null = no } Module: Linked to module rlm_files Module: Instantiating files files { usersfile = "/usr/local/etc/raddb/users" acctusersfile = "/usr/local/etc/raddb/acct_users" preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users" compat = "no" } Module: Checking session {...} for more modules to load Module: Linked to module rlm_radutmp Module: Instantiating radutmp radutmp { filename = "/usr/local/var/log/radius/radutmp" username = "%{User-Name}" case_sensitive = yes check_with_nas = yes perm = 384 callerid = yes } Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load Module: Linked to module rlm_attr_filter Module: Instantiating attr_filter.access_reject attr_filter attr_filter.access_reject { attrsfile = "/usr/local/etc/raddb/attrs.access_reject" key = "%{User-Name}" } } # modules } # server server { modules { Module: Checking authenticate {...} for more modules to load Module: Checking authorize {...} for more modules to load Module: Linked to module rlm_preprocess Module: Instantiating preprocess preprocess { huntgroups = "/usr/local/etc/raddb/huntgroups" hints = "/usr/local/etc/raddb/hints" with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = no with_alvarion_vsa_hack = no } Module: Checking preacct {...} for more modules to load Module: Linked to module rlm_acct_unique Module: Instantiating acct_unique acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } Module: Checking accounting {...} for more modules to load Module: Linked to module rlm_detail Module: Instantiating detail detail { detailfile = "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d" header = "%t" detailperm = 384 dirperm = 493 locking = no log_packet_header = no } Module: Instantiating attr_filter.accounting_response attr_filter attr_filter.accounting_response { attrsfile = "/usr/local/etc/raddb/attrs.accounting_response" key = "%{User-Name}" } Module: Checking session {...} for more modules to load Module: Checking post-proxy {...} for more modules to load Module: Checking post-auth {...} for more modules to load } # modules } # server radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 } listen { type = "acct" ipaddr = * port = 0 } listen { type = "control" listen { socket = "/usr/local/var/run/radiusd/radiusd.sock" } } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests. rad_recv: Access-Request packet from host 192.168.1.109 port 51736, id=5, length=106 User-Name = "steve" Acct-Session-Id = "001" NAS-Identifier = "NASIDTest" NAS-IP-Address = 192.168.1.120 Called-Station-Id = "called" Calling-Station-Id = "caller" NAS-Port = 1234 NAS-Port-Type = Ethernet CHAP-Password = 0x74657374696e67 User-Password = "testing" +- entering group authorize {...} ++[preprocess] returns ok [chap] Setting 'Auth-Type := CHAP' ++[chap] returns ok ++[mschap] returns noop [suffix] No '@' in User-Name = "steve", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound [files] users: Matched entry steve at line 76 ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = CHAP +- entering group CHAP {...} [chap] rlm_chap: password supplied has wrong length ++[chap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> steve attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 0 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 0 Sending Access-Reject of id 5 to 192.168.1.109 port 51736 Waking up in 4.9 seconds. Cleaning up request 0 ID 5 with timestamp +79 Ready to process requests.
Karuna G. Kumar wrote:
I want to use CHAP for authenticating the user. When I am sending CHAP-Password to FreeRADIUS, I am getting the following error.
Found Auth-Type = CHAP +- entering group CHAP {...} [chap] rlm_chap: password supplied has wrong length
Your RADIUS client does not implement RADIUS. ...
CHAP-Password = 0x74657374696e67
It is sending *ASCII* for the CHAP-Password. It needs to implement the CHAP protocol. Use a real RADIUS client, like radclient. Alan DeKok.
Alan, Thanks for your response. As you suggested, I used radclient command to test the CHAP. Now the server sends Access-Accept. But, what I observed is that the problem araises again even with radclient when I send User-Password attribute along with CHAP-Password attribute in the request. There is no problem when I don't send User-Password with CHAP-Password. Any thoughts on this why it is happening like this? I am attaching the Access packet info below for both success and failure cases. Success case: ============= Sending Access-Request of id 168 to 127.0.0.1 port 1812 User-Name = "steve" Acct-Session-Id = "001" NAS-Identifier = "NASIDTest" NAS-IP-Address = 192.168.1.120 Called-Station-Id = "called" Calling-Station-Id = "caller" NAS-Port = 1234 NAS-Port-Type = Ethernet CHAP-Password = 0xa88b83c43dd3fc20c67f3566f12ebb4958 rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=168, length=71 Service-Type = Framed-User Framed-Protocol = PPP Framed-IP-Address = 172.16.3.33 Framed-IP-Netmask = 255.255.255.0 Framed-Routing = Broadcast-Listen Filter-Id = "std.ppp" Framed-MTU = 1500 Framed-Compression = Van-Jacobson-TCP-IP server logs ----------- Found Auth-Type = CHAP +- entering group CHAP {...} [chap] login attempt by "steve" with CHAP password [chap] Using clear text password "testing" for user steve authentication. [chap] chap user steve authenticated succesfully ++[chap] returns ok Failure case ============ Sending Access-Request of id 109 to 127.0.0.1 port 1812 User-Name = "steve" Acct-Session-Id = "001" NAS-Identifier = "NASIDTest" NAS-IP-Address = 192.168.1.120 Called-Station-Id = "called" Calling-Station-Id = "caller" NAS-Port = 1234 NAS-Port-Type = Ethernet CHAP-Password = 0x74657374696e67 User-Password = "testing" rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=109, length=20 server logs: ------------ Found Auth-Type = CHAP +- entering group CHAP {...} [chap] rlm_chap: password supplied has wrong length ++[chap] returns invalid Failed to authenticate the user. Regards, Karun. -----Original Message----- From: freeradius-users-bounces+karuna.kumar=indscape.com@lists.freeradius.org on behalf of Alan DeKok Sent: Wed 6/9/2010 3:26 PM To: FreeRadius users mailing list Cc: Subject: Re: How to use CHAP? Karuna G. Kumar wrote:
I want to use CHAP for authenticating the user. When I am sending CHAP-Password to FreeRADIUS, I am getting the following error.
Found Auth-Type = CHAP +- entering group CHAP {...} [chap] rlm_chap: password supplied has wrong length
Your RADIUS client does not implement RADIUS. ...
CHAP-Password = 0x74657374696e67
It is sending *ASCII* for the CHAP-Password. It needs to implement the CHAP protocol. Use a real RADIUS client, like radclient. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Karuna G. Kumar wrote:
But, what I observed is that the problem araises again even with radclient when I send User-Password attribute along with CHAP-Password attribute in the request. There is no problem when I don't send User-Password with CHAP-Password. Any thoughts on this why it is happening like this? I am attaching the Access packet info below for both success and failure cases.
This is forbidden by the RADIUS protocol. There is *no* reason for doing this. The only reason to have a bad CHAP-Password, or to send both User-Password && CHAP-Password in the same packet is if you're writing your own RADIUS client. Are you asking this list for free support so that you can write your own RADIUS client? Alan DeKok.
Alan DeKok wrote:
Are you asking this list for free support so that you can write your own RADIUS client?
No. Not at all :-) I just want to know whether I need to send User-Password also in the request packet for CHAP. That's it. -Karun. -----Original Message----- From: freeradius-users-bounces+karuna.kumar=indscape.com@lists.freeradius.org on behalf of Alan DeKok Sent: Wed 6/9/2010 3:53 PM To: FreeRadius users mailing list Cc: Subject: Re: How to use CHAP? Karuna G. Kumar wrote:
But, what I observed is that the problem araises again even with radclient when I send User-Password attribute along with CHAP-Password attribute in the request. There is no problem when I don't send User-Password with CHAP-Password. Any thoughts on this why it is happening like this? I am attaching the Access packet info below for both success and failure cases.
This is forbidden by the RADIUS protocol. There is *no* reason for doing this. The only reason to have a bad CHAP-Password, or to send both User-Password && CHAP-Password in the same packet is if you're writing your own RADIUS client. Are you asking this list for free support so that you can write your own RADIUS client? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
Alan DeKok -
Karuna G. Kumar