FreeRadius+AD integration

shrikant Bhat shrikabhat at gmail.com
Fri Apr 27 12:35:46 CEST 2007


Yes I figured that. thanks for that. But the issues is the user I am
trying to authenticate is not listed in users file or in AD, so I dont
understand how is it authenticating this user.
I have attached debug .
thanks for the help.

*********************************************************************************************************
rad_recv: Access-Request packet from host 127.0.0.1:32779, id=100, length=59
        User-Name = "raduser"
        User-Password = "radpass"
        NAS-IP-Address = 255.255.255.255
        NAS-Port = 0
  Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 3
  modcall[authorize]: module "preprocess" returns ok for request 3
  modcall[authorize]: module "chap" returns noop for request 3
  modcall[authorize]: module "mschap" returns noop for request 3
    rlm_realm: No '@' in User-Name = "raduser", looking up realm NULL
    rlm_realm: No such realm "NULL"
  modcall[authorize]: module "suffix" returns noop for request 3
  rlm_eap: No EAP-Message, not doing EAP
  modcall[authorize]: module "eap" returns noop for request 3
    users: Matched entry DEFAULT at line 154
  modcall[authorize]: module "files" returns ok for request 3
modcall: leaving group authorize (returns ok) for request 3
  rad_check_password:  Found Auth-Type ntlm_auth
auth: type "ntlm_auth"
  Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 3
radius_xlat: Running registered xlat function of module mschap for
string 'User-Name'
radius_xlat:  '--username=raduser'
radius_xlat:  '--password=radpass'
  modcall[authenticate]: module "ntlm_auth" returns ok for request 3
modcall: leaving group authenticate (returns ok) for request 3
Sending Access-Accept of id 100 to 127.0.0.1 port 32779
Finished request 3
Going to the next request
--- Walking the entire request list ---
Waking up in 6 seconds...
--- Walking the entire request list ---
Cleaning up request 3 ID 100 with timestamp 4631d1f0
Nothing to do.  Sleeping until we see a request.
****************************************************************************************************

