Hello Vincente,
On Dec 24, 9:28am, Vicente Ferrando wrote:
> Subject: (RADIATOR) Problems using AscendSNMP.
> Hello everybody,
>
> This is my first message to the list and I beg you pardon if I don't
> use it the correct way.
Yes, this is 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?
When you put NasType AscendSNMP in you Client, it means that Radiator will try
to use SNMP to contact the NAS to double check duplicate logins.
Now, if the requests appear to come from a NAS that does not actually have SNMP
support, or, if there is a connectivity problem to the NAS, or if your
community is wrong, then Radiator will have trouble doing the SNMP. The result
will often be long delays as each SNMP times out.
If there is a proxy between Radiator and the NASs, its a good bet that you cant
contact the NAS by SNMP from where you are. If you can confirm that I would
suggest you delete the NasType AscendSNMP from your CLient clause.
Hope that helps.
Cheers.
> 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.
>-- End of excerpt from Vicente Ferrando
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
