Hello
I've got a big problem. We want to use the following attributes in some
of our user profiles we fetch via replaceIfNotExistProfiles hook and LDAP:
cisco-avpair=ip:addr-pool=setup_pool
cisco-avpair=ip:dns-servers=212.117.64.86 212.117.67.2
cisco-avpair=ip:idletime=89
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
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
What dictionary are you using? I find that if I put the original
dictionary on the proxy server, and the Ascend2 on the authentication
system It works rather well. If you put the Ascend2 on the proxy server I
kept getting errors like you have below.
Hope that helps.
Cortney
At 10:22 AM
Can anyone give me any pointers on setting up Radiator so that it will
return different vendor specific information per NAS?
Or maybe on stripping atributes that aren't required (or conflict) for a
NAS?
(We are trying to use both Tigris and TNT.)
Thanks,
Jeremy C. Reed
We have recently installed Radiator 2.15 on our RedHat Linux 6.2 box after
installing Perl 5 v5.005, Perl LDAP v.16, and Perl MD5 v2.09. Everything
compiled without a hitch. And, we modified the ldap.cfg file to reflect our
environment. We're using OpenLDAP 1.2.9.
The server worked perfectly
"Jeremy C. Reed" wrote:
>
> Can anyone give me any pointers on setting up Radiator so that it will
> return different vendor specific information per NAS?
>
> Or maybe on stripping atributes that aren't required (or conflict) for a
> NAS?
>
> (We are trying to use both Tigris and TNT.)
For one
Hello Christian -
On Thu, 11 May 2000, Christian Hammers wrote:
> Hello
>
> I've got a big problem. We want to use the following attributes in some
> of our user profiles we fetch via replaceIfNotExistProfiles hook and LDAP:
> cisco-avpair=ip:addr-pool=setup_pool
> cisco-avpair=ip:d
Hello Juan -
On Thu, 11 May 2000, ARG-MENENDEZ, JUAN wrote:
> 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 24
-- Forwarded Message --
Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from [Fabrizio Cuseo
<[EMAIL PROTECTED]>]
Date: Fri, 12 May 2000 03:10:21 +1000 (EST)
From: [EMAIL PROTECTED]
>From owner-radiator Fri May 12 03:10:14 2000
Received: by oscar.open.com.au (8.9.0
Hello Fabrizio -
On Fri, 12 May 2000, [EMAIL PROTECTED] wrote:
>
> I'm using a national roaming service with a proxy radius that forwards me
> all @domain.it requests.
> Sometimes their access-servers or radius, don't send me the STOP accounting
> record, so i often have dead sessions on my r
Hello Jeremy -
On Fri, 12 May 2000, Jeremy C. Reed wrote:
> Can anyone give me any pointers on setting up Radiator so that it will
> return different vendor specific information per NAS?
>
> Or maybe on stripping atributes that aren't required (or conflict) for a
> NAS?
>
Well, I already sent
Hello Fred -
On Fri, 12 May 2000, Fred Donovan wrote:
> We have recently installed Radiator 2.15 on our RedHat Linux 6.2 box after
> installing Perl 5 v5.005, Perl LDAP v.16, and Perl MD5 v2.09. Everything
> compiled without a hitch. And, we modified the ldap.cfg file to reflect our
> environm
We recently merged with a couple smaller ISP's. Currently one is running
off RadiusNT, another off of a livingston radius. I would like to have all
our dialup pops pointing to just one radius eventually. The first logical
step seems to be using Radius as a proxy for all the other radius serve
Hello Randy -
On Fri, 12 May 2000, Randy Cosby wrote:
> We recently merged with a couple smaller ISP's. Currently one is running
> off RadiusNT, another off of a livingston radius. I would like to have all
> our dialup pops pointing to just one radius eventually. The first logical
> step see
15 matches
Mail list logo
