|
> > UDP 195.74.212.37:16450 rr
> > -> 195.74.212.26:16450 Route 1 0 0
> > -> 195.74.212.34:16450 Route 1 0 0
> > UDP 195.74.212.31:1646 wlc
> > -> 195.74.212.26:1646 Route 1 0 106
> > -> 195.74.212.10:1646 Route 1 0 106
> > UDP 195.74.212.31:1645 wlc
> > -> 195.74.212.26:1645 Route 1 0 1
> > -> 195.74.212.10:1645 Route 1 0 0
> >
> how is the output above an example of it not working?
for the rule 1646 you can see it works. However for
rule 16450 & 1645, all UDP go to only one the real server.
(rule 16450 is not used at the moment. 1645 is. You can
see the strange little "1" for 195.74.212.26)
> Someone had a similar sounding problem with ntp (which is udp based).
> All packets would go to one host and then after a little while to
> another. In the short term the load balancing was bad, but
> over the long term (>15mins) the loadbalancing was fine.
> The udp LVS code sends all udp packets to one realserver, till a timeout
> is reached, and then sends the next packets to another realserver.
> It sounds like all udp packets are going to one realserver forever, right?
yes indeed. No switching.
> > UDP packets come from a single
> > server (our central proxy radius).
>
> Do you mean that the udp packets are coming from a single machine, which
> is a client for the LVS, but is a server for your users?
I have a serie of NAS (Network Access Server) sending
Authentication Request to a Proxy Radius server. This
Proxy Radius Server then forward Authentication Request
to the load-balancer which should normally dispatch them
to several nodes for processing (check with DB etc..)
Thanks for your help.
Regards,
Francois
Francois Baligant * * EuroNet Internet NV/SA
Network Operation Center * * a subsidiary of France Telecom
* Lozenberg 22 - B-1932 Zaventem
FB1-6BONE * tel: +32 2 717 17 17
francois@xxxxxxxxxxx fax: +32 2 717 17 77
|
