Proxy (check status of the 3rd party server)

[Peter Balsianok]

Fri Aug 14 16:31:17 2015 : Debug: (2) proxy: Trying to allocate ID (0/2)
Fri Aug 14 16:31:17 2015 : Debug: (2) proxy: request is now in proxy hash
Fri Aug 14 16:31:17 2015 : Debug: (2) proxy: allocating destination
127.0.0.1 port 61813 - Id 215
Fri Aug 14 16:31:17 2015 : Debug: PING: Waiting 4 seconds for response to
ping
Fri Aug 14 16:31:17 2015 : Debug: (2) Sent Status-Server Id 215 from
0.0.0.0:37576 to 127.0.0.1:61813 length 0
Fri Aug 14 16:31:17 2015 : Debug: (2)   Message-Authenticator := 0x00
Fri Aug 14 16:31:17 2015 : Debug: (2)   NAS-Identifier := "Status Check 1.
Are you alive?"
50 12 ...
20 20  53 74 61 74 75 73 20 43 68 65 63 6b 20 31 2e 20
41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f
  Socket: 13
  Proto: 0
  Src IP: 0.0.0.0
    port: 37576
  Dst IP: 127.0.0.1
    port: 61813
  Code: 12
  Id: 215
  Length: 70
  Vector: 56dd3fb2660db32c59405402f78de7d4
  Data: 50  12  f4 df 14 78 db d0 45 66 0b 15 4f 71 88 de 47 06
20  20  53 74 61 74 75 73 20 43 68 65 63 6b 20 31 2e 20
41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f
Fri Aug 14 16:31:17 2015 : Debug: PING: Next status packet in 6 seconds
Fri Aug 14 16:31:17 2015 : Debug: Waking up in 3.9 seconds.
  Socket: 13
  Proto: 0
  Src IP: 127.0.0.1
    port: 61813
  Dst IP: 127.0.0.1
    port: 37576
  Code: 5
  Id: 215
  Length: 20
  Vector: cd395b6837e57b2ed82175fffbe94dba
Fri Aug 14 16:31:17 2015 : Proxy: No outstanding request was found for
Accounting-Response packet from host 127.0.0.1 port 61813 - ID 215


On Fri, Aug 14, 2015 at 3:35 PM, Peter Balsianok <balsianok.peter at gmail.com>
wrote:

> Debug output (accounting server):
> Fri Aug 14 15:33:24 2015 : Debug: (2) proxy: Trying to allocate ID (0/2)
> Fri Aug 14 15:33:24 2015 : Debug: (2) proxy: request is now in proxy hash
> Fri Aug 14 15:33:24 2015 : Debug: (2) proxy: allocating destination
> 127.0.0.1 port 61813 - Id 65
> Fri Aug 14 15:33:24 2015 : Debug: PING: Waiting 4 seconds for response to
> ping
> Fri Aug 14 15:33:24 2015 : Debug: (2) Sent Status-Server Id 65 from
> 0.0.0.0:39764 to 127.0.0.1:61813 length 0
> Fri Aug 14 15:33:24 2015 : Debug: (2)   Message-Authenticator := 0x00
> Fri Aug 14 15:33:24 2015 : Debug: (2)   NAS-Identifier := "Status Check 1.
> Are you alive?"
> 50 12 ...
> 20 20  53 74 61 74 75 73 20 43 68 65 63 6b 20 31 2e 20
> 41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f
>   Code: 12
>   Id: 65
>   Length: 70
>   Vector: 70a010641803b9f6c5019325204e8bd3
>   Data: 50  12  20 f5 e8 9b 36 55 22 13 c4 f9 6e 71 f4 39 cf ea
> 20  20  53 74 61 74 75 73 20 43 68 65 63 6b 20 31 2e 20
> 41 72 65 20 79 6f 75 20 61 6c 69 76 65 3f
> Fri Aug 14 15:33:24 2015 : Debug: PING: Next status packet in 6 seconds
> Fri Aug 14 15:33:24 2015 : Debug: Waking up in 3.9 seconds.
>   Code: 5
>   Id: 65
>   Length: 20
>   Vector: 0b2dc4a4cb1eef4b89f64dbdd20744ed
> Fri Aug 14 15:33:24 2015 : Proxy: No outstanding request was found for
> Accounting-Response packet from host 127.0.0.1 port 61813 - ID 65
>
>
> Debug output (3rd party server):
> Listening on acct address 127.0.0.1 port 61813 bound to server default
> Ready to process requests
> (0) Received Status-Server Id 65 from 127.0.0.1:39764 to 127.0.0.1:61813
> length 70
> (0)   Message-Authenticator = 0x20f5e89b36552213c4f96e71f439cfea
> (0)   NAS-Identifier = "Status Check 1. Are you alive?"
> (0) Sent Accounting-Response Id 65 from 127.0.0.1:61813 to 127.0.0.1:39764
> length 0
> (0) Finished request
> Waking up in 1.9 seconds.
> (0) <done>: Cleaning up request packet ID 65 with timestamp +4
> Ready to process requests
> (1) Received Status-Server Id 21 from 127.0.0.1:39764 to 127.0.0.1:61813
> length 70
> (1)   Message-Authenticator = 0x557c9db0ae54d9e837a06151a5f7d951
> (1)   NAS-Identifier = "Status Check 2. Are you alive?"
> (1) Sent Accounting-Response Id 21 from 127.0.0.1:61813 to 127.0.0.1:39764
> length 0
> (1) Finished request
> Waking up in 1.9 seconds.
>
>
>
> On Fri, Aug 14, 2015 at 3:30 PM, Peter Balsianok <
> balsianok.peter at gmail.com> wrote:
>
>> [radiusd at tdrad1 acct-test]$ cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release 5.11 (Tikanga)
>>
>> A virtual machine on the ESX server
>>
>> Status-Server -> Yes i can try
>>
>> On Fri, Aug 14, 2015 at 3:18 PM, Alan DeKok <aland at deployingradius.com>
>> wrote:
>>
>>> On Aug 14, 2015, at 2:23 PM, Peter Balsianok <balsianok.peter at gmail.com>
>>> wrote:
>>>
>>>   Hmm... what kind of system are you running? i.e. is this a container?
>>> A plain OS?  What is unusual about this?
>>>
>>>   Can you try using Status-Server packets for the checks, instead of
>>> Accounting-Request packets?
>>>
>>>   Alan DeKok.
>>>
>>>
>>> -
>>> List info/subscribe/unsubscribe? See
>>> http://www.freeradius.org/list/users.html
>>>
>>
>>
>