Hi Alan,
I am suspecting some radius setting on my server because free radius on
other server is responding and authentication and accounting is successful.
On May 24, 2013 7:56 PM, freeradius-users-requ...@lists.freeradius.org
wrote:
Send Freeradius-Users mailing list submissions to
On 2013-05-25, at 12:39 PM, Arvind Bahuguni arvind...@gmail.com wrote:
Hi Alan,
I am suspecting some radius setting on my server because free radius on other
server is responding and authentication and accounting is successful
For one, you need to edit your posts. It's ridiculous to reply
I'm trying to restrict a guest user from a single NAS-IP-Address via users
and I can't get it to work.
Doesn't work:
testNAS-IP-Address == 127.0.0.1
Auth-Type := Accept
testNAS-IP-Address == 127.0.1.1
Auth-Type := Accept
Works, but it isn't restricted by NAS:
test
Pete Ashdown wrote:
I'm trying to restrict a guest user from a single NAS-IP-Address via users
and I can't get it to work.
Doesn't work:
test NAS-IP-Address == 127.0.0.1
Auth-Type := Accept
That's wrong. Why? See the debug output. It *tells* you what's
wrong, and how to fix
I am having trouble starting freeradius at boot on CentOS 6.4. It starts, but
it does not connect to my database; however, if run it manually from the
command the it works fine. I think there is permission issue somewhere. See the
log below:
when I run following command as root it works
#
Bill Grant wrote:
I am having trouble starting freeradius at boot on CentOS 6.4. It starts, but
it does not connect to my database; however, if run it manually from the
command the it works fine. I think there is permission issue somewhere. See
the log below:
when I run following command
You are right I temporarily disabled SE Linux with echo 0 /selinux/enforce
and it worked. Now I just need to figure out exactly what it is blocking.
Thanks for the help!
From: Alan DeKok [al...@deployingradius.com]
Sent: Saturday, May 25, 2013 7:44 PM
I think Phil's diagnosis is correct; 'Auth-Type := Reject' requires the ':='
operator to reject a CHAP authentication.
Unfortunately, it's not always easy to place a live production system in
debug mode, hence the initial is this something stupid question :)
(And apologies for the lack of a
I was able to fix it by doing the following.
I installed setroubleshoot
yum install setroubleshoot
Then I ran the following command
sealert -a /var/log/audit/audit.log /path/to/mylogfile.txt
mylogfile.txt showed:
found 3 alerts in /var/log/audit/audit.log
On Sat, May 25, 2013 at 06:23:44PM -0400, Alan DeKok wrote:
You *did* run the server in debugging mode, as suggested in the FAQ,
README, man page, and daily on this list?
Yes I did, over a period of about 3 hours of trial and error before banging my
head against:
[...]
[files] users:
the list and banned permanently.
Alan DeKok.
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.freeradius.org/pipermail/freeradius-users/attachments/20130525/dc49bb28/attachment-0001.html
--
Message: 2
Date: Sat
11 matches
Mail list logo
