default configuration no auth-type

[John Dennis]

On 01/03/2014 01:52 PM, Michael Aldridge wrote:
> Having just completely purged and reinstalled freeradius, I cannot get
> the default configuration to work.  Here is the output from a request in
> debug mode:
> 
> rad_recv: Access-Request packet from host 127.0.0.1 port 59114, id=221,
> length=59
>         User-Name = "testing"
>         User-Password = "password"
>         NAS-IP-Address = 127.0.1.1
>         NAS-Port = 0
> # Executing section authorize from file
> /etc/freeradius/sites-enabled/default
> +- entering group authorize {...}
> ++[preprocess] returns ok
> ++[chap] returns noop
> ++[mschap] returns noop
> ++[digest] returns noop
> [suffix] No '@' in User-Name = "testing", looking up realm NULL
> [suffix] No such realm "NULL"
> ++[suffix] returns noop
> [eap] No EAP-Message, not doing EAP
> ++[eap] returns noop
> ++[files] returns noop
> ++[expiration] returns noop
> ++[logintime] returns noop
> [pap] WARNING! No "known good" password found for the user.
>  Authentication may fail because of this.
> ++[pap] returns noop
> ERROR: No authenticate method (Auth-Type) found for the request:
> Rejecting the user
> Failed to authenticate the user.
> Using Post-Auth-Type Reject
> # Executing group from file /etc/freeradius/sites-enabled/default
> +- entering group REJECT {...}
> [attr_filter.access_reject]     expand: %{User-Name} -> testing
>  attr_filter: Matched entry DEFAULT at line 11
> ++[attr_filter.access_reject] returns updated
> Delaying reject of request 0 for 1 seconds
> Going to the next request
> Waking up in 0.9 seconds.
> Sending delayed reject for request 0
> Sending Access-Reject of id 221 to 127.0.0.1 port 59114
> 
> The user and testing were performed following the guide found on the
> freeradius wiki here:
> http://wiki.freeradius.org/guide/Basic-configuration-HOWTO
> 
> any help is greatly appreciated!

Try reading what you posted, the answer is there.

See the line that says:

ERROR: No authenticate method (Auth-Type) found for the request

Hmm ... let's see, why wouldn't there be a password for the user "testing"?

Maybe because you wiped out the user's file where you put that information?


-- 
John