Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+CentOS\/RHEL\s+6\s+ipvs\s+issue\s+with\s+DR\s+\(different\s+interfaces\s+and\s+networks\)\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] CentOS/RHEL 6 ipvs issue with DR (different interfaces and networks) (score: 1)
Author: Alex Attarian <u2sashko@xxxxxxxxx>
Date: Fri, 18 Oct 2013 05:39:20 -0700
David, yes both values 0 and 2 work, however 0 does no source checking at all, 2 does a loose checking: 2 = basically if any interface can actually route any of the networks the packet is coming in f
/html/lvs-users/2013-10/msg00021.html (12,580 bytes)

2. Re: [lvs-users] CentOS/RHEL 6 ipvs issue with DR (different interfaces and networks) (score: 1)
Author: David Coulson <david@xxxxxxxxxxxxxxxx>
Date: Fri, 18 Oct 2013 07:07:24 -0400
We have a large LVS environment with RHEL6 for both balancers and real servers. On most real servers we have rp_filter set to 1. Our network config is pretty much the same as yours (VIPs on lo, usual
/html/lvs-users/2013-10/msg00020.html (10,322 bytes)

3. [lvs-users] CentOS/RHEL 6 ipvs issue with DR (different interfaces and networks) (score: 1)
Author: Alex Attarian <u2sashko@xxxxxxxxx>
Date: Thu, 17 Oct 2013 21:50:42 -0700
Hello everyone, I've been running ipvs on our systems for quite a long time, we recently upgraded some servers from CentOS 5 to CentOS 6 (which ships with kernel 2.6.32). Our setup is ipvs DR: loadba
/html/lvs-users/2013-10/msg00019.html (10,255 bytes)


This search system is powered by Namazu