Hello everyone -
Thanks to Andy Loukes for drawing our attention to a bug in the recent Radiator
2.16.2 release regarding AuthAttrDef in AuthBy LDAP* clauses.
There are new versions of these modules in the 2.16.2 patches area.
Our apologies for any inconvenience.
regards
Hugh
On Tue, 22 Aug
Hello Ricardo -
On Tue, 22 Aug 2000, Ricardo Guerra1 wrote:
> Hi!!
> i try to make a vpn with radiator, a cisco 7100 and a ericsson's tigris
> but when the tigris tries to authenticate a user with radiator it
> answers the default reply for vpn
>
> Attributes:
> Tunnel-Type = L2TP
>
Hello William -
Without seeing the log file its difficult to say what caused the original
problem, however I notice that you query the NAS(s) to check simultaneous use.
This can cause timeout problems if the NAS does not reply to the query.
We have also occasionally seen "No such user" problems
Hello Ingvar -
You would have to propogate the host addresses dynamically in your internal
routing protocol.
regards
Hugh
On Tue, 22 Aug 2000, Ingvar Berg (ERA) wrote:
> How would you handle routing with a common IP pool across several NASs?
> /Ingvar
>
> > -Original Message-
> > Fro
Hello Vangelis -
The AuthBy TACACSPLUS module only handles authentication requests. You will
have to deal with authorisation and accounting seperately.
regards
Hugh
On Tue, 22 Aug 2000, Vangelis Kyriakakis wrote:
> Hugh Irvine wrote:
>
> > Hello Vangelis -
> >
> > On Mon, 21 Aug 2000, Vangel
Hi!!
i try to make a vpn with radiator, a cisco 7100 and a ericsson's tigris
but when the tigris tries to authenticate a user with radiator it
answers the default reply for vpn
Attributes:
Tunnel-Type = L2TP
Tunnel-Medium-Type = IP
Tunnel-Server-Endpoint = "216.230.128.185
Hello, Hugh
Ipass just confirmed that there's a bug on vnas version 3.5.5 with the
include_domain tag. If you intend to use this, you should upgrade to
version 3.6
I'll do the upgrade tonight and will keep you informed of the results.
Thanks for your help!
Rafael
--
R
Hello everyone,
Last evening at about 9:00pm (which is prime time with many users
logging in) our primary radius server apparently started timing
out and requests were being passed along to our secondary radius
server (both are running Radiator 2.15).
In the radius.log of out backup radius serve
On Tue, 22 Aug, Andy Loukes wrote:
> I updgraded to 2.16.2 as I was having problems with AuthAttrDef. I
> couldn't get it to sent the reply to the NAS.
>
> Now if I do a request to the server configured to AuthLDAP it crashes:
>
> Tue Aug 22 09:23:27 2000: DEBUG: Handling with Radius::AuthLDAP
Hugh Irvine wrote:
> Hello Vangelis -
>
> On Mon, 21 Aug 2000, Vangelis Kyriakakis wrote:
> > Hello,
> >
> > 1) Is Radiator capable of sending authentication requests to TACACS+
> > servers? We need to implement a scheme in which a call will be
> > authenticated based on the domain name either
I updgraded to 2.16.2 as I was having problems with AuthAttrDef. I couldn't
get it to sent the reply to the NAS.
Now if I do a request to the server configured to AuthLDAP it crashes:
Tue Aug 22 09:23:27 2000: DEBUG: Handling with Radius::AuthLDAP
Tue Aug 22 09:23:27 2000: DEBUG: Connecting to l
How would you handle routing with a common IP pool across several NASs?
/Ingvar
> -Original Message-
> From: FlintHillsTechnical Support [mailto:[EMAIL PROTECTED]]
> Sent: den 19 augusti 2000 02:48
> To: [EMAIL PROTECTED]
> Subject: (RADIATOR) assigning ip addresses from a common pool
>
12 matches
Mail list logo