Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+lvs\s+masq\s+response\s+package\s+not\s+getting\s+picked\s+up\s*$/: 8 ]

Total 8 documents matching your query.

1. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 15:31:19 +0200
Klavs Klavsen said the following on 08/13/2012 03:05 PM: I believe I just confused how iptables vs. ipchains worked - sorry for being daft :) -- Regards, Klavs Klavsen, GSEC - kl@xxxxxxx - http://www
/html/lvs-users/2012-08/msg00008.html (10,076 bytes)

2. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 15:05:35 +0200
Graeme Fowler said the following on 08/13/2012 02:11 PM: [CUT] Ok. thank you for clarifying. So the external Ip would be in the OUTPUT chain, and I could filter more specificly there (unless I get st
/html/lvs-users/2012-08/msg00007.html (11,515 bytes)

3. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Graeme Fowler <graeme@xxxxxxxxxxx>
Date: Mon, 13 Aug 2012 13:11:14 +0100
You're using LVS-NAT. The only place the VIP is present in the usual usage of this is in the external (client-facing) interface of the director. ipvs works in tandem with netfilter (is part of it now
/html/lvs-users/2012-08/msg00006.html (10,052 bytes)

4. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 13:54:21 +0200
Appearently they are going through FORWARD - with the source IP of the backend - instead of the sourceIP of the VIP - that the client actually accessed. Also - for some reason there's no state - so I
/html/lvs-users/2012-08/msg00005.html (11,070 bytes)

5. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Graeme Fowler <graeme@xxxxxxxxxxx>
Date: Mon, 13 Aug 2012 12:46:37 +0100
I'm not 100% sure, but it looks like this is your problem. Remove those rules and see what happens. * I say "not sure" because I'm not sure whether the incoming packets will traverse the FORWARD chai
/html/lvs-users/2012-08/msg00004.html (10,288 bytes)

6. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 13:44:16 +0200
I enabled logging in iptables for both INPUT and FORWARD, and got this in logs: IN=eth2 OUT=eth2 SRC=Y.Y.Y.105 DST=MyInternetClientIP LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=TCP SPT=80 DPT=516
/html/lvs-users/2012-08/msg00003.html (13,301 bytes)

7. Re: [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 13:26:32 +0200
Y.Y.Y.105 is not the IP of the LVS server internal interface ofcourse - it's the ip of the backendserver. Klavs Klavsen said the following on 08/13/2012 01:20 PM: -- Regards, Klavs Klavsen, GSEC - kl
/html/lvs-users/2012-08/msg00002.html (12,961 bytes)

8. [lvs-users] lvs masq response package not getting picked up (score: 1)
Author: Klavs Klavsen <kl@xxxxxxx>
Date: Mon, 13 Aug 2012 13:20:47 +0200
Hi, I've setup a server, with public IPs (currently only one though) on one interface, and an internal ip on another interface - where the backend webservers are hosted. My problem is that I see the
/html/lvs-users/2012-08/msg00001.html (11,930 bytes)


This search system is powered by Namazu