- Freeradius-Users - lists.freeradius.org

RE: Freeradius-Users Digest, Vol 7, Issue 115
by Varun Marwah 30 Nov '05

30 Nov '05

Thanks charles schwartz Your documentation and responses really helped. The radius Server is working now properly for all users in LDAP. I need to give access to specific users in a group call RadiusUsers in Windows 2003 LDAP. How can I go about it. The Group is at location: cn=RadiusUsers,ou=Groups,dc=ABC,dc=DEF,dc=com Thanks & Regards Varun Marwah CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com) and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. -----Original Message----- From: freeradius-users-bounces(a)lists.freeradius.org [mailto:freeradius-users-bounces@lists.freeradius.org] On Behalf Of freeradius-users-request(a)lists.freeradius.org Sent: Wednesday, November 30, 2005 4:37 AM To: freeradius-users(a)lists.freeradius.org Subject: Freeradius-Users Digest, Vol 7, Issue 115 Send Freeradius-Users mailing list submissions to freeradius-users(a)lists.freeradius.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeradius.org/mailman/listinfo/freeradius-users or, via email, send a message with subject or body 'help' to freeradius-users-request(a)lists.freeradius.org You can reach the person managing the list at freeradius-users-owner(a)lists.freeradius.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Freeradius-Users digest..." Today's Topics: 1. Re: WLAN 802.1x FreeRadius with LDAP (Zoltan Ori) 2. RE: WLAN 802.1x FreeRadius with LDAP (Christian Poessinger) 3. RE: WLAN 802.1x FreeRadius with LDAP (King, Michael) 4. Re: WLAN 802.1x FreeRadius with LDAP (Zoltan Ori) 5. RE: WLAN 802.1x FreeRadius with LDAP (Christian Poessinger) 6. Re: Configuring RADIUS Users (Radius) 7. LDAP, FreeRadius, and Schema (Matt Juszczak) 8. Re: AD authentication (charles schwartz) ---------------------------------------------------------------------- Message: 1 Date: Tue, 29 Nov 2005 13:19:40 -0500 From: Zoltan Ori <z.ori(a)morehead-st.edu> Subject: Re: WLAN 802.1x FreeRadius with LDAP To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <200511291319.40875.z.ori(a)morehead-st.edu> Content-Type: text/plain; charset="iso-8859-1" On Tuesday 29 November 2005 11:07, Christian Poessinger wrote: > > You didn't configure a password for the user. > > Yes, I did. I have a userPassword atribute in my LDAP backend, also > it contains a clear text password. I can fully use this account in > the backend for ftp/ssh/http but not with peap/mschapv2 over radius. > You have ntlm_auth in your mschap configuration. You don't want that for LDAP. You don't need anything NT in that module. The default configuration had everything commented out but authtype = MS-CHAP. Start with that and then add what you need. ------------------------------ Message: 2 Date: Tue, 29 Nov 2005 19:56:29 +0100 From: "Christian Poessinger" <christian(a)poessinger.com> Subject: RE: WLAN 802.1x FreeRadius with LDAP To: "'FreeRadius users mailing list'" <freeradius-users(a)lists.freeradius.org> Message-ID: <000f01c5f516$9c2c4600$370110ac(a)wueI.poessinger.org> Zoltan Ori wrote: > You have ntlm_auth in your mschap configuration. You don't want that > for LDAP. > You don't need anything NT in that module. The default configuration > had everything commented out but authtype = MS-CHAP. Start with that > and then add what you need. Nope, there is everything uncommented. I also tried to add this to the ldap.attrmap file: checkItem LM-Password userPassword checkItem NT-Password userPassword But this hadn't any effect either. ------------------------------ Message: 3 Date: Tue, 29 Nov 2005 14:03:21 -0500 From: "King, Michael" <MKing(a)bridgew.edu> Subject: RE: WLAN 802.1x FreeRadius with LDAP To: "FreeRadius users mailing list" <freeradius-users(a)lists.freeradius.org> Message-ID: <EFB7B6506E9AB147BCC8EF9417E22091075C4118(a)EXCH2.campus.bridgew.edu> Content-Type: text/plain; charset="us-ascii" -----Original Message----- Zoltan Ori wrote: > You have ntlm_auth in your mschap configuration. You don't want that > for LDAP. > You don't need anything NT in that module. The default configuration > had everything commented out but authtype = MS-CHAP. Start with that > and then add what you need. Nope, there is everything uncommented. I also tried to add this to the ldap.attrmap file: Christian, That is what he is saying your problem is, everything is uncommented........ ------------------------------ Message: 4 Date: Tue, 29 Nov 2005 14:08:47 -0500 From: Zoltan Ori <z.ori(a)morehead-st.edu> Subject: Re: WLAN 802.1x FreeRadius with LDAP To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Message-ID: <200511291408.47792.z.ori(a)morehead-st.edu> Content-Type: text/plain; charset="iso-8859-1" On Tuesday 29 November 2005 13:56, Christian Poessinger wrote: > Nope, there is everything uncommented. I also tried to add this to the > ldap.attrmap file: > That's the problem everything is uncommented. Comment out ntlm_auth and with_ntdomain_hack. If you have plain text passwords, you aren't authenticating to a Windows domain controller, you don't have windbindd and nmbd running, you don't need want them in your mschap configuration. ------------------------------ Message: 5 Date: Tue, 29 Nov 2005 20:16:56 +0100 From: "Christian Poessinger" <christian(a)poessinger.com> Subject: RE: WLAN 802.1x FreeRadius with LDAP To: "'FreeRadius users mailing list'" <freeradius-users(a)lists.freeradius.org> Message-ID: <001701c5f519$77c4f070$370110ac(a)wueI.poessinger.org> King, Michael wrote: > Christian, That is what he is saying your problem is, everything is > uncommented........ Sorry, with uncommented i ment that all is commented out. Sorry my fault. ------------------------------ Message: 6 Date: Tue, 29 Nov 2005 13:04:48 -0700 From: "Radius" <radius(a)kingmanaz.net> Subject: Re: Configuring RADIUS Users To: "FreeRadius users mailing list" <freeradius-users(a)lists.freeradius.org> Message-ID: <00e301c5f520$26e2e610$0501a8c0@LockKey> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response ----- Original Message ----- From: "Christopher Carver" <ccarver(a)pennswoods.net> To: "FreeRadius users mailing list" <freeradius-users(a)lists.freeradius.org> Sent: Tuesday, November 29, 2005 11:04 AM Subject: Re: Configuring RADIUS Users > Madhuraka Godahewa wrote: > >>Hi All, I installed freeRADIUS 1.0.5 recently, and configured the server >>as described in the documentation files. My operating system is SUSE Linux >>9.2. When I run the 'radiusd -X' from the shell, the last four lines of >>the output are as follows. < Listening on authentication >>10.128.253.110:1812 Listening on accounting 10.128.253.110:1813 Listening >>on proxy 10.128.253.110:1814 Ready to process requests. >> 10.128.253.110 is the IP Address given to the Radius Server. Then, I >> created a test account named 'root' with the password 'root'. Then, I ran >> the radtest (from the RADIUS Server itself) and got the following output. >> < Sending Access-Request of id 195 to 10.128.253.110:1812 User-Name = >> "root" User-Password = "root" NAS-IP-Address = rajith-office NAS-Port = >> 1812 rad_recv: Access-Accept packet from host 10.128.253.110:1812, >> id=195, length=20 >>'rajith-office' is the name given to the RADIUS Server. In the debug >>shell, I obtained the following output. < rad_recv: Access-Request packet >>from host 10.128.253.110:1025, id=195, length=56 User-Name = "root" >>User-Password = "root" NAS-IP-Address = 255.255.255.255 NAS-Port = 1812 >>Processing the authorize section of radiusd.conf modcall: entering group >>authorize for request 0 modcall[authorize]: module "preprocess" returns ok >>for request 0 modcall[authorize]: module "chap" returns noop for request 0 >>modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: >>No '@' in User-Name = "root", looking up realm NULL rlm_realm: No such >>realm "NULL" modcall[authorize]: module "suffix" returns noop for request >>0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" >>returns noop for request 0 users: Matched root at 153 users: Matched >>DEFAULT at 157 modcall[authorize]: module "files" returns ok for request 0 >>modcall: group authorize returns ok for request 0 rad_check_password: >>Found Auth-Type Local auth: type Local auth: user supplied User-Password >>matches local User-Password Sending Access-Accept of id 195 to >>10.128.253.110:1025 Finished request 0 Going to the next request --- >>Walking the entire request list --- >>Waking up in 6 seconds... --- Walking the entire request list --- >>Cleaning up request 0 ID 195 with timestamp 438c1bca Nothing to do. >>Sleeping until we see a request. >> Now my problem is, when I try to send an access-request (using the Radius >> Test Utility) from another machine (running Windows XP), which is in the >> same network, the server does not says that it receives an >> access-request. Does anybody know, where the problem is? You should be >> seeing something if the requests is even making it to the > radiusd process. Use tcpdump on the server to ensure you are receiving > the request. 'tcpdump port 1812' should do it. If you see nothing, you > have a firewall/network connectivity issue on the server or client. > > Chris Carver > - But root does not allow logins that way if his system is setup not to and most Linux variants do that automatically. You have to "su" to get root access after you log in with regular user. Maybe create a different user and try it. ------------------------------ Message: 7 Date: Tue, 29 Nov 2005 17:13:41 -0500 From: Matt Juszczak <matt(a)atopia.net> Subject: LDAP, FreeRadius, and Schema To: freeradius-users(a)lists.freeradius.org Message-ID: <438CD295.3030604(a)atopia.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi all, I was wondering what everyone uses for an account objectClass? Right now I'm using "Person", which makes the dn: cn=<user>,ou=Radius,dc=mydomain,dc=net However, indexing the cn would index the CN of other OU's as well ... . I'm just wondering what people use. I know "Account" could also be used. Regards, Matt ------------------------------ Message: 8 Date: Tue, 29 Nov 2005 23:50:05 +0100 From: charles schwartz <charles.schwartz(a)umail.univ-metz.fr> Subject: Re: AD authentication To: vmarwah(a)quark.com Cc: freeradius-users(a)lists.freeradius.org Message-ID: <200511292250.jATMo5OS024332(a)umail.univ-metz.fr> Content-Type: text/plain Hi, Here is what I found in your log: [...] Exec-Program output: winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/cache/samba/winbindd_privileged are set correctly. (0xc0000022) Exec-Program-Wait: plaintext: winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/cache/samba/winbindd_privileged are set correctly. (0xc0000022) Exec-Program: returned: 1 [...] Try to troubleshoot winbind. It seems that there may be a permission problem. Regards, Charles > Hi There > > I have configured the Freeradius on Fedora core 3 as per the > documentation > > [root@Radius raddb]# ntlm_auth --request-nt-key --domain=INDIA > --username=checkad > password: > NT_STATUS_OK: Success (0x0) > [root@Radius raddb]# > > When I start the the Radius Server using Radius -X command Starts fine. > > When I give the logon credentials through the wireless laptop the user > doesn't get validated. > > Please help me out. If you need the any config files for your reference, > please let me know.Atached is the log file of output generated. > > Also guide me, as I have already given allow permissions to users with > Dialin Permissions in AD domain. > > > Thanks & Regards > Varun Marwah > CONFIDENTIALITY NOTICE > This e-mail transmission and any documents, files, or previous e-mail > messages appended or attached to it, may contain information that is > confidential or legally privileged. If you are not the intended > recipient, or a person responsible for delivering it to the intended > recipient, you are hereby notified that any disclosure, copying, > printing, distribution, or use of the information contained or attached > to this transmission is STRICTLY PROHIBITED. If you have received this > transmission in error, please immediately notify the sender by telephone > (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com) and > delete the original transmission, its attachments, and any copies > without reading or saving in any manner. Thank you. > > -----Original Message----- > From: charles schwartz [mailto:charles.schwartz@umail.univ-metz.fr] > Sent: Monday, November 28, 2005 10:51 PM > To: freeradius-users(a)lists.freeradius.org > Cc: Varun Marwah > Subject: Re: AD authentication > > Hi, > > If the wbinfo command does not work, ntlm_auth won't work too. > > > > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > This error indicates that something went wrong with the domain access. > Try to troubleshoot by using wbinfo -g or wbinfo -u. > With these commands you should be able to list the users and groups of > your domain. > > There may be a problem with NTLM on your Windows2003 server. > Note thath NTLM was the authentication protocol used by earlier version > of Windows. > It is still supported for backward compatibility, but can be disabled. > By default, Win2k and 2003 use Kerberos for authentication. > > You might have a security policy thats restricts the use of NTLM on your > network. > Check your GPO if NTLM is allowed to be transmitted across the network. > > > Regards, > Charles Schwartz > > > > > > Hi, > > > > > > > > I used the document freeRadius_AD_tutorial.pdf for configuring a linux > > box to get authenticated through users in Windows 2003 AD. > > > > > > > > I used the command net join -U Administrator to add the machine to the > > domain. It gave successful results. Now on typing the command > > > > > > > > wbinfo -a checkad%Quark_123 > > > > > > > > I got the following results:- > > > > > > > > plaintext password authentication failed > > > > error code was NT_STATUS_NO_SUCH_USER (0xc0000064) > > > > error messsage was: No such user > > > > Could not authenticate user checkad%Quark_123 with plaintext password > > > > challenge/response password authentication failed > > > > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > > > Could not authenticate user checkad with challenge/response > > > > > > > > Also, on giving the command > > > > > > > > # ntlm_auth --request-nt-key --domain=india.quark.com --username= > > checkad > > > > password: > > > > NT_STATUS_CANT_ACCESS_DOMAIN_INFO: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > (0xc00000da) > > > > [root@Radius etc]# > > > > I get the above stated error. Please help. > > > > Thanks & Regards > > > > Varun Marwah > > > > CONFIDENTIALITY NOTICE > > > > This e-mail transmission and any documents, files, or previous e-mail > > messages appended or attached to it, may contain information that is > > confidential or legally privileged. If you are not the intended > > recipient, or a person responsible for delivering it to the intended > > recipient, you are hereby notified that any disclosure, copying, > > printing, distribution, or use of the information contained or > attached > > to this transmission is STRICTLY PROHIBITED. If you have received this > > transmission in error, please immediately notify the sender by > telephone > > (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com > > <mailto:vmarwah@quark.com> ) and delete the original transmission, its > > attachments, and any copies without reading or saving in any manner. > > Thank you. > > > > > > > > -- > This message has been scanned for viruses and > dangerous content by Quark Anti Virus, and is > believed to be clean. > ------------------------------ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html End of Freeradius-Users Digest, Vol 7, Issue 115 ************************************************ -- This message has been scanned for viruses and dangerous content by Quark Anti Virus, and is believed to be clean.

