Re: %RAD_REPLY hash problem

2010-11-08 Thread Ana Gallardo
Hello, I've tested adding my vendor specific attributes to check list, and the problem persist. Here is the debug info: rad_recv: Access-Request packet from host x.x.x.x port 32880, id=4, length=75 User-Name = a...@unex.es User-Password = 111 Calling-Station-Id = ... ...

Re: %RAD_REPLY hash problem

2010-10-29 Thread Ana Gallardo
Hello, thank you very much for your response. I’m not sure if this will fix it, but try: use constant RLM_MODULE_UPDATED= 8;# /* OK (pairs modified) */ then change “return RLM_MODULE_OK” to: return RLM_MODULE_UPDATED; I try that but the problem persist. If this doesn’t fix

RE: %RAD_REPLY hash problem

2010-10-29 Thread Garber, Neal
Yes, I know :) but it would be better if we can solve that I agree, but I haven't found a better solution (i.e., that's what I do to workaround the problem). - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: %RAD_REPLY hash problem

2010-10-26 Thread Garber, Neal
My problem is that rlm_perl duplicate an attribute in %RAD_REPLY hash. I'm not sure if this will fix it, but try: use constant RLM_MODULE_UPDATED= 8;# /* OK (pairs modified) */ then change return RLM_MODULE_OK to: return RLM_MODULE_UPDATED; If this doesn't fix it, you can always delete