Hello all

[Jon Cash]

Hello all
i use freeradius with the network access control Packetfence
I have a problem with captive portal registration
I use radius authentication and i have this problem when i put login pass in
the authentication page

rad_recv: Access-Request packet from host 127.0.0.1 port 47764, id=171,
length=50
        User-Name = "user"
        User-Password = "\026JoL\267\277O\235:~\327\374\367"
        NAS-IP-Address = 127.0.0.1
server packetfence {
+- entering group authorize {...}
[suffix] No '@' in User-Name = "user", looking up realm NULL
[suffix] No such realm "NULL"
++[suffix] returns noop
++[preprocess] returns ok
[eap] No EAP-Message, not doing EAP
++[eap] returns noop
[files] users: Matched entry user at line 2
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
rlm_perl: Added pair User-Name = user
rlm_perl: Added pair User-Password = \026JoL\267\277O\235:~\327\374\367
rlm_perl: Added pair NAS-IP-Address = 127.0.0.1
rlm_perl: Added pair Cleartext-Password = pass
++[perl] returns noop
WARNING: Please update your configuration, and remove 'Auth-Type = Local'
WARNING: Use the PAP or CHAP modules instead.
User-Password in the request does NOT match "known good" password.
Failed to authenticate the user.
} # server packetfence
Using Post-Auth-Type Reject
+- entering group REJECT {...}
[attr_filter.access_reject]     expand: %{User-Name} -> user
 attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 33 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 33
Sending Access-Reject of id 171 to 127.0.0.1 port 47764
Waking up in 4.9 seconds.
Cleaning up request 33 ID 171 with timestamp +1302
Ready to process requests.

the password match in user file

any idea please

cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110810/a9c7c256/attachment.html>