Hello Marcel -
Yes the accounting requests are being sent to Radiator, the trace shows the
accounting records written to the database, and an accounting response is
returned.
As far as the trace shows, the accounting requests are being written to the
database, so you should check there what is going on.
regards
Hugh
On Tue, 12 Mar 2002 13:46, Marcel Welschbillig wrote:
> 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: ]<133><17><253>Hg<186><207><194>jg<216><248><251><159><227>
> > 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 = "000003A0"
> > 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, '000003A0',
> > '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: ]<133><17><253>Hg<186><207><194>jg<216><248><251><159><227>
> > 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.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.