Michael Monette
2014-04-17 20:38:24 UTC
Hi,
Could anyone explain why this is happening? I just spent like 3 hours trying to figure this out, and I feel like it just doesn't make much sense.
On the RADIUS server, SELinux is ON. I start radius in Debug with "radiusd -X" and from my client I login with my RADIUS credentials(really..ldap creds) and it works. No problem.
I stop radiusd in debug, and run a 'service radiusd start'. I try to login again and it fails! I then disable SELinux (setenforce 0) and try again and it works.
Why does SElinux not block 'radiusd -X' but it seems to block radius when it's started as a service(service radiusd start).
What is the difference?
Mike
Mike
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Could anyone explain why this is happening? I just spent like 3 hours trying to figure this out, and I feel like it just doesn't make much sense.
On the RADIUS server, SELinux is ON. I start radius in Debug with "radiusd -X" and from my client I login with my RADIUS credentials(really..ldap creds) and it works. No problem.
I stop radiusd in debug, and run a 'service radiusd start'. I try to login again and it fails! I then disable SELinux (setenforce 0) and try again and it works.
Why does SElinux not block 'radiusd -X' but it seems to block radius when it's started as a service(service radiusd start).
What is the difference?
Mike
Mike
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html