Ah You're relying on the authorize section being run after the
proxy reply is received.
Don't do that.
That feature was removed before 2.0, and seems to have accidentally
been enabled again. It was removed in 2.0.5 because it's wrong. The
post-proxy section is meant to process proxy
Hi,
For some reason the module returns noop ;-( I tried the following:
I created new 'files' instance:
files post_proxy_files {
usersfile = ${confdir}/post-proxy-users
acctusersfile = ${confdir}/post-proxy-users
auth_usersfile =
Pshem Kowalczyk wrote:
For some reason the module returns noop ;-( I tried the following:
Which is not what I suggested. Why?
I guess the easiest way to fix this is to use unlang to update the
reply packet based on information from either control or request
attributes.
That's what
Hi,
I upgraded our test server from 2.0.4 to 2.0.5 today and proxy setup
we use stopped working.
Currently (2.0.4) we have following entries in the users.conf:
DEFAULT User-Name =~ '@bitstream.dsl.$', Proxy-To-Realm := quik-dsl
Cisco-AVpair += ip:dns-servers=x.y.129.67 x.y.129.68,
Pshem Kowalczyk wrote:
I upgraded our test server from 2.0.4 to 2.0.5 today and proxy setup
we use stopped working.
What does debugging mode say in 2.0.4, and in 2.0.5?
Should that continue to work?
Well, yes.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
5 matches
Mail list logo