On 4/27/07, tnt at kalik.co.yu <tnt at kalik.co.yu> wrote:
> Error seems to be because shared secret is testing123 not testing 123.
> But you need to paste output od radiusd-X after Access-Request. Open two
> ssh sessions and do radtest from one and radiusd -X from the other.
>
> Ivan Kalik
> Kalik Informatika ISP
>
>
> Dana 27/4/2007, "shrikant Bhat" <shrikabhat at gmail.com> piše:
>
> >I get this error
> >[root at rad ~]# radtest raduser radpass localhost 0 testing 123
> >Sending Access-Request of id 47 to 127.0.0.1 port 1812
> >        User-Name = "raduser"
> >        User-Password = "radpass"
> >        NAS-IP-Address = 255.255.255.255
> >        NAS-Port = 0
> >        Framed-Protocol = PPP
> >rad_recv: Access-Accept packet from host 127.0.0.1:1812, id=47, length=20
> >rad_verify: Received Access-Accept packet from client 127.0.0.1 port
> >1812 with invalid signature (err=2)!  (Shared secret is incorrect.)
> >
> >On 4/27/07, tnt at kalik.co.yu <tnt at kalik.co.yu> wrote:
> >> And what happens when you get Access-Request?
> >>
> >>
> >> Dana 27/4/2007, "shrikant Bhat" <shrikabhat at gmail.com> pi e:
> >>
> >> >Hello Alan,
> >> >I have built and installed 1.1.6 version of FreeRadius. When I test
> >> >using radtest it authenticates any user with any pasword, what I mean
> >> >by this is it doesnt seem to contact the ADS to lookup the user
> >> >information and authenticate. I have attached the debug
> >> >*****************************************************************************************************
> >> >[root at my-rad raddb]# /usr/local/sbin/radiusd -X
> >> >Starting - reading configuration files ...
> >> >reread_config:  reading radiusd.conf
> >> >Config:   including file: /etc/raddb/clients.conf
> >> >Config:   including file: /etc/raddb/snmp.conf
> >> >Config:   including file: /etc/raddb/eap.conf
> >> >Config:   including file: /etc/raddb/sql.conf
> >> > main: prefix = "/usr"
> >> > main: localstatedir = "/var"
> >> > main: logdir = "/var/log/radius"
> >> > main: libdir = "/usr/lib"
> >> > main: radacctdir = "/var/log/radius/radacct"
> >> > main: hostname_lookups = no
> >> > main: max_request_time = 30
> >> > main: cleanup_delay = 5
> >> > main: max_requests = 1024
> >> > main: delete_blocked_requests = 0
> >> > main: port = 0
> >> > main: allow_core_dumps = no
> >> > main: log_stripped_names = no
> >> > main: log_file = "/var/log/radius/radius.log"
> >> > main: log_auth = no
> >> > main: log_auth_badpass = no
> >> > main: log_auth_goodpass = no
> >> > main: pidfile = "/var/run/radiusd/radiusd.pid"
> >> > main: user = "radiusd"
> >> > main: group = "radiusd"
> >> > main: usercollide = no
> >> > main: lower_user = "no"
> >> > main: lower_pass = "no"
> >> > main: nospace_user = "no"
> >> > main: nospace_pass = "no"
> >> > main: checkrad = "/usr/sbin/checkrad"
> >> > main: proxy_requests = yes
> >> > security: max_attributes = 200
> >> > security: reject_delay = 1
> >> > security: status_server = no
> >> > main: debug_level = 0
> >> >read_config_files:  reading dictionary
> >> >read_config_files:  reading naslist
> >> >Using deprecated naslist file.  Support for this will go away soon.
> >> >read_config_files:  reading clients
> >> >read_config_files:  reading realms
> >> >radiusd:  entering modules setup
> >> >Module: Library search path is /usr/lib
> >> >Module: Loaded expr
> >> >Module: Instantiated expr (expr)
> >> >Module: Loaded exec
> >> > exec: wait = no
> >> > exec: program = "/usr/bin/ntlm_auth  --request-nt-key
> >> >--domain=MYDOMAIN.COM --username=%{mschap:User-Name}
> >> >--password=%{User-Password}"
> >> > exec: input_pairs = "request"
> >> > exec: output_pairs = "(null)"
> >> > exec: packet_type = "(null)"
> >> >Module: Instantiated exec (ntlm_auth)
> >> >Module: Loaded CHAP
> >> >Module: Instantiated chap (chap)
> >> >Module: Loaded preprocess
> >> > preprocess: huntgroups = "/etc/raddb/huntgroups"
> >> > preprocess: hints = "/etc/raddb/hints"
> >> > preprocess: with_ascend_hack = no
> >> > preprocess: ascend_channels_per_line = 23
> >> > preprocess: with_ntdomain_hack = no
> >> > preprocess: with_specialix_jetstream_hack = no
> >> > preprocess: with_cisco_vsa_hack = no
> >> >Module: Instantiated preprocess (preprocess)
> >> >Module: Loaded MS-CHAP
> >> > mschap: use_mppe = yes
> >> > mschap: require_encryption = no
> >> > mschap: require_strong = no
> >> > mschap: with_ntdomain_hack = yes
> >> > mschap: passwd = "(null)"
> >> > mschap: authtype = "MS-CHAP"
> >> > mschap: ntlm_auth = "(null)"
> >> >Module: Instantiated mschap (mschap)
> >> >Module: Loaded realm
> >> > realm: format = "suffix"
> >> > realm: delimiter = "@"
> >> > realm: ignore_default = no
> >> > realm: ignore_null = no
> >> >Module: Instantiated realm (suffix)
> >> >Module: Loaded eap
> >> > eap: default_eap_type = "md5"
> >> > eap: timer_expire = 60
> >> > eap: ignore_unknown_eap_types = no
> >> > eap: cisco_accounting_username_bug = no
> >> >rlm_eap: Loaded and initialized type md5
> >> >rlm_eap: Loaded and initialized type leap
> >> > gtc: challenge = "Password: "
> >> > gtc: auth_type = "PAP"
> >> >rlm_eap: Loaded and initialized type gtc
> >> > mschapv2: with_ntdomain_hack = no
> >> >rlm_eap: Loaded and initialized type mschapv2
> >> >Module: Instantiated eap (eap)
> >> >Module: Loaded files
> >> > files: usersfile = "/etc/raddb/users"
> >> > files: acctusersfile = "/etc/raddb/acct_users"
> >> > files: preproxy_usersfile = "/etc/raddb/preproxy_users"
> >> > files: compat = "cistron"
> >> >[/etc/raddb/users]:1 Cistron compatibility checks for entry raduser ...
> >> >[/etc/raddb/users]:153 Cistron compatibility checks for entry DEFAULT ...
> >> >?Changing 'Auth-Type =' to 'Auth-Type +='
> >> >[/etc/raddb/users]:172 Cistron compatibility checks for entry DEFAULT ...
> >> >[/etc/raddb/users]:184 Cistron compatibility checks for entry DEFAULT ...
> >> >[/etc/raddb/users]:191 Cistron compatibility checks for entry DEFAULT ...
> >> >[/etc/raddb/users]:198 Cistron compatibility checks for entry DEFAULT ...
> >> >Module: Instantiated files (files)
> >> >Module: Loaded Acct-Unique-Session-Id
> >> > acct_unique: key = "User-Name, Acct-Session-Id, NAS-IP-Address,
> >> >Client-IP-Address, NAS-Port"
> >> >Module: Instantiated acct_unique (acct_unique)
> >> >Module: Loaded detail
> >> > detail: detailfile =
> >> >"/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d"
> >> > detail: detailperm = 384
> >> > detail: dirperm = 493
> >> > detail: locking = no
> >> >Module: Instantiated detail (detail)
> >> >Module: Loaded System
> >> > unix: cache = no
> >> > unix: passwd = "(null)"
> >> > unix: shadow = "/etc/shadow"
> >> > unix: group = "(null)"
> >> > unix: radwtmp = "/var/log/radius/radwtmp"
> >> > unix: usegroup = no
> >> > unix: cache_reload = 600
> >> >Module: Instantiated unix (unix)
> >> >Module: Loaded radutmp
> >> > radutmp: filename = "/var/log/radius/radutmp"
> >> > radutmp: username = "%{User-Name}"
> >> > radutmp: case_sensitive = yes
> >> > radutmp: check_with_nas = yes
> >> > radutmp: perm = 384
> >> > radutmp: callerid = yes
> >> >Module: Instantiated radutmp (radutmp)
> >> >Listening on authentication *:1812
> >> >Listening on accounting *:1813
> >> >Ready to process requests.
> >> >***********************************************************************
> >> >Thanks
> >> >SB
> >> >
> >> >On 4/23/07, Alan DeKok <aland at deployingradius.com> wrote:
> >> >> shrikant Bhat wrote:
> >> >> > 1.The document says  adding exec ... to the modules section and then
> >> >> > listing ntlm_auth in the authenticate section. when I have exec
> >> >> > ntlm_auth in modules section and ntlm_auth listed in authenticate
> >> >> > section I get 'Unknown Auth-Type "exec" in authenticate section'
> >> >> > error
> >> >> > how do I fix this? please help.
> >> >> > I have attached my radiusd.conf file.
> >> >>
> >> >>   All I know is that it works for me in 1.1.6.
> >> >>
> >> >> > 2. To authenticate cisco telnet sessions, is it possible to use
> >> >> > freeRadius with AD integration
> >> >> > what I mean by this is can I telnet using my ad ID and password with
> >> >> > freeRadius being authentication server?
> >> >>
> >> >>   Yes.
> >> >>
> >> >>   Alan DeKok.
> >> >> --
> >> >>   http://deployingradius.com       - The web site of the book
> >> >>   http://deployingradius.com/blog/ - The blog
> >> >> -
> >> >> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> >> >>
> >> >-
> >> >List info/subscribe/unsubscribe? See http://www.freeradius.org/list/usershtml
> >> >
> >> >
> >>
> >> -
> >> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> >>
> >
> >-
> >List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> >
> >
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>




More information about the Freeradius-Users mailing list