[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnu-radius] is it bug or not?
From: |
Andriy Tkachuk |
Subject: |
Re: [Bug-gnu-radius] is it bug or not? |
Date: |
Mon, 17 Mar 2003 11:43:12 +0200 (EET) |
Hi, Sergey.
(0.96.4)
info radius:
`time-to-live'
Sets the request time-to-live in seconds. The time-to-live is the
time to wait for the completion of the request. If the request job
isn't completed within this interval of time it is cleared, the
corresponding child process killed and the request removed from
the queue.
`request-cleanup-delay'
Sets the request cleanup delay in seconds, i.e. determines how
long will the completed account request reside in the queue.
On Mon, 17 Mar 2003, Sergey Poznyakoff wrote:
> > It seems to me that radiusd drops
> > the start request from the queue if
> > there already stop comes regardless of
> > request-cleanup-delay parameter
>
> No, it does not. A request is dropped only when its lifetime expires.
you mean request-cleanup-delay ?
or time-to-live?
(i think, that it might be request-cleanup-delay)
so, i have in my config:
request-cleanup-delay 60;
for acct
but there are such situations:
(there are requests with same session-id)
Sat Mar 15 11:17:10 2003
^^^^^^^^^^^^^^^^^^^^^^^
Acct-Session-Id = 7818
Cisco-h323-call-origin = h323-call-origin=answer
Cisco-AVPair = h323-incoming-conf-id=BC6377CC 55FD11D7 947CC0E3 217358FE
Cisco-AVPair = subscriber=RegularLine
User-Name = null
Acct-Status-Type = Start
^^^^^
NAS-Port-Type = Async
Cisco-PRI-Circuit = ISDN 2:D:27
NAS-Port-Id = 27
Cisco-AVPair = interface=ISDN 2:D:27
Calling-Station-Id = 4907364
Called-Station-Id = 78123947838
Service-Type = Login-User
NAS-IP-Address = bb (i changed it here)
Acct-Delay-Time = 0
Orig-NAS-Port-Id = 0
Voip-Call-Leg-Type = answer
Timestamp = 1047719830
Request-Authenticator = Verified
Sat Mar 15 11:17:11 2003
^^^^^^^^^^^^^^^^^^^^^^^^
Acct-Session-Id = 7818
Cisco-h323-call-origin = h323-call-origin=answer
Cisco-AVPair = h323-incoming-conf-id=BC6377CC 55FD11D7 947CC0E3 217358FE
Cisco-AVPair = subscriber=RegularLine
Acct-Input-Octets = 0
Acct-Output-Octets = 0
Acct-Input-Packets = 0
Acct-Output-Packets = 0
Acct-Session-Time = 0
Cisco-h323-disconnect-cause = h323-disconnect-cause=22
Cisco-AVPair = h323-ivr-out=Tariff:Unknown
Cisco-AVPair = gw-rxd-cdn=78123947838
Cisco-AVPair = gw-rxd-cgn=4907364
Acct-Status-Type = Stop
^^^^
NAS-Port-Type = Async
Cisco-PRI-Circuit = ISDN 2:D:27
NAS-Port-Id = 27
Cisco-AVPair = interface=ISDN 2:D:27
Calling-Station-Id = 4907364
Called-Station-Id = 78123947838
Service-Type = Login-User
NAS-IP-Address = bb
Acct-Delay-Time = 0
Orig-NAS-Port-Id = 0
Voip-Disconnect-Cause = 34
Voip-Call-Leg-Type = answer
Timestamp = 1047719831
Request-Authenticator = Verified
Sat Mar 15 11:17:25 2003
^^^^^^^^^^^^^^^^^^^^^^^^
Acct-Session-Id = 7818
Cisco-h323-call-origin = h323-call-origin=answer
Cisco-AVPair = h323-incoming-conf-id=BC6377CC 55FD11D7 947CC0E3 217358FE
Cisco-AVPair = subscriber=RegularLine
User-Name = null
Acct-Status-Type = Start
^^^^^
NAS-Port-Type = Async
Cisco-PRI-Circuit = ISDN 2:D:27
NAS-Port-Id = 27
Cisco-AVPair = interface=ISDN 2:D:27
Calling-Station-Id = 4907364
Called-Station-Id = 78123947838
Service-Type = Login-User
NAS-IP-Address = bb
Acct-Delay-Time = 15
Orig-NAS-Port-Id = 0
Voip-Call-Leg-Type = answer
Timestamp = 1047719845
Request-Authenticator = Verified
and radiusd does not recognize the it as duplicate
and as the result invokes acct_start_query
What do you think about this, Sergey?
Am i miss something?
Thank you in advance.
>
> Regards,
> Sergey
>
--
Because strait is the gate, and narrow is the way, which leadeth unto
<b>life</b>, and few there be that find it. (MAT 7:14)
<b>Ask</b>, and it shall be given you; <b>seek</b>, and ye shall find;
<b>knock</b>, and it shall be opened unto you... (MAT 7:7)
ANT17-RIPE