--- Forwarded mail from [EMAIL PROTECTED]
Date: Fri, 9 Jun 2000 14:40:27 +1000 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from ["Aaron
Liu" <[EMAIL PROTECTED]>]
>From mikem Fri Jun 9 14:40:23 2000
Received: by oscar.open.com.au (8.9.0/8.9.0) id OAA17421
for [EMAIL PROTECTED]; Fri, 9 Jun 2000 14:40:22 +1000 (EST)
>Received: from china.asiainter.net (asiainter.net [202.84.207.2]) by
perki.connect.com.au with SMTP id OAA12218
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Fri, 9 Jun 2000 14:37:41 +1000
(EST)
Received: from china.asiainter.net (asiainter.net [202.84.207.2]) by
perki.connect.com.au with SMTP id OAA12218
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Fri, 9 Jun 2000 14:37:41 +1000
(EST)
Received: (qmail 6323 invoked from network); 9 Jun 2000 04:37:27 -0000
by asiainter.net with SMTP; 9 Jun 2000 04:37:27 -0000
/var/spool/mailq/960525447.6322.chinaReceived: from unknown (HELO aaron)
(203.161.225.233)
by asiainter.net with SMTP; 9 Jun 2000 04:37:27 -0000
Message-ID: <001b01bfd1cc$799e1500$[EMAIL PROTECTED]>
From: "Aaron Liu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Duplicate records in accounting log
Date: Fri, 9 Jun 2000 12:37:26 +0800
Organization: FirstEcom
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
charset="big5"
Hi all,
I am working on a new installation at a client site. The client is using
a mix of Ascend Max 4000 and TNT as NAS. We noticed that the NAS tried to
send multiple requests to Radiator with a slightly different Acct-Delay-Time
but same Session ID. The problem is that currently their existing billing
system cannot handle duplicate records in the accounting log. When I read in
the source code, I noticed this is a known problem, in particular:
In Client.pm (near the section that handles DupInterval):
[...]
# BUG ALERT: this _wont_ catch retransmissions of
# accounting where the Acct-Delay-Time has changed, because
# the identifier will also have changed. Gag.
[...]
I have tried to modified the source code (by adding one more hash to
store Session ID with NAS IP, port and status type as the key) to trap this
particular situation. I am able to detect this situation. From the original
comment in the source code it seems that accounting log will not be
generated for duplicating requests. However, it seems that the accounting
log is still written no matter what. Did there anyone here encounter the
same problem? Am I looking at the wrong place of source code? I know that I
can write another script to pre-process the accounting log before feeding it
to their billing system but our client wants a cleaner solution (that fits
inside Radiator). Any suggestions will be welcome.
--
Aaron Liu
---End of forwarded mail from [EMAIL PROTECTED]
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
2000, NT, MacOS X
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
