Hello everybody,
This is my first message to the list and I beg you pardon if I don't
use it the correct way.
Well, this is the matter, I'm having problems with accounting packets,
particularly with the lost of "stop" accounting packets. According to
the manuals, I though using AscendSNMP will solve the problem. But
something is going wrong with it.
I've searched the list archive and found some messages related with
this subject, particularly some posted by Hector Lopez on july 16th
"Duplicate login control using AscendSNMP" , but I can't find the
solution the list gave to Hector.
When I enable AscendSNMP, RADIATOR stops working after sending the log
message:
Wed Dec 22 16:45:27 1999: NOTICE: BDS Session for spaz@wanadoo at
x.x.x.x:57 has gone away
Wed Dec 22 16:45:27 1999: NOTICE: BDS Session for spaz@wanadoo at
x.x.x.x:57 has gone away
This is the part of my radiator.cfg file where AscendSNMP is
configured:
SnmpgetProg /usr/local/bin/snmpget
<Client x.x.x.x>
Secret yyyyyy
NasType AscendSNMP
SNMPCommunity zzzzzz
IdenticalClients ( some other clients )
</Client>
We are using a radius proxy server between the NAS and radiator. So
accounting passes trough this server. Could this cause any problem when
using AscendSNMP to interact directly with the NAS?
please, can someone tell me what I'm doing wrong or if this has been
discussed before on the list?
Thanks in advance.
--
CTV-JET Uni2 [http://www.ctv.es]
Vicente Ferrando / [EMAIL PROTECTED]
Dpto. Sistemas / Ingeniero de Sistemas / System Engineer
Tel: +34 96 584 52 91 - Fax: +34 96 584 48 96
---
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