1 0

RE: Can not authenticate against Active directory as LDAP server
by Alhagie Puye 30 Nov '05

30 Nov '05

Make sure the password has double-quotes around it. I had to do that to get it working. Have you tried using ldapsearch first to make sure that you are feeding it the correct parameters? Try something like ldapsearch -LLL -h 10.1.1.1 -x -b 'dc=corp,dc=van,dc=com' '(&(memberof=CN=rptpcps,OU=Users,DC=corp,DC=van,DC=com)(samaccountname=a puye))' -D apuye(a)corp.van.com -w yourpassword Change it to match your environment. Hope that helps. Alhagie Puye - Network Engineer Datawave Group of Companies (604)295-1817 > >-----Original Message----- > >From: freeradius-users-bounces(a)lists.freeradius.org > >[mailto:freeradius-users-bounces@lists.freeradius.org] On > >Behalf Of Anup Parkhi > >Sent: November 29, 2005 6:44 PM > >To: freeradius-users(a)lists.freeradius.org > >Subject: Can not authenticate against Active directory as LDAP server > > > >My environment is > > > >FreeRadius: 1.0.5 on RedHat > >Funk Odyssey supplicant. (Tried with XP supplicant also) > >Authenticator: HP procurve switch > >EAP: EAP-MD5 > >Directory: Active directory as LDAP server > > > >I am getting the following error while authenticating users > >in Active directory. Any help is appreciated. I went through > >ldap_how_to.txt and changed my radiusd.conf to tailor for > >active directory but it is still failing. > > > >My configuration sections are > >lldap { > > server = "10.11.12.137" > > identity = > >"cn=Administrator,cn=users,dc=parkhi,dc=net" > > password = mypassword > > basedn = "cn=users,dc=parkhi,dc=net" > > filter = > >"(sAMAccountName=%{Stripped-User-Name:-%{User-Name}})" > > # base_filter = "(objectclass=radiusprofile)" > > > > # set this to 'yes' to use TLS encrypted connections > > # to the LDAP database by using the StartTLS extended > > # operation. > > # The StartTLS operation is supposed to be > >used with normal > > # ldap connections instead of using ldaps (port 689) > >connections start_tls = no > > > > # tls_cacertfile = /path/to/cacert.pem > > # tls_cacertdir = /path/to/ca/dir/ > > # tls_certfile = /path/to/radius.crt > > # tls_keyfile = /path/to/radius.key > > # tls_randfile = /path/to/rnd > > # tls_require_cert = "demand" > > > > # default_profile = > >"cn=radprofile,ou=dialup,o=My Org,c=UA" > ># profile_attribute = "radiusProfileDn" > > #access_attr = "dialupAccess" > > > > # Mapping of RADIUS dictionary attributes to LDAP > > # directory attributes. > > dictionary_mapping = ${raddbdir}/ldap.attrmap > > > > ldap_connections_number = 10 > > > > # > > # NOTICE: The password_header directive is > >NOT case insensitive > > # > > # password_header = "{clear}" > > # > > # The server can usually figure this out on > >its own, and pull > > # the correct User-Password or NT-Password > >from the database. > > # > > # Note that NT-Passwords MUST be stored as a > >32-digit hex > > # string, and MUST start off with "0x", such as: > > # > > # 0x000102030405060708090a0b0c0d0e0f > > # > ># Without the leading "0x", NT-Passwords will not work. > > # This goes for NT-Passwords stored in SQL, too. > > # > > password_attribute = User-Password > > # groupname_attribute = cn > > # groupmembership_filter = > >"(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(obj > >ectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" > > # groupmembership_attribute = radiusGroupName > > timeout = 4 > > timelimit = 3 > > net_timeout = 1 > > compare_check_items = no > > # do_xlat = yes > > # access_attr_used_for_allow = yes > > } > > > >authorize { > > preprocess > > suffix > > files > > ldap > >} > > > >authenticate { > > Auth-Type LDAP { > > ldap > > } > >} > > > > > > > >the console output of radiusd -X > > > > > > > > > > > >Cleaning up request 4 ID 229 with timestamp 438d0d46 Nothing > >to do. Sleeping until we see a request. > >rad_recv: Access-Request packet from host 10.11.12.107:1024, id=230, > >length=214 > > Framed-MTU = 1480 > > NAS-IP-Address = 10.11.12.107 > > NAS-Identifier = "HP ProCurve Switch 2824" > > User-Name = "test" > > Service-Type = Framed-User > > Framed-Protocol = PPP > > NAS-Port = 24 > > NAS-Port-Type = Ethernet > > NAS-Port-Id = "24" > > Called-Station-Id = "00-0f-20-8d-04-c8" > > Calling-Station-Id = "00-c0-9f-0d-4a-1f" > > Connect-Info = "CONNECT Ethernet 100Mbps Full duplex" > > Tunnel-Type:0 = VLAN > > Tunnel-Medium-Type:0 = IEEE-802 > > Tunnel-Private-Group-Id:0 = "1010" > > EAP-Message = 0x020100090174657374 > > Message-Authenticator = 0xaf12ec64c245045bbf5a5cc4985025de > >Processing the authorize section of radiusd.conf > >modcall: entering group authorize for request 5 > >modcall[authorize]: module "preprocess" returns ok for request 5 > > rlm_realm: No '@' in User-Name = "test", looking up realm NULL > > rlm_realm: No such realm "NULL" > >modcall[authorize]: module "suffix" returns noop for request 5 > > users: Matched test at 66 > >modcall[authorize]: module "files" returns ok for request 5 > >rlm_ldap: - authorize > >rlm_ldap: performing user authorization for test > >radius_xlat: '(sAMAccountName=test)' > >radius_xlat: 'cn=users,dc=parkhi,dc=net' > >rlm_ldap: ldap_get_conn: Checking Id: 0 > >rlm_ldap: ldap_get_conn: Got Id: 0 > >rlm_ldap: performing search in cn=users,dc=parkhi,dc=net, with filter > >(sAMAccou)rlm_ldap: looking for check items in directory... > >rlm_ldap: looking for reply items in directory... > >rlm_ldap: user test authorized to use remote access > >rlm_ldap: ldap_release_conn: Release Id: 0 > >modcall[authorize]: module "ldap" returns ok for request 5 > >rad_check_password: Found Auth-Type LDAP > >auth: type "LDAP" > >Processing the authenticate section of radiusd.conf > >modcall: entering group Auth-Type for request 5 > >rlm_ldap: - authenticate > >rlm_ldap: Attribute "User-Password" is required for authentication. > >modcall[authenticate]: module "ldap" returns invalid for request 5 > >modcall: group Auth-Type returns invalid for request 5 > >auth: Failed to validate the user. > >Delaying request 5 for 1 seconds > >Finished request 5 > > > > > >- > >List info/subscribe/unsubscribe? See > >http://www.freeradius.org/list/users.html > > Disclaimer: This message (including any attachments) is confidential, may be privileged and is only intended for the person to whom it is addressed. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. E-mail communications are inherently vulnerable to interception by unauthorized parties and are susceptible to change. We will use alternate communication means upon request.

1 0

Fall-through and different NAS IP Settings
by Curt LeCaptain 30 Nov '05

30 Nov '05

Hello all, I've done a radiusd -X to do some testing and was rather shocked by what happened when I'm attempting to make some changes to make one specific NAS (our DSL group) to have no timeouts. Here's a snippet of my config: DEFAULT Auth-Type = System, NAS-IP-Address == ip.add.re.ss, Simultaneous-Use = 1 Framed-Compression = None, Idle-Timeout = 0, Session-Timeout = 0, Fall-Through = No # DEFAULT Service-Type == Framed-User Service-Type == Framed-User, Framed-Routing = None, Framed-Compression = Van-Jacobsen-TCP-IP, Fall-Through = Yes DEFAULT Framed-Protocol == PPP, Auth-Type = System Framed-Protocol == PPP, Idle-Timeout = 1200, Session-Timeout = 28800, Framed-MTU = 1518, Framed-Compression = Van-Jacobsen-TCP-IP, Filter-Id = "smtpfilter" >From what I understand, if people come from the NAS-IP-Address of ip.add.re.ss, it should be stopping everything, giving them their IP and not continuing on due to the Fall-Through = No. Perhaps I'm getting this wrong, but I'm trying to make it so that those users aren't getting any timeouts. Any thoughts would be very helpful. Thanks, Curt LeCaptain

2 1

Re: AD authentication
by charles schwartz 29 Nov '05

29 Nov '05

Hi, Here is what I found in your log: [...] Exec-Program output: winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/cache/samba/winbindd_privileged are set correctly. (0xc0000022) Exec-Program-Wait: plaintext: winbind client not authorized to use winbindd_pam_auth_crap. Ensure permissions on /var/cache/samba/winbindd_privileged are set correctly. (0xc0000022) Exec-Program: returned: 1 [...] Try to troubleshoot winbind. It seems that there may be a permission problem. Regards, Charles > Hi There > > I have configured the Freeradius on Fedora core 3 as per the > documentation > > [root@Radius raddb]# ntlm_auth --request-nt-key --domain=INDIA > --username=checkad > password: > NT_STATUS_OK: Success (0x0) > [root@Radius raddb]# > > When I start the the Radius Server using Radius -X command Starts fine. > > When I give the logon credentials through the wireless laptop the user > doesn't get validated. > > Please help me out. If you need the any config files for your reference, > please let me know.Atached is the log file of output generated. > > Also guide me, as I have already given allow permissions to users with > Dialin Permissions in AD domain. > > > Thanks & Regards > Varun Marwah > CONFIDENTIALITY NOTICE > This e-mail transmission and any documents, files, or previous e-mail > messages appended or attached to it, may contain information that is > confidential or legally privileged. If you are not the intended > recipient, or a person responsible for delivering it to the intended > recipient, you are hereby notified that any disclosure, copying, > printing, distribution, or use of the information contained or attached > to this transmission is STRICTLY PROHIBITED. If you have received this > transmission in error, please immediately notify the sender by telephone > (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com) and > delete the original transmission, its attachments, and any copies > without reading or saving in any manner. Thank you. > > -----Original Message----- > From: charles schwartz [mailto:charles.schwartz@umail.univ-metz.fr] > Sent: Monday, November 28, 2005 10:51 PM > To: freeradius-users(a)lists.freeradius.org > Cc: Varun Marwah > Subject: Re: AD authentication > > Hi, > > If the wbinfo command does not work, ntlm_auth won't work too. > > > > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > This error indicates that something went wrong with the domain access. > Try to troubleshoot by using wbinfo -g or wbinfo -u. > With these commands you should be able to list the users and groups of > your domain. > > There may be a problem with NTLM on your Windows2003 server. > Note thath NTLM was the authentication protocol used by earlier version > of Windows. > It is still supported for backward compatibility, but can be disabled. > By default, Win2k and 2003 use Kerberos for authentication. > > You might have a security policy thats restricts the use of NTLM on your > network. > Check your GPO if NTLM is allowed to be transmitted across the network. > > > Regards, > Charles Schwartz > > > > > > Hi, > > > > > > > > I used the document freeRadius_AD_tutorial.pdf for configuring a linux > > box to get authenticated through users in Windows 2003 AD. > > > > > > > > I used the command net join -U Administrator to add the machine to the > > domain. It gave successful results. Now on typing the command > > > > > > > > wbinfo -a checkad%Quark_123 > > > > > > > > I got the following results:- > > > > > > > > plaintext password authentication failed > > > > error code was NT_STATUS_NO_SUCH_USER (0xc0000064) > > > > error messsage was: No such user > > > > Could not authenticate user checkad%Quark_123 with plaintext password > > > > challenge/response password authentication failed > > > > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > > > Could not authenticate user checkad with challenge/response > > > > > > > > Also, on giving the command > > > > > > > > # ntlm_auth --request-nt-key --domain=india.quark.com --username= > > checkad > > > > password: > > > > NT_STATUS_CANT_ACCESS_DOMAIN_INFO: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > (0xc00000da) > > > > [root@Radius etc]# > > > > I get the above stated error. Please help. > > > > Thanks & Regards > > > > Varun Marwah > > > > CONFIDENTIALITY NOTICE > > > > This e-mail transmission and any documents, files, or previous e-mail > > messages appended or attached to it, may contain information that is > > confidential or legally privileged. If you are not the intended > > recipient, or a person responsible for delivering it to the intended > > recipient, you are hereby notified that any disclosure, copying, > > printing, distribution, or use of the information contained or > attached > > to this transmission is STRICTLY PROHIBITED. If you have received this > > transmission in error, please immediately notify the sender by > telephone > > (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com > > <mailto:vmarwah@quark.com> ) and delete the original transmission, its > > attachments, and any copies without reading or saving in any manner. > > Thank you. > > > > > > > > -- > This message has been scanned for viruses and > dangerous content by Quark Anti Virus, and is > believed to be clean. >

1 0

Configuring RADIUS Users
by Madhuraka Godahewa 29 Nov '05

29 Nov '05

Hi All, I installed freeRADIUS 1.0.5 recently, and configured the server as described in the documentation files. My operating system is SUSE Linux 9.2. When I run the 'radiusd -X' from the shell, the last four lines of the output are as follows. < Listening on authentication 10.128.253.110:1812 Listening on accounting 10.128.253.110:1813 Listening on proxy 10.128.253.110:1814 Ready to process requests. > 10.128.253.110 is the IP Address given to the Radius Server. Then, I created a test account named 'root' with the password 'root'. Then, I ran the radtest (from the RADIUS Server itself) and got the following output. < Sending Access-Request of id 195 to 10.128.253.110:1812 User-Name = "root" User-Password = "root" NAS-IP-Address = rajith-office NAS-Port = 1812 rad_recv: Access-Accept packet from host 10.128.253.110:1812, id=195, length=20 > 'rajith-office' is the name given to the RADIUS Server. In the debug shell, I obtained the following output. < rad_recv: Access-Request packet from host 10.128.253.110:1025, id=195, length=56 User-Name = "root" User-Password = "root" NAS-IP-Address = 255.255.255.255 NAS-Port = 1812 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "root", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 users: Matched root at 153 users: Matched DEFAULT at 157 modcall[authorize]: module "files" returns ok for request 0 modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type Local auth: type Local auth: user supplied User-Password matches local User-Password Sending Access-Accept of id 195 to 10.128.253.110:1025 Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... --- Walking the entire request list --- Cleaning up request 0 ID 195 with timestamp 438c1bca Nothing to do. Sleeping until we see a request. > Now my problem is, when I try to send an access-request (using the Radius Test Utility) from another machine (running Windows XP), which is in the same network, the server does not says that it receives an access-request. Does anybody know, where the problem is? Thanking You. -------------------------------------------------------------------------------- Madhuraka Godahewa Telecommunications Engineer Research and Development Unit Electroteks Global Networks (Pvt.) Ltd. Mobile: + 94-777-647055

5 4

RE: WLAN 802.1x FreeRadius with LDAP
by King, Michael 29 Nov '05

29 Nov '05

-----Original Message----- Zoltan Ori wrote: > You have ntlm_auth in your mschap configuration. You don't want that > for LDAP. > You don't need anything NT in that module. The default configuration > had everything commented out but authtype = MS-CHAP. Start with that > and then add what you need. Nope, there is everything uncommented. I also tried to add this to the ldap.attrmap file: Christian, That is what he is saying your problem is, everything is uncommented........

2 1

RE: AD authentication
by Varun Marwah 29 Nov '05

29 Nov '05

Hi Charles, I already have defined NTLM Security policy for my Domain Controller security settings. But Still getting the same error message. Can you please specify the local domain controller policies with settings which should be enabled for Freeradius server to authenticate. Thanks & Regards Varun Marwah CONFIDENTIALITY NOTICE This e-mail transmission and any documents, files, or previous e-mail messages appended or attached to it, may contain information that is confidential or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, printing, distribution, or use of the information contained or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender by telephone (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com) and delete the original transmission, its attachments, and any copies without reading or saving in any manner. Thank you. -----Original Message----- From: charles schwartz [mailto:charles.schwartz@umail.univ-metz.fr] Sent: Monday, November 28, 2005 10:51 PM To: freeradius-users(a)lists.freeradius.org Cc: Varun Marwah Subject: Re: AD authentication Hi, If the wbinfo command does not work, ntlm_auth won't work too. > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO This error indicates that something went wrong with the domain access. Try to troubleshoot by using wbinfo -g or wbinfo -u. With these commands you should be able to list the users and groups of your domain. There may be a problem with NTLM on your Windows2003 server. Note thath NTLM was the authentication protocol used by earlier version of Windows. It is still supported for backward compatibility, but can be disabled. By default, Win2k and 2003 use Kerberos for authentication. You might have a security policy thats restricts the use of NTLM on your network. Check your GPO if NTLM is allowed to be transmitted across the network. Regards, Charles Schwartz > Hi, > > > > I used the document freeRadius_AD_tutorial.pdf for configuring a linux > box to get authenticated through users in Windows 2003 AD. > > > > I used the command net join -U Administrator to add the machine to the > domain. It gave successful results. Now on typing the command > > > > wbinfo -a checkad%Quark_123 > > > > I got the following results:- > > > > plaintext password authentication failed > > error code was NT_STATUS_NO_SUCH_USER (0xc0000064) > > error messsage was: No such user > > Could not authenticate user checkad%Quark_123 with plaintext password > > challenge/response password authentication failed > > error code was NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da) > > error messsage was: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > > Could not authenticate user checkad with challenge/response > > > > Also, on giving the command > > > > # ntlm_auth --request-nt-key --domain=india.quark.com --username= > checkad > > password: > > NT_STATUS_CANT_ACCESS_DOMAIN_INFO: NT_STATUS_CANT_ACCESS_DOMAIN_INFO > (0xc00000da) > > [root@Radius etc]# > > I get the above stated error. Please help. > > Thanks & Regards > > Varun Marwah > > CONFIDENTIALITY NOTICE > > This e-mail transmission and any documents, files, or previous e-mail > messages appended or attached to it, may contain information that is > confidential or legally privileged. If you are not the intended > recipient, or a person responsible for delivering it to the intended > recipient, you are hereby notified that any disclosure, copying, > printing, distribution, or use of the information contained or attached > to this transmission is STRICTLY PROHIBITED. If you have received this > transmission in error, please immediately notify the sender by telephone > (+91-172-2299137) or return e-mail message (vmarwah(a)quark.com > <mailto:vmarwah@quark.com> ) and delete the original transmission, its > attachments, and any copies without reading or saving in any manner. > Thank you. > > > -- This message has been scanned for viruses and dangerous content by Quark Anti Virus, and is believed to be clean.

3 2

EAP-TLS problem with Intel PROSet 7.1.4.4
by Michelle Lin 29 Nov '05

29 Nov '05

Hi Experts, I'm new to FreeRadius server. The version I installed on my Linux box (RedHat 9.0) is 1.0.5. I configured this FreeRadius server using EAP_TLS. And the server works fine with following hardware/software setup: NIC card (built in): Intel(R)PRO/Wireless 2200BG Network Connection NIC software: Intel PROSet/Wireless, version 9.0.3.0 AP: DLink wireless router DI-624 Client System: Windows XP However, the same certifcate doesn't work with an older NIC card/NIC software on a different laptop. Here is the info about NIC card and NIC software. This laptop also runs Windows XP. NIC card (built in): Intel (R) PRO/Wireless LAN 2100 3A Mini PCI Adapter NIC software: Intel PROSet, version 7.1.4.4 I got following failure notification after trying to connect to the AP: 802.1x Authentication has failed due to a Challenge Failure. This may have happened because of wrong user credentials. Same certificate works fine with my first laptop. The debugging trace from FreeRADIUS server is in the attached file. Thanks a lot in advance for your help... - michelle __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/

2 1

RE: Vendor-type length problem
by MINODIER David RD-RESA-LAN 29 Nov '05

29 Nov '05

Many thanks for such a quick answer ! Sub-question: First, i'll definitly have a look at the CVS. Can you just tell me if (CVS) Freeradius will be able to reply to 1 vendor with a vendor-type of 2 octets and the other vendors with a vendor-type of 1 octet ? Again, thanks so much Alan. > > - can Freeradius encode a vendor-type on 2 octets for 1 specific > > vendor while replying to the client? > > In 1.0.5, no. In the CVS head, yes.

2 1

Vendor-type length problem
by MINODIER David RD-RESA-LAN 29 Nov '05

29 Nov '05

HI all, I have a Radius client (not generic but proprietary) that encodes its vendor-type on *2* octets while the "normal and common" way is to encode the vendor-type on 1 octet (0-255). RFC 2865 says that the actual "vendor-type + length + value" is a string field and : "The String field is one or more octets. The actual format of the information is site or application specific, and a robust implementation SHOULD support the field as undistinguished octets. The codification of the range of allowed usage of this field is outside the scope of this specification." O'Reilley Radius book however says page 28: "vendor type - the vendor type field, which is one octet in length, etc". And the consequent questions: - Is there an RFC that actually defines for good the length of the vendor-type? (I did not manage to find that piece of information) - can Freeradius encode a vendor-type on 2 octets for 1 specific vendor while replying to the client? - if so (I doubt...), how? (configuration? Special dictionary format?) Many thks. David.

2 1