Alan DeKok wrote:
if (proxy:NAS-IP-Address == 172.29.51.24) {
update proxy {
NAS-IP-Address := 172.26.64.100
}
}
It works, but instead of update proxy should be update proxy-request,
and instead of proxy:NAS-IP-Address
I have some rewrites like this (in pre-proxy):
attr_rewrite fixcboss6 {
attribute = NAS-IP-Address
searchin = proxy
searchfor = 172.29.51.24
replacewith = 172.26.64.100
new_attribute = no
Evgeniy Kozhuhovskiy wrote:
...
fixcboss6: Does not match: NAS-IP-Address = ╛?3?
It's trying to do a regex match against the packed (32-bit) IP
address, not against the ASCII string describing the IP address. That
can easily be fixed.
But in any case, you *don't* need to use attr_rewrite
Alan DeKok wrote:
It's trying to do a regex match against the packed (32-bit) IP
address, not against the ASCII string describing the IP address. That
can easily be fixed.
But in any case, you *don't* need to use attr_rewrite for this. Just
put the following into the pre-proxy section,
I am trying to download the branch_1_1 from CVS but i am getting error as:
Unknown host
Ping to 64.24.0.50 (cvs.freeradius.org) not reachable.
Is the cvs.freeradius.org server is down?
Thanks,
Sumithra
On 4/7/07, Alan DeKok [EMAIL PROTECTED] wrote:
nikitha wrote:
Thanks for your
nikitha wrote:
I am trying to download the branch_1_1 from CVS but i am getting error
as: Unknown host
Ping to 64.24.0.50 http://64.24.0.50 (cvs.freeradius.org
http://cvs.freeradius.org) not reachable.
Is the cvs.freeradius.org http://cvs.freeradius.org server is down?
I can see it as
I could ping to freeradius.org but not to cvs.freeradius.org.
Anyhow i will try it once again after some time.
Thanks.
On 4/9/07, Alan DeKok [EMAIL PROTECTED] wrote:
nikitha wrote:
I am trying to download the branch_1_1 from CVS but i am getting error
as: Unknown host
Ping to 64.24.0.50
nikitha wrote:
Thanks for your information.
As we need a fix immediately, can i upgrade to 1.1.5? Does it have fixes
for these kind of issues?
If you need something now, try 1.1.4, or branch_1_1 in CVS.
What is the exact date that you are planning to release 1.1.6?
No idea. Next week
What about 1.1.5? Can i use this version until we get 1.1.6?
Because i already started of porting 1.1.5, so please advise me whether i
can go with 1.1.5 itself. Or should i follow as you mentioned in the below
mail.
Thanks a lot,
-- Nikitha
On 4/7/07, Alan DeKok [EMAIL PROTECTED] wrote:
nikitha wrote:
What about 1.1.5? Can i use this version until we get 1.1.6?
What part of my message was unclear?
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http://deployingradius.com/blog/ - The blog
-
List info/subscribe/unsubscribe? See
=
0x02020070198000661603010061015d0301461654c362b26af0ff6d48f398a5156d6566ebbced03258c344461681761d8ed3600390038003500160013000a00330032002f0007006600050004006300620061001500120009006500640060001400110008000600030100
Message-Authenticator = 0x572da3efc1f70fab4cbd23469ec0722a
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 1163
modcall[authorize]: module preprocess returns ok for request 1163
radius_xlat: 'anonymous'
rlm_attr_rewrite: Added
Hi Alan,
Thanks for your information.
As we need a fix immediately, can i upgrade to 1.1.5? Does it have fixes for
these kind of issues?
What is the exact date that you are planning to release 1.1.6?
Thanks a lot,
-- Nikitha
On 4/6/07, Alan DeKok [EMAIL PROTECTED] wrote:
nikitha wrote:
Hi
Hi Freeradius friends!
I am programming a proxyRadius (FreeRadius v1.88.2.3 in Debian) in order to
write a Session-Tiemout attribute with a value =3600 if the attribute
doesn't exist yet.
I have defined an instance of attr_rewirte called setSessionTimeout3600
with append=no,
Hi Freeradius friends!
I am programming a proxyRadius (FreeRadius v1.88.2.3 in Debian) in order to
write a Session-Tiemout attribute with a value =3600 if the attribute
doesn't exist yet.
I have defined an instance of attr_rewirte called setSessionTimeout3600
with append=no, new_attribute=no,
Is it possible to delete entire attributes with rlm_attr_rewrite?
Tomasz
--
Tomasz Wolniewicz
[EMAIL PROTECTED]http://www.uni.torun.pl/~twoln
Uczelniane Centrum Informatyczne InformationCommunication Technology Centre
Uniwersytet Mikolaja Kopernika Nicolaus Copernicus
-Password
Processing the post-auth section of radiusd.conf
modcall: entering group post-auth for request 3
radius_xlat: '(.*)'
radius_xlat: '49172560'
rlm_attr_rewrite: Changed value for attribute NAS-Port from '' to
'49172560'
rlm_attr_rewrite: Could not find value pair for attribute NAS-Port
Michael Kopp [EMAIL PROTECTED] wrote:
Here is what we have configured in radiusd.conf
attr_rewrite unique-nas-port {
attribute = NAS-Port
...
replacewith = %{Calling-Station-Id}
That won't work. NAS-Port is an integer, and Calling-Station-Id is
a string. You can't assign
17 matches
Mail list logo