Dinko Korunic <[EMAIL PROTECTED]> wrote:
> I have, in fact. You're not going to like the answer - it seems that
> current rlm_mschap isn't endian-clean.

  That's at least an explanation as to why it doesn't work.

  Now that we know that, it's possible to track down the problem.

  You can use the test attributes I posted earlier, and hack
rlm_mschap so that it prints out a bunch of numbers it's calculated.
e.g.

  MSCHAP: Step 1 879
  MSCHAP: Step 2 58721674267
  ...

  You can then run it on two machines, use 'grep' to pull out the
MSCHAP lines from the debug log, and then use 'diff' to see where they
differ.  This will let you track down where the problem occurs.

  Alan DeKok.


  

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

Reply via email to