Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+LVS\s+and\s+Squid\s+client\s+with\s+persistent\s+connection\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [lvs-users] LVS and Squid client with persistent connection (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sat, 5 Jan 2019 19:07:37 +0200 (EET)
Hello, LBLC[R] work by directing client traffic based on the destination address. i.e. the remote web server IP. So, we try to forward every client that browses some site to same proxy server with th
/html/lvs-users/2019-01/msg00008.html (12,375 bytes)

2. Re: [lvs-users] LVS and Squid client with persistent connection (score: 1)
Author: Peter Viskup <skupko.sk@xxxxxxxxx>
Date: Wed, 12 Dec 2018 08:57:38 +0100
Hello Thomas, The lblcr algorithm should not balance on source-ip, but on "dh with wlc", but the algorithm is not clear to me. Would not expect the described situation to happen. Would like to stay w
/html/lvs-users/2018-12/msg00003.html (10,040 bytes)

3. Re: [lvs-users] LVS and Squid client with persistent connection (score: 1)
Author: Thomas Bätzler <t.baetzler@xxxxxxxxxx>
Date: Wed, 5 Dec 2018 14:22:23 +0000
Hello Peter, the Yeah, while there's an established connection over ipvs all subsequent new connections from the same source ip are routed to the same backend server. Weight just specifies how traffi
/html/lvs-users/2018-12/msg00001.html (9,904 bytes)

4. [lvs-users] LVS and Squid client with persistent connection (score: 1)
Author: Peter Viskup <skupko.sk@xxxxxxxxx>
Date: Wed, 5 Dec 2018 14:46:30 +0100
Having client of Squid server with opened persistent connection causing the LVS balancing forwarding new connections to the other node only. LVS configuration and status: ~ $ ipvsadm -Ln IP Virtual S
/html/lvs-users/2018-12/msg00000.html (9,817 bytes)

Current List: 1 - 4
Page: [1]
This search system is powered by Namazu