(RADIATOR) FW: Comindico DialIP Ports

Mon Aug 26 18:42:54 CDT 2002

Hi Skeeve,

What you may notice, is these packets also contain the attribute "Tunnel-Id"
These attributes will match the two packets, perhaps you could use that in
order to collect the two packets correctly.

I have to battle that one myself in a few days, I have suggested to
COMindico engineers that perhaps they could attempt to combine the packets
from their end, as their response in regards to handling StaticIP Accounting
was to simply ignore the second packet. I don't believe this is going to
happen :-)

The reason for the packet is the startpoint and endpoint sections from the
L2TP tunnel formed..
I guess the question, do you require any of the information that is only
held in one of the packets?
For instance, the packets below are two example start packets for the same
user..

The first packet is generated from the NAS, the second from the LNS Server.
As you'll notice, most of the information here is duplicated, besides the
important things like Session-Id's and the like.  The LNS Server Packet
seems to have little useful information.

I also noticed, from the Alive packets, we only get Alive packets for the
NAS Record (SessionId: 0000F316).

With this, I would say, as much as it's throwing away information, ignore
the second packet, perhaps with:

<Handler NAS-Port-Type=/Virtual/>
 <AuthBy SOMETHING>
		...
 </AuthBy>
</Handler>

(However, if you resell Request, make sure ignoring NAS-Port-Type doesn't
affect billing there too.. as NAS-Port-Type = Virtual is used there too I
think)

Thanks
Martin

*** Received from 203.194.56.121 port 1813 ....
Code:       Accounting-Request
Identifier: 114
Authentic:  ho-<199><128>k<159>]<30>6<139><165>i|x<26>
Attributes:
        NAS-IP-Address = 203.220.251.113
        NAS-Port = 6204
        NAS-Port-Type = Async
        Called-Station-Id = "142320198333401"
        Calling-Station-Id = "891751477"
        Acct-Status-Type = Start
        Acct-Authentic = Local
        Service-Type = Framed-User
        Acct-Session-Id = "0000F316"
        Framed-Protocol = PPP
        Tunnel-Server-Endpoint = 50:03.194.30.244
        Tunnel-Client-Endpoint = 50:03.220.251.65
        Tunnel-Client-Auth-ID = 65:CC01-WARA-KTA
        Tunnel-Server-Auth-ID = 76:NS01-KENT-SYD
        Tunnel-ID = 49:441000076
        Ascend-Session-Svr-Key = "xxxxxxxxxx"
        Acct-Delay-Time = 0
        User-Name = "eastpilb"
        Proxy-State =
BSP2ims01-syd/E084B8A3558A933FC21E351925257349AAEAD1F20F70D16B8156A80724198C
3F9780E2B10F70D3474A8A53D522
7794019780E2ED0F62DB2EB025DCCB4220DC54D0B191996016EA66D611CDC5576DE46AFBE2

------------- TUNNEL PACKET -----------------
Pros: Nothing. Appears most of the information below is duplicated above.
Cons: Doesn't tell you where the user dialed up (the NAS-IP-Address is
COMindico's LNS Server)

*** Received from 203.194.28.132 port 1813 ....
Code:       Accounting-Request
Identifier: 43
Authentic:  <133>T0<155><154><156>P<129><204><144><235><181>w<176><153>V
Attributes:
        Acct-Session-Id = "000138E8"
        Tunnel-Server-Endpoint = 0:203.194.29.248
        Tunnel-Client-Endpoint = 0:203.220.251.65
        Tunnel-Assignment-ID = 0:1
        Tunnel-ID = 49:441000076
        Tunnel-Client-Auth-ID = 0:ACC01-WARA-KTA
        Tunnel-Server-Auth-ID = 0:LNS01-KENT-SYD
        Framed-Protocol = PPP
        Ascend-Connect-Progress = prCallUp
        Acct-Authentic = RADIUS
        Acct-Status-Type = Start
        NAS-Port = 33
        NAS-Port-Type = Virtual
        Calling-Station-Id = "891751477"
        Called-Station-Id = "142320198333401"
        Service-Type = Framed-User
        NAS-IP-Address = 203.194.30.244
        Event-Timestamp = 1030370079
        Acct-Delay-Time = 0
        User-Name = "eastpilb"
        Proxy-State =
BSP2ims01-syd/1977AAFCDD88DD49DA1DAA988803EF58DDBF6595956F445CA5DF21F972F4CD
C1E0D556D6956F460C6E1D3FCF74
9ACDE2E0D5568A957D4E1994AC555414CD85B7A7E425FEFA097F51F298445A0180BD898CB7

-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au]On
Behalf Of Skeeve Stevens
Sent: Monday, August 26, 2002 11:03 PM
To: radiator at open.com.au
Subject: (RADIATOR) FW: Comindico DialIP Ports

Anyone here have any experience doing the radius accounting with
Comindico DialIP Ports? (Australia)

I am not sure how to deal with their double accounting radius records.

If they had the same session ID this would not be a problem... but they
come from 2 sources with different id's maybe a second or two apart....
and I am really unsure how to differentiate them....

Anyone dealt with this that can help?

...Skeeve

_______________________________________________________
Skeeve Stevens, RHCE     Email: skeeve at skeeve.org
Website: www.skeeve.org  - Telephone: (0414) 753 383
Address: P.O Box 1035, Epping, NSW, 1710, Australia

eIntellego - skeeve at eintellego.net - www.eintellego.net
_______________________________________________________
Si vis pacem, para bellum

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.