0001829: Admin Guide 4.4.0 clarification on paper pages 31-32 - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001829

PacketFence

doc

public

2014-10-08 09:51

2015-03-04 12:10

Reporter

ae3

Assigned To

lmunro

Priority

normal

Severity

minor

Reproducibility

always

Status

acknowledged

Resolution

open

Platform

All

OS Version

All

Product Version

4.4.0

Target Version

Fixed in Version

Summary

0001829: Admin Guide 4.4.0 clarification on paper pages 31-32

Description

On 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 Reproduce

Open manual, bang head against wall. :-)

Additional Information

Maybe I'm mis-reading the page, but the suggested order above seems proper at least from the CentOS/RHEL perspective.

Issue History
Date Modified	Username	Field	Change
2014-10-08 09:51	ae3	New Issue
2015-03-04 12:10	lmunro	Assigned To	=> lmunro
2015-03-04 12:10	lmunro	Status	new => acknowledged

Relationships

Notes
There are no notes attached to this issue.