it's not what i wanted actually... you should take a look at the messages and decide if the ACK IS valid or where it becomes invalid and perhaps why... it's probably invalid at the server-side, otherwise the server wouldn't say it. but why? and where has it been changed? is it wrong when coming from the supplicant? ...
etc.... what you've sent now doesn't help much more than what you sent before, since there is usually exactly one ack... (well, you should send the whole logs anyway). well, at least me still have no clue. try ethereal... or before: are you using a cisco 350/340? do you have the newest firmware? try to update it. you should have anything newer than 11.21 should be just fine. try using those :eap_diag1_on, :eap_diag2_on flags ciao artur -- Artur Hecker artur[at]hecker.info - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
