Hello,
It's the same server with the very same config for both users in
radcheck and radreply, except that in proxy.conf, only the "proxy.com"
realm is set to be proxied to 192.168.1.2.
When the user "[EMAIL PROTECTED]" (no proxy) logs in, the VSA
ERX-Service-Bundle is sent to the B-RAS, while it
Guilherme Franco wrote:
> Hi,
>
> Sorry for bothering you guys.
>
> I would like to humbly ask if there's any ideas on this?
There's a lot there, and it's not clear what's going on.
Look at the differences between the two configurations.
Alan DeKok.
--
http://deployingradius.com
Hi,
Sorry for bothering you guys.
I would like to humbly ask if there's any ideas on this?
Thanks.
On 6/11/07, Guilherme Franco wrote:
> Hello Mr. Alan,
>
> Thank you for answering.
>
> Below, you will find a working local authentication, user
> [EMAIL PROTECTED] (without proxy), where the VSA
Hello Mr. Alan,
Thank you for answering.
Below, you will find a working local authentication, user
[EMAIL PROTECTED] (without proxy), where the VSA "ERX-Service-Bundle" is
found in radreply (although the debug doesn't says that) and sent back
to the B-RAS:
rad_recv: Access-Request packet from ho
Guilherme Franco wrote:
> With proxy configured, the user gets authenticated by bar.com but the
> VSA is not sent to bar.com (no traces of it in pre_proxy logs nor in
> radiusd -X debugs).
The debug logs will still tell you what modules are being executed,
and when. That will give information
Hello,
Running Freeradius 1.1.4 on RHEL with an Oracle backend.
I'm at a Carrier and every "@bar.com" request is configured to be
proxied but I have a problem where a VSA (in radreply table) is not
even sent to bar.com.
In my database:
select * from radcheck;
ID USERNAME ATTRIBUTE
6 matches
Mail list logo