PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001829PacketFencedocpublic2014-10-08 09:512015-03-04 12:10
Reporterae3 
Assigned Tolmunro 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformAllOSAllOS VersionAll
Product Version4.4.0 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001829: Admin Guide 4.4.0 clarification on paper pages 31-32
DescriptionOn paper pages 31-32 (PDF pages 35-36), there seems to be confusion in the sample command line text boxes:

For Centos/RHEL:

(box)
# usermod -a -G wbpriv pf
(/box)

Finally, start winbind, and test the setup using ntlm_auth and radtest:

(box)
# service winbind start
# chkconfig --level 345 winbind on
(/box)


For Debian and Ubuntu:

(box)
# usermod -a -G winbindd_priv pf
# ntlm_auth --username myDomainUser
# radtest -t mschap -x myDomainUser myDomainPassword localhost:18120 12
 testing123
 Sending Access-Request of id 108 to 127.0.0.1 port 18120
 User-Name = "myDomainUser"
 NAS-IP-Address = 10.0.0.1
 NAS-Port = 12
 Message-Authenticator = 0x00000000000000000000000000000000
 MS-CHAP-Challenge = 0x79d62c9da4e55104
 MS-CHAP-Response =
 0x000100000000000000000000000000000000000000000000000091c843b420f0dec4228ed2f26bff07d5e49ad9a2974229e5
 rad_recv: Access-Accept packet from host 127.0.0.1 port 18120, id=108,
 length=20
(/box)

When following this through for CentOS/RHEL, you do not do the ntlm_auth or radtest tests...since it is only in the Debian/Ubuntu textbox!!!

ASSuming that the service and chkconfig work the same under Debian/Ubuntu (which I have personally never used), this order seems to make sense to me:

For Centos/RHEL:

(box)
# usermod -a -G wbpriv pf
(/box)

For Debian and Ubuntu:

(box)
# usermod -a -G winbindd_priv pf
(/box)

Start winbind:

(box)
# service winbind start
# chkconfig --level 345 winbind on
(/box)

Finally, test the setup using ntlm_auth and radtest:

(box)
# ntlm_auth --username myDomainUser
# radtest -t mschap -x myDomainUser myDomainPassword localhost:18120 12
 testing123
 Sending Access-Request of id 108 to 127.0.0.1 port 18120
 User-Name = "myDomainUser"
 NAS-IP-Address = 10.0.0.1
 NAS-Port = 12
 Message-Authenticator = 0x00000000000000000000000000000000
 MS-CHAP-Challenge = 0x79d62c9da4e55104
 MS-CHAP-Response =
 0x000100000000000000000000000000000000000000000000000091c843b420f0dec4228ed2f26bff07d5e49ad9a2974229e5
 rad_recv: Access-Accept packet from host 127.0.0.1 port 18120, id=108,
 length=20
(/box)

Steps To ReproduceOpen manual, bang head against wall. :-)
Additional InformationMaybe I'm mis-reading the page, but the suggested order above seems proper at least from the CentOS/RHEL perspective.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-08 09:51ae3New Issue
2015-03-04 12:10lmunroAssigned To => lmunro
2015-03-04 12:10lmunroStatusnew => acknowledged

There are no notes attached to this issue.