This has more to do with Max TNT itself than with Radiator, hope
someone working with Max TNT could help me:
I´d like to prevent anyone to telnet to the Max TNT unit, except
from my management network segment. I could make this to work setting up the
filter in the Max TNT (filter
I have the same error too, when proxying to other hosts.
242 is Ascend-Data-Filter and its well defined in my dictionary. The
filter does work allright aswell.
Thu May 11 10:16:20 2000: ERR: Attribute number 242 (vendor 529) is
not defined in your dictionary
Thu
s Manager
> Internet Direct, Inc. <http://www.idworld.net/>
>
> > -----Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of ARG-MENENDEZ, JUAN
> > Sent: Tuesday, March 07, 2000 7:24 AM
> > To: '[EMAIL PROTECTED]&#x
t; To: ARG-MENENDEZ, JUAN; '[EMAIL PROTECTED]'
> Subject: Re: (RADIATOR) Radiator & MAX TNT
>
>
> Hello Juan -
>
> On Tue, 07 Mar 2000, ARG-MENENDEZ, JUAN wrote:
> > I been doing some tests with Radiator Demo Version 2.15 & some
> > Ciscos 2511/5300
I been doing some tests with Radiator Demo Version 2.15 & some
Ciscos 2511/5300 and everything went allright.
We also have some MAX TNTs here and I noticed the MAX TNT unit is
sending ´garbage´ to the radius server (I can only see it if I configure
loglevel to trace 4), although
