Hello Nir -
If I understand you correctly you are trying to test simultaneous use
with the radpwtst program? You need to be a bit careful doing this
because of the way Radiator maintains the session database. When
Radiator receives an access request it first of all deletes any
existing
Hello Mariano -
Thanks for the kind words - we appreciate it.
And I'm glad that we are keeping you happy - if you have any more
good ideas for Radiator please let us know!
regards
Hugh
El 28 Oct 2001 a las 13:08, Mike McCauley escribió:
We are pleased to announce the release of
Hello Onno -
How nice to hear from you - hope everything is going well?
I have copied this to Mike to ask him to have a look at if for you.
regards
Hugh
Hi All,
I am trying to send tagged tunneling attributes with radiator and having
some problems. I have read the FAQ/manual as per
40.
Title: Re: (RADIATOR) default gateway
Hello Anton -
I suppose you could use the Framed-Route attribute,
however I think this is much more likely to be entirely dependent on
the NAS and PPP client.
You will have to check with your NAS vendor to see what options
are available.
regards
Hugh
Hello Arwin -
Hello,
How can I add a session-timeout attribute on a per client basis?
When I use AddToReply SessionTimeout=1800 in a handler, it works fine for
this handler.
But I want to do this on a per client basis. I think I'll have to use some
sort of hook,
but the client clause only
Greetings;
A few weeks ago we mentioned that on a fresh install of radiator 2.18, which
was being done on a freshly installed FreeBSD 4.4-RELEASE machine, we got an
error message about hostname.pl.
We just did a fresh install of radiator 2.19 on a fresly installed
FreeBSD4.4 machine and got the
I have just turned up a 7206VXR with ADSL using PPPOA. I am
authenticating to my Radiator server and everything works fine on the first
DSL connection. But when I connect the second modem and look at radwho.cgi
the connected user changes to the second modem that is connected and doesn't
add
Hello Onno,
On Wed, 31 Oct 2001 02:35, Hugh Irvine wrote:
Hello Onno -
How nice to hear from you - hope everything is going well?
I have copied this to Mike to ask him to have a look at if for you.
regards
Hugh
Hi All,
I am trying to send tagged tunneling attributes with radiator
I have just upgrade to 2.19
I am now getting this error
ERR: Attribute number 79 is not defined in your dictionary
What is attribute 79 ?
I am using
Radius::AuthEMERALD into platpus
I did get this error before the upgrade
Thanks
Matthew Hobbs
===
Archive at
Hello Arwin -
Hello,
How can I add a session-timeout attribute on a per client basis?
When I use AddToReply SessionTimeout=1800 in a handler, it works fine for
this handler.
But I want to do this on a per client basis. I think I'll have to use some
sort of hook,
but the client clause only
Hello Wayne -
The problem here is due to the fact that the NAS-Port value in all
the access requests is always 0, therefore Radiator gets confused
because the NAS-IP-Address/NAS-Port combination is what is used for
the maintenance of the session database.
You will have to check with your
Hello Matthew -
The following is defined in the standard dictionary contained in the
Radiator 2.19 distribution.
ATTRIBUTE EAP-Message 79 binary
What dictionary are you using?
BTW - you should always start with the standard Radiator dictionary
and add or remove
Salut Julien -
You will have to check with the Ariel vendor to find out why this is.
It may also be an issue with your telephone service that does not
supply that information in the call setup data.
regards
Hugh
Radiator is not receiving the Called-Station-Id in the
Access-Request
I use
Hello Gustavo -
Have you installed and configured the DBI/DBD modules for Perl?
regards
Hugh
Hi guys,
I'm trying to set up a radiator server with a MySQL server only to
assign three address pools. The trouble is that radiator can't connect to
the sql server, and I don't understand
Hi Hugh/Wayne,
Gareth Coco
AAPT Data Operations
AAPT - http://www.aapt.com.au/
Hugh Irvine [EMAIL PROTECTED] 10/31/01 01:17pm
You will have to check with your vendor to get the problem fixed.
On the Cisco 6400 NRP blade (a 7200 on a stick) our config has the following in it:
15 matches
Mail list logo