Hello,
We have a Fedora Core 2 linux server which unfortunately automatically
upgraded, using yum, from freeradius 0.9.3 to 1.0.1 last night. (I did
not intend that to happen so that I could check out the changes with
1.0.1 to ensure that it would work okay on our servers.) This morning
the server was showing that the freeradius daemon was not running.
In our radiusd.conf file in the authorize section we have:
mschap {
ok = return
}
It seems that a change in the new version now doesn't like this. Running
'radiusd -X' gives:
Module: Instantiated files (files)
radiusd.conf[1393] Unknown configuration directive "mschap" in
authorize section.
If I change this to just 'mschap' then radiusd runs. Is this a bug or
was there a reason for what appears to be a syntax change?
I'm looking through the mailing list archives but have found nothing
about this yet. I'll also try and see if we can get around the problem -
just using 'mschap' doesn't work for us, it seems that radiusd then
(afer the mschap bit) tries to authenticate (proxy?) against itself
(127.0.0.1) so I'm not sure what is going on there.
Thanks,
John.
--
---------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: [EMAIL PROTECTED] Fax: +44 (0)1752 233839
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
