Re: (RADIATOR) Strange Problem, no billing data
Hugh,
Thanks for looking at the files. This dose not explain why there is no
billing data on the database though. So from this you can see that the
accounting data is sent back and acknowleged by the radius server is
that correct ? So am i right in assuming that my problem lies between
radiator and the database not between radiator and the router ??
Regards,
Marcel
Hugh Irvine wrote:
Hello Marcel -
Thanks for sending the trace.
As far as I can see everything is working correctly.
Here is what is happening with the accounting requests:
Tue Mar 12 05:03:14 2002: DEBUG: Packet dump:
*** Received from 202.65.74.130 port 1646
Code: Accounting-Request
Identifier: 125
Authentic: ]13317253Hg186207194jg216248251159227
Attributes:
NAS-IP-Address = 202.65.74.17
NAS-Port = 33
NAS-Port-Type = Async
User-Name = macmahon
Acct-Status-Type = Start
Acct-Authentic = RADIUS
Service-Type = Framed-User
Acct-Session-Id = 03A0
Framed-Protocol = PPP
Acct-Delay-Time = 0
Tue Mar 12 05:03:14 2002: DEBUG: Handling request with Handler 'Realm=DEFAULT'
Tue Mar 12 05:03:14 2002: DEBUG: Adding session for macmahon, 202.65.74.17,
33
Tue Mar 12 05:03:14 2002: DEBUG: Handling with Radius::AuthEMERALD
Tue Mar 12 05:03:14 2002: DEBUG: Handling accounting with Radius::AuthEMERALD
Tue Mar 12 05:03:15 2002: DEBUG: do query is: insert into Calls
(UserName, CallDate, AcctStatusType, AcctDelayTime,
AcctSessionId, NASIdentifier, NASPort)
values
('macmahon', 'Mar 12, 2002 05:03', 1, 0, '03A0',
'202.65.74.17', 33)
Tue Mar 12 05:03:15 2002: DEBUG: Accounting accepted
Tue Mar 12 05:03:15 2002: DEBUG: Packet dump:
*** Sending to 202.65.74.130 port 1646
Code: Accounting-Response
Identifier: 125
Authentic: ]13317253Hg186207194jg216248251159227
Attributes:
As you can see - the accounting request results in a record inserted into the
Calls table with the values shown, and an accounting response is then sent
back to the client.
regards
Hugh
On Tue, 12 Mar 2002 12:02, Marcel Welschbillig wrote:
Hugh,
I have attached a debug trace 4 and the radiator config, found it wasn't
the one i sent you earlier but this is the one.
Thanks in advance !
Marcel
Hugh Irvine wrote:
Hello Marcel -
Thanks for sending the debug.
It appears that you are sending the radius accounting to 202.65.68.8:1646
and the authentication to 202.65.68.8:1645. There is a response from the
radius server in both cases.
Could you please send me a copy of your configuration file (no secrets)
together with a trace 4 debug from Radiator showing what is happening.
thanks
Hugh
On Mon, 11 Mar 2002 17:02, Marcel Welschbillig wrote:
Hugh,
Thanks for the reply. I have attached the config and debug info, i have
looked at this for many days and found nothing obvious (my knowlege on
radius is limited) and tried many different things and come to no
conclusion. If you can see anything wrong please let me know. Also i
have removed all filters and access lists on the routers between here
and there and had no luck.
Regards,
Marcel
Hugh Irvine wrote:
Hello Marcel -
It sounds like the 2611 is not configured correctly for radius
accounting.
You should do a debug on the 2611 to see what it is doing. You might
also check your access lists and filters, as the accounting port number
is different from the authentication port (1645/1812 and 1646/1813).
regards
Hugh
On Mon, 11 Mar 2002 16:31, Marcel Welschbillig wrote:
Hi,
Was hopping someone can shed some light on our problem, the story goes
like this.
We are running radiator with platypus billing system and things are
working fine on our local ISP system. We recently got into the
satellite telecommunications business and decided to put a 2611 router
out on a remote site with an 8AM analog modem module to provide access
to the data stream and authenticate via radiator/platypus. The data
stream is via VSAT satellite equipment ( Basicly a serial at both
routers with VSAT equipment between, using HDSL Encapsulation,
introduces about 700ms delay round trip )
The strange thing is that i can seem to authenticate from the remote
2611 but there is no call/download information sent back. The radius
server and platypus server are local and work fine with our other
access servers. Why can it authenticate over the SAT link but not send
the billing data back ?? I know the radius server and platypus server
are configured correctly because they are accounting for our loacl
dialin customers, the router is configured nearly identical to our
access servers with regards to CISCO aaa.
Any help would be great, i have tried just about everything and dont
know where to go next.
===
Archive at http://www.open.com.au/archives/radiator
Re: (RADIATOR) Strange Problem, no billing data
Hugh, Thanks for the reply. I have attached the config and debug info, i have looked at this for many days and found nothing obvious (my knowlege on radius is limited) and tried many different things and come to no conclusion. If you can see anything wrong please let me know. Also i have removed all filters and access lists on the routers between here and there and had no luck. Regards, Marcel Hugh Irvine wrote: Hello Marcel - It sounds like the 2611 is not configured correctly for radius accounting. You should do a debug on the 2611 to see what it is doing. You might also check your access lists and filters, as the accounting port number is different from the authentication port (1645/1812 and 1646/1813). regards Hugh On Mon, 11 Mar 2002 16:31, Marcel Welschbillig wrote: Hi, Was hopping someone can shed some light on our problem, the story goes like this. We are running radiator with platypus billing system and things are working fine on our local ISP system. We recently got into the satellite telecommunications business and decided to put a 2611 router out on a remote site with an 8AM analog modem module to provide access to the data stream and authenticate via radiator/platypus. The data stream is via VSAT satellite equipment ( Basicly a serial at both routers with VSAT equipment between, using HDSL Encapsulation, introduces about 700ms delay round trip ) The strange thing is that i can seem to authenticate from the remote 2611 but there is no call/download information sent back. The radius server and platypus server are local and work fine with our other access servers. Why can it authenticate over the SAT link but not send the billing data back ?? I know the radius server and platypus server are configured correctly because they are accounting for our loacl dialin customers, the router is configured nearly identical to our access servers with regards to CISCO aaa. Any help would be great, i have tried just about everything and dont know where to go next. areac-rtr# 1w2d: Async33 AAA/DISC: 2/Lost Carrier 1w2d: Async33 AAA/DISC/EXT: 1011/Lost Carrier 1w2d: AAA/ACCT/ACCT_DISC: Found list default 1w2d: Async33 AAA/DISC: 2/Lost Carrier 1w2d: AAA/ACCT/ACCT_DISC: Found list default 1w2d: Async33 AAA/DISC/EXT: 1011/Lost Carrier 1w2d: AAA/ACCT/ACCT_DISC: Found list default 1w2d: Async33 AAA/DISC: 2/Lost Carrier 1w2d: AAA/ACCT/ACCT_DISC: Found list default 1w2d: Async33 AAA/DISC/EXT: 1011/Lost Carrier 1w2d: AAA/ACCT: no attribute pre-bytes-in to replace, adding it 1w2d: AAA/ACCT: no attribute pre-bytes-out to replace, adding it 1w2d: AAA/ACCT: no attribute pre-paks-in to replace, adding it 1w2d: AAA/ACCT: no attribute pre-paks-out to replace, adding it 1w2d: AAA/ACCT: no attribute bytes_in to replace, adding it 1w2d: AAA/ACCT: no attribute bytes_out to replace, adding it 1w2d: AAA/ACCT: no attribute paks_in to replace, adding it 1w2d: AAA/ACCT: no attribute paks_out to replace, adding it 1w2d: AAA/ACCT: no attribute pre-session-time to replace, adding it 1w2d: AAA/ACCT: no attribute elapsed_time to replace, adding it 1w2d: AAA/ACCT non-ISDN xmit=33600 recv=33600 hwidb=81E5FA20 tty=81E5E1A8 1w2d: AAA/ACCT/NET/STOP User macmahon, Port Async33: task_id=30 timezone=GMT+8 service=ppp protocol=ip addr=192.168.30.2 disc-cause=1 disc-cause-ext=1045 pre-bytes-in=99 pre-bytes-out=105 pre-paks-in=4 pre-paks-out=4 bytes_in=1175927 bytes_out=971570 paks_in=14840 paks_out=18630 pre-session-time=4 connect-progress=60 elapsed_time=3815 nas-rx-speed=33600 nas-tx-speed=33600 1w2d: AAA/ACCT: user macmahon, acct type 2 (3797123294): Method=radius (radius) 1w2d: RADIUS: ustruct sharecount=3 1w2d: RADIUS: Initial Transmit Async33 id 188 202.65.68.8:1646, Accounting-Request, len 130 1w2d: Attribute 4 6 CA414A11 1w2d: Attribute 5 6 0021 areac-rtr# 1w2d: Attribute 61 6 1w2d: Attribute 1 10 6D61636D 1w2d: Attribute 40 6 0002 1w2d: Attribute 45 6 0001 1w2d: Attribute 6 6 0002 1w2d: Attribute 44 10 30303030 1w2d: Attribute 7 6 0001 1w2d: Attribute 8 6 C0A81E02 1w2d: Attribute 49 6 0001 1w2d: Attribute 42 6 0011F177 1w2d: Attribute 43 6 000ED332 1w2d: Attribute 47 6 39F8 1w2d: Attribute 48 6 48C6 1w2d: Attribute 46 6 0EE7 1w2d: Attribute 41 6 1w2d: RADIUS: Received from id 188 202.65.68.8:1646, Accounting-response, len 20 1w2d: %LINK-5-CHANGED: Interface Async33, changed state to reset areac-rtr# 1w2d: As33 AAA/DISC: 2/Lost Carrier 1w2d: As33 AAA/DISC/EXT: 1011/Lost Carrier areac-rtr# 1w2d: Async33: Async protocol mode stopped for 0.0.0.0 1w2d: AAA/MEMORY: free_user (0x81B7FDD0) user='macmahon' ruser='' port='Async33' rem_addr='async' authen_type=PAP service=PPP priv=1 areac-rtr# 1w2d: %LINK-3-UPDOWN: Interface Async33, changed state to down areac-rtr# 1w2d: As33 AAA
