- 1. Re: [lvs-users] Unexpected source IP selection in IPVS TUN (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Sun, 19 Apr 2020 10:44:43 +0300 (EEST)
- Hello, Sorry for the delay> I'm not aware of any work-around. May be with SNAT translation. If IPVS box can not do it, some next hop. Regards -- Julian Anastasov <ja@xxxxxx> _________________________
- /html/lvs-users/2020-04/msg00012.html (9,978 bytes)
- 2. Re: [lvs-users] Unexpected source IP selection in IPVS TUN (score: 1)
- Author: "Calvin Zachman" <calvin.zachman@xxxxxxx>
- Date: Tue, 7 Apr 2020 12:45:05 +0000
- Hi Julian, That is the exact issue we are seeing. Thank you for the guidance. I will look into whether we can update to the latest RHEL with newer kernel version. I know it's probably a long shot, bu
- /html/lvs-users/2020-04/msg00010.html (13,353 bytes)
- 3. Re: [lvs-users] Unexpected source IP selection in IPVS TUN (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Mon, 6 Apr 2020 16:43:29 +0300 (EEST)
- Hello, Looking at archives I found thread that can help you: https://marc.info/?t=153556562900003&r=1&w=2 Check if your kernel has this line removed from do_output_route4(): fl4.saddr = (rt_mode & IP
- /html/lvs-users/2020-04/msg00008.html (11,434 bytes)
- 4. [lvs-users] Unexpected source IP selection in IPVS TUN (score: 1)
- Author: "Calvin Zachman" <calvin.zachman@xxxxxxx>
- Date: Mon, 6 Apr 2020 13:07:31 +0000
- Hello, I am looking for some help with an intermittent issue with IPVS source IP selection in TUNNEL mode. We run LVS directly in a Kuberenetes cluster, potentially on the same machine as backend wor
- /html/lvs-users/2020-04/msg00007.html (14,412 bytes)
This search system is powered by
Namazu