[prev in list] [next in list] [prev in thread] [next in thread]
List: freeradius-users
Subject: Re: can attr_filter.accounting_response be used in post-proxy section
From: 魏景鹏 <weijingpeng () m800400 ! com>
Date: 2011-04-26 10:58:02
Message-ID: 4DB6A53A.4020208 () m800400 ! com
[Download RAW message or body]
[Attachment #2 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Dear </tt>Brian Candler,<br>
<br>
thank you for focus.<br>
<br>
I think freeradius may lack the opportunity to change & filter
acctcounting-response(reply) in post-proxy.<br>
<br>
I have done this througth filter proxy-reply.<br>
<br>
Best regards<br>
WeiJingpeng<br>
<br>
Brian Candler wrote:
<blockquote cite="mid20110426103230.GA7835@uk.tiscali.com" type="cite">
<pre wrap="">On Mon, Apr 18, 2011 at 09:13:47PM +0800, 魏景鹏 wrote:
</pre>
<blockquote type="cite">
<pre wrap="">In post-proxy section, I wrote lines as follows:
post-proxy {
if(cond) {
attr_filter.accounting_response
}
}
But it seems not work as expected.
Any Ideas?
</pre>
</blockquote>
<pre wrap=""><!---->
How does it not work as expected? What does radiusd -X show when proxying?
attr_filter acts on different lists depending on where it's invoked.
preacct: request
accounting: reply
preproxy: proxy request
postproxy: proxy reply
postauth: reply
authorize: request
Unfortunately this is hard-coded. There have been times where I've wanted to
filter out reply attributes in the 'authorize' section, for example, and
I've been forced to move this to postauth.
</pre>
</blockquote>
</body>
</html>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic