On 08/25/2012 02:34 AM, Kevin Schmidt wrote:
> I've been using Radiator in support of a variety of services for years,
> but I just ran into a really strange bug. If someone has an idea of
> what's happening, or a particularly good debugging technique to find the
> root cause, I'm all ears.
T
On 08/26/2012 09:59 AM, eliran shlomo wrote:
> Hi, i tried it and it send the first packet to both of the AuthBy server
> and then it sends it to the authby1 only.
Can you reply with your current configuration. You need one AuthBy
clause for each server you want to forward the request to. Within
Identifier ProxyAccounting
Host *
NoForwardAuthentication
AcctPort 1813
FailureBackoffTime 180
Retries 1
RetryTimeout 3
Secret ***
Identifier ProxyAccounting71
Host ***
NoForwardAuthentic
The configuration looks fine. It should send the request to two
destinations: ProxyAccounting and ProxyAccounting71.
You could do the following: Change FailureBackoffTime to 0 to make sure
the request is always forwarded even if the next hop host is down. Also,
add IgnoreAccountingResponse to both
I use Radiator 4.10 and I need to place a second radiator and I use FreeBSD,
but I need a solution to the sessions (SessionDatabase SQL) is well
synchronized since I use mysql. A mysql replication via resolves or is there a
better solution?
I also thought about using FreeBSD with CARP.
Thanks
Changing the FailureBackoffTime to 0 and adding the
IgnoreAccountingResponse solved the problem
thanks for the help.
2012/8/26 Heikki Vatiainen
> The configuration looks fine. It should send the request to two
> destinations: ProxyAccounting and ProxyAccounting71.
>
> You could do the followin
