Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+IPv6\s+loadbalancer\s+and\s+source\s+addr\s+selection\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] IPv6 loadbalancer and source addr selection (score: 1)
Author: Ferenc Wagner <wferi@xxxxxxx>
Date: Thu, 09 Jan 2014 12:32:41 +0100
Besides the very insightful stuff I elided above, what about adding a local route for the VIP instead of adding the address? Of course that works only if the VIP traffic is routed to the address of y
/html/lvs-users/2014-01/msg00025.html (10,280 bytes)

2. Re: [lvs-users] IPv6 loadbalancer and source addr selection (score: 1)
Author: Anders Henke <anders.henke@xxxxxxxx>
Date: Thu, 9 Jan 2014 11:25:58 +0100
There are multiple ways to achieve this. You noted the adress label, but according to RFC 3484, there are other ways with even higher preferences to influence the source address selection. First of a
/html/lvs-users/2014-01/msg00024.html (11,860 bytes)

3. [lvs-users] IPv6 loadbalancer and source addr selection (score: 1)
Author: Michael Schwartzkopff <ms@xxxxxxx>
Date: Wed, 08 Jan 2014 21:50:34 +0100
Hi, I want to set up a IPv6 load balancer in direct routing mode. So I configure a IPv6 address an my loadbalancer and the same IPv6 addr on the lo interface of the real servers. No to the problem: S
/html/lvs-users/2014-01/msg00020.html (9,519 bytes)


This search system is powered by Namazu