I have this same problem with one of my radius servers. I've checked, and re-checked the shared secrets and they match. Also, if they didn't match then I wouldn't be able to authenticate on the server as the passwords would be garbled. Correct? The users are able to authenticate fine however.. It's very odd..

It's not really a big deal in my situation because all the accounting is handled by the proxy server. Just an annoyance to have the errors shown in the logs. They look something like this..

Sat Mar 29 13:41:42 2003 : Error: Received Accounting-Response packet from 1.2.3.4 with invalid signature!

Darren


Alan DeKok wrote:
Squirrel User <[EMAIL PROTECTED]> wrote:

Didn't recall anything about "Invalid Signature" in FAQ. I searched on google and found couple of references mentioning the problem regards to mismatch of shared secrets between NAS and clients.conf, suggesting retype of secrets. FAQ also mentions that if shared secrets don't match, the password will be garbled.


"Invalid signature" means that the shared secret is wrong.


But when I do the radtest, the password shows correct.  And
strangely, before it authenticated fine, but now it won't.


  Passwords aren't sent in accounting packets.  Try sending the server
accounting packets.

Alan DeKok.

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html





- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to