Hi all,
This is more a question about client Radius implementations rather than
Radiator.
In our networks we use the Radius protocol (and Radiator of course!) also to
download config commands into our NAS equipment (Ascend/Lucent and Cisco).
This works very well in our environment. We now try to
Hi guys,
It seems that I don't know how to use PreAuthHook properly. I would like
to do something like: if a username matches a certain patter (in my case,
the last two chars are 'es'), then rename the username to a known one
'abracadabra', and do the authentification (fetch 'abracadabra
It's been my experience that for some reason Radiator stores the user name a
couple of different ways. If you want to authoritatively change the user
name attribute you need to do this in your hook-
$p->{OriginalUserName}='abracadabra';
$p->changeUserName('abracadabra');
For your
Thank you, Frank,
It does work now...
bogdan
iCom Media AG
Kirchweg 36
Koln, 50858
Germany
Phone: +49-(0)221-485-689-16
Fax : +49-(0)221-485-689-20
Mobile:+49-(0)173-906-46-01
On Fri, 25 Oct 2002, Frank Danielson wrote:
> It's been my experience that
Is there a way to make Radiator not re-send packets? I use AuthBy SQL
and I have attempted to set retries to 0 and 1. When I set it to 0 it
seems to retry 3 times, when I set it to 1 it retries twice. I am hoping
someone can help me with this as I am in the middle of a network
migration of my radiu
Hello,
Have you tried a -1 value for Retries?
Regards,
Neil D. Quiogue
On Saturday, October 26, 2002, at 03:24 AM, James M. Luedke wrote:
Is there a way to make Radiator not re-send packets? I use AuthBy SQL
and I have attempted to set retries to 0 and 1. When I set it to 0 it
seems to retry
Hello Doug -
This is actually a NAS problem, due to a recent upgrade to the CVX
software.
The Acct-Session-Id is defined as a string (check the RFC), and the CVX
is now sending binary data instead.
You should check with your vendor to find out what they are sending and
how to interpret it.
