Hey Hugh,
You were absolutly right! Thank you so much. As soon as I added the
shared secret to the Accounting, it worked like a charm. I didn't know
that on Ascends you have to set a secret for accounting like you do for
authentication. Good lesson for me, I guess :)
Again, thanks a lot...
On Thu, 15 Jun 2000, Hugh Irvine wrote:
>
> Hello Garry -
>
> On Thu, 15 Jun 2000, Garry Shtern wrote:
> > Hi Hugh,
> >
> > Here is the output from DSL Terminatior:
> >
> > RADIF: radius type Acct ID = 100
> > RADIF: _radiusAcctRequest: type 0 id 100, user name <0:>
> > RADIF: _radiusAcctReq: socket 8 len 49 IP 160.79.128.15 port 1026=>1813, ID=100
> > RADIF: _radCallback: buf=81543660 from 160.79.128.15 1813
> > RADIF: _radProcAcctRsp: user:<0:>, ID=100
> > RADIF: _radProcAcctRsp, bad authenticator for buffer 81543660
> > RADIF: _radCallback: processed acct server type=0
> > RADACCT-CP: Handling msg type 16
> > RADIF: radius type Acct ID = 101
> > RADIF: _radiusAcctRequest: type 0 id 101, user name <0:>
> > RADIF: _radiusAcctReq: socket 8 len 49 IP 160.79.128.15 port 1026=>1813, ID=101
> > RADIF: _radCallback: buf=81543660 from 160.79.128.15 1813
> > RADIF: _radProcAcctRsp: user:<0:>, ID=101
> > RADIF: _radProcAcctRsp, bad authenticator for buffer 81543660
> > RADIF: _radCallback: processed acct server type=0
> > RADACCT-CP: Handling msg type 16
> > RADIF: radius type Acct ID = 102
> > RADIF: _radiusAcctRequest: type 0 id 102, user name <0:>
> > RADIF: _radiusAcctReq: socket 8 len 49 IP 160.79.128.15 port 1026=>1813, ID=102
> > RADIF: _radCallback: buf=81543660 from 160.79.128.15 1813
> > RADIF: _radProcAcctRsp: user:<0:>, ID=102
> > RADIF: _radProcAcctRsp, bad authenticator for buffer 81543660
> > RADIF: _radCallback: processed acct server type=0
> > RADACCT-CP: Handling msg type 16
> >
>
> This is the Ascend sending its Accounting On message and it is complaining
> about the authenticator in the reply packet, so it resends the request. This
> usually means that the shared secret is set incorrectly.
>
> If you are sure that the shared secret is correct (verify 1 (one) and l (ell)
> and 0 (zero) and O (oh) especially), then I would suspect a bug in the Ascend
> software. It may also be possible to disable the Accounting On messages in the
> Ascend configuration.
>
> Are the other radius requests from the device handled correctly by Radiator?
>
> thanks
>
> Hugh
>
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/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.
