Is it possible to setup a LAC repeater to perform load-balancing and/or failover functions to multiple LNS serveres?
There is a "complete_lac" configuration example (mpd.conf) with more than one LNS server configured. The LAC will choose the appropriate LNS based on the "peer auth name" But it's not exactly what I want.
The functionality I need would be somethning similar:
1) In case of load-balancing:
I want the LAC to choose the appropriate LNS server based on some round-robin algorithm.
2) In case of fail-over:
If there is no response from the first LNS server, try next-one in a list.
Thanks for your advice.
Brady77
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no built-in load-balancing in repeater facilities in MPD. But radius-auth and ext-auth authentication backends may affect which link template will be used to forward connection. Look for mpd-action attribute. This should be enough to implement first point. Second point in that case would require some other source of information, as MPD doesn't call accounting when forwarding calls.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Is it possible to setup a LAC repeater to perform load-balancing and/or failover functions to multiple LNS serveres?
There is a "complete_lac" configuration example (mpd.conf) with more than one LNS server configured. The LAC will choose the appropriate LNS based on the "peer auth name" But it's not exactly what I want.
The functionality I need would be somethning similar:
1) In case of load-balancing:
I want the LAC to choose the appropriate LNS server based on some round-robin algorithm.
2) In case of fail-over:
If there is no response from the first LNS server, try next-one in a list.
Thanks for your advice.
Brady77
There is no built-in load-balancing in repeater facilities in MPD. But radius-auth and ext-auth authentication backends may affect which link template will be used to forward connection. Look for mpd-action attribute. This should be enough to implement first point. Second point in that case would require some other source of information, as MPD doesn't call accounting when forwarding calls.