replication to multiple servers with proxy
FreeRADIUS Version 3.0.10 I'm trying replicate accounting data to multiple servers, however it's only replicating to the radive instance - if I swap radive and calix in the update control block, nothing gets proxied (monitoring with tshark) even though their configurations are essentially identical, so two questions: 1. Why is it only proxying to one? 2. Why doesn't it like the calix instance? Thanks... site file excerpt: preacct { preprocess acct_unique suffix update control { Proxy-To-Realm := "radive" Proxy-To-Realm += "calix" } } proxy.conf: proxy server { default_fallback = no } home_server radive { type = acct ipaddr = 207.55.16.33 port = 1813 status_check = none check_interval = 30 check_timeout = 4 num_answers_to_alive = 3 max_outstanding = 65536 } home_server_pool radive_pool { type = fail-over home_server = radive } realm radive { acct_pool = radive_pool } home_server calix { type = acct ipaddr = 199.71.142.73 port = 1813 status_check = none check_interval = 30 check_timeout = 4 num_answers_to_alive = 3 max_outstanding = 65536 } home_server_pool calix_pool { type = fail-over home_server = calix } realm calix { acct_pool = calix_pool }
Hi,
I'm trying replicate accounting data to multiple servers, however it's only replicating to the radive instance - if I swap radive and calix in the update control block, nothing gets proxied (monitoring with tshark) even though their configurations are essentially identical, so two questions:
preacct { preprocess acct_unique suffix update control { Proxy-To-Realm := "radive" Proxy-To-Realm += "calix" } }
you cant do it simply like this (with current versions). there are several virtual servers shipped with the server that you could use... so 'copy-acct-to-home-server' is an ideal example "# The purpose of this virtual server is to enable duplication # of information across a load-balanced, or fail-over set of # servers. For example, if a group of clients lists two # home servers (primary, secondary), then RADIUS accounting # messages will go only to one server at a time. This file # configures a server (primary, secondary) to send copies of # the accounting information to each other." yes? alan
On 9/7/16 1:55 PM, A.L.M.Buxey@lboro.ac.uk wrote:
you cant do it simply like this (with current versions). there are several virtual servers shipped with the server that you could use... so 'copy-acct-to-home-server' is an ideal example
"# The purpose of this virtual server is to enable duplication # of information across a load-balanced, or fail-over set of # servers. For example, if a group of clients lists two # home servers (primary, secondary), then RADIUS accounting # messages will go only to one server at a time. This file # configures a server (primary, secondary) to send copies of # the accounting information to each other."
yes?
I'm using that example, however apparently it can only choose one (this is a replication situation, not a failover or load-balance situation). There are two workarounds: 1. Chain them: server1 -> server2 -> server3 2. Get the radrelay client from freeradius v1 and do it the old, simple way, with a detail file and radrelay instance for each copy. Since "server3" in my case is a vendor server and I would have had to get them to change their configuration (to allow packets from a new client), I picked #2 in this case.
Hi,
I'm using that example, however apparently it can only choose one (this is a replication situation, not a failover or load-balance situation). There are two workarounds:
ummm, no...the example just uses the detail file. so thats easy, in the server you define a second detail file eg "detail2" ensuring you call that in the appropriate place - so the server writes 2 detail files, detail and detail2, you then create another copy of the virtual server that read the second detail file. alan
On 9/8/16 11:09 AM, A.L.M.Buxey@lboro.ac.uk wrote:
ummm, no...the example just uses the detail file. so thats easy, in the server you define a second detail file eg "detail2" ensuring you call that in the appropriate place - so the server writes 2 detail files, detail and detail2, you then create another copy of the virtual server that read the second detail file.
That worked easier than I thought it would ;-) Thanks!
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan Batie -
Alan DeKok