Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+\"selective\s+balancing\"\s+\-\s+make\s+requests\s+from\s+1\.2\.3\.4\s+go\s+to\s+realserver_A\,\s+all\s+others\s+\-\s+to\s+realserver_B\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Alex Attarian <u2sashko@xxxxxxxxx>
Date: Fri, 7 Mar 2014 09:31:32 -0800
Sorry I missed the part where your director is also a real server... My other thought was also fw marks only exist in the kernel of the machine and never leave the machine, that's why it confused me
/html/lvs-users/2014-03/msg00027.html (12,336 bytes)

2. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Tomasz Chmielewski <tch@xxxxxxxxxxx>
Date: Fri, 7 Mar 2014 18:26:45 +0100
"iptables -t mangle -I PREROUTING -s 1.2.3.4 -j ACCEPT" doesn't set any mark, and that's exactly why it works: any rules setting the mark later on are simply ignored, and requests from 1.2.3.4 hit th
/html/lvs-users/2014-03/msg00026.html (12,199 bytes)

3. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Alex Attarian <u2sashko@xxxxxxxxx>
Date: Fri, 7 Mar 2014 09:18:48 -0800
I'm confused how this "iptables -t mangle -I PREROUTING -s 1.2.3.4 -j ACCEPT" sets a mark? Doesn't Tomasz need to set a mark (*-j MARK --set-mark 1)* and then tell ipvsadm to route based on fwmark? i
/html/lvs-users/2014-03/msg00025.html (12,303 bytes)

4. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Ferenc Wagner <wferi@xxxxxxx>
Date: Fri, 07 Mar 2014 12:53:27 +0100
Just a note: you don't *have to* use the mangle table (though oldish kernels restrict the MARK target to the mangle table), if you don't want to base your routing decision on fwmarks. For LVS virtual
/html/lvs-users/2014-03/msg00024.html (10,378 bytes)

5. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Tomasz Chmielewski <tch@xxxxxxxxxxx>
Date: Fri, 7 Mar 2014 12:47:21 +0100
Indeed. iptables -t mangle -I PREROUTING -s 1.2.3.4 -j ACCEPT on the realserver does the trick :) -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Please read the
/html/lvs-users/2014-03/msg00023.html (11,372 bytes)

6. Re: [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Patrick Schaaf <netdev@xxxxxx>
Date: Fri, 7 Mar 2014 12:15:08 +0100
Hi Tomasz, 2014-03-07 11:52 GMT+01:00 Tomasz Chmielewski <tch@xxxxxxxxxxx>: The key to such usage, is fwmark based LVS virtual hosts. You then use the iptables -t mangle PREROUTING to set firewall ma
/html/lvs-users/2014-03/msg00022.html (10,845 bytes)

7. [lvs-users] "selective balancing" - make requests from 1.2.3.4 go to realserver_A, all others - to realserver_B (score: 1)
Author: Tomasz Chmielewski <tch@xxxxxxxxxxx>
Date: Fri, 7 Mar 2014 11:52:22 +0100
I was wondering if I can use ipvsadm not only for load balancing, but also for "code testing". Normal scenario (i.e. what I use right now): - both servers acting as directors and realservers, - IP fa
/html/lvs-users/2014-03/msg00021.html (10,379 bytes)


This search system is powered by Namazu