Hi,
I'm wondering why it is prohibited to have a particular NAS-IP-Address
in more than one huntgroup.
I want to use huntgroups for roaming blocking:
huntgroups:
DE.HDN NAS-IP-Address == 10.0.0.1
DE NAS-IP-Address == 10.0.0.1
EMEANAS-IP-Address == 10.0.0.1
Hi,
the parser for Ascend-Data-Filter attributes in FreeRadius is very
rigorous, following the definition in the Ascend Radius guide.
However, the Ascend documentation seems to be a bit messy, since first
there is the definition:
Ascend-Data-Filter=ip dir action [dstip dest_ipaddr/subnet_mask]
Yep, done.
Wolfgang
At Tue, 26 Apr 2005 09:53:49 -0400,
Alan DeKok wrote:
Wolfgang Hottgenroth [EMAIL PROTECTED] wrote:
What do you think? (Just in case of: I would volunteer to deliver a
patch.)
Sure, submit a patch to bugs.freeradius.org
Alan DeKok.
-
List info/subscribe
Hi,
I see in lib/print.c:
static const char *vp_tokens[] = {
?, /* T_INVALID */
EOL,/* T_EOL */
{,
},
(,
),
,,
;,
+=,
-=,
:=,
=,
!=,
=,
,
=,
,
=~,
!~,
=*,
~*,
==,
#,
BARE-WORD,
\STRING\,
I'm sorry for not being very exact. This is about 1.0.2. I've checked
CVS, it is there too.
Wolfgang
At Wed, 20 Apr 2005 22:36:32 +0200,
Wolfgang Hottgenroth wrote:
Hi,
I see in lib/print.c:
static const char *vp_tokens[] = {
?,/* T_INVALID
Hi to you all!
I've a question concerning the attribute User-Category (1029). It is
not strictly FreeRADIUS related, but I read many times it origin was
the Cistron Radius, and as FreeRADIUS is the descendant of Cistron
somebody here might know an answer ...
Andrei used the attribute
Hi,
I've a question concerning the rlm_ldap module.
The order of radius attributes, especially of multiple values for one
attribute, in the access-accept reply sent to the NAS is sometimes
crucially. For instance for the ascend-data-filter attribute.
Is there a way to guarantee this order when
7 matches
Mail list logo
