Thank very much for help. We are using Redhat & Debian. The test was done on the Redhat Here is debug output: Fri Aug 14 13:23:20 2015 : Debug: (3) proxy: Trying to allocate ID (0/2) Fri Aug 14 13:23:20 2015 : Debug: (3) proxy: request is now in proxy hash Fri Aug 14 13:23:20 2015 : Debug: (3) proxy: allocating destination 127.0.0.1 port 61813 - Id 198 Fri Aug 14 13:23:20 2015 : Debug: PING: Waiting 4 seconds for response to ping 01 0f 6f 72 61 6e 67 65 2d 73 79 73 74 65 6d 28 06 00 00 00 02 2c 0a 30 30 30 30 30 30 30 30 37 06 55 cd cf a8 20 20 53 74 61 74 75 73 20 43 68 65 63 6b 20 32 2e 20 41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f Code: 4 Id: 198 Length: 89 Vector: daa7f1987b6f95c70b87dbdfa2d12a2a Data: 01 0f 6f 72 61 6e 67 65 2d 73 79 73 74 65 6d 28 06 00 00 00 02 2c 0a 30 30 30 30 30 30 30 30 37 06 55 cd cf a8 20 20 53 74 61 74 75 73 20 43 68 65 63 6b 20 32 2e 20 41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f Fri Aug 14 13:23:20 2015 : Debug: PING: Next status packet in 6 seconds Fri Aug 14 13:23:20 2015 : Debug: Waking up in 3.9 seconds. Code: 5 Id: 198 Length: 20 Vector: 4c86d4e105670d850481902077ab2fe1 Fri Aug 14 13:23:20 2015 : Proxy: No outstanding request was found for reply from host 127.0.0.1 port 61813 - ID 198 Fri Aug 14 13:23:20 2015 : Debug: Waking up in 3.9 seconds. On Fri, Aug 14, 2015 at 11:17 AM, Alan DeKok <aland@deployingradius.com> wrote:
Please try the v3.0.x branch from git. I've put some more debugging messages in for Status-Server packets.
My guess is you're using FreeBSD. It's networking is a bit different than Linux, so some of the assumptions in the code were wrong. I've put in fixes which are better for matching replies to requests.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html