Hello! Yes, we have these patches installed: 00-tcp_window_tracking.diff 01-nat_reservations.diff 02-nat_reservations_tproxy_exports.diff 03-tproxy.diff plus Julian's ipvs_nfct patch (the one you mention in the link) to provide the interface between IPVS and conntrack. I also should have said that we are only using LVS-NAT in the IPVS setup. Thanks for your note and the link. We'll keep digging ;-) Tim --- KOVACS Krisztian <hidden@balabit.hu> wrote:
Hi,
2004-10-14, cs keltez�ssel 12:04-kor Tim Burress ezt �rta:
The only evidence suggesting that TPROXY is involved at this point is the observation that the problem doesn't appear when we use TPROXY 1.2. One other data point is that, when we use TPROXY 2.0, the problem appears even when the module is not loaded, so it seems to be a side effect of patches to other modules.
I realize this is vague, and we're trying to track it down, but I thought I would post and just see if anyone else has observed similar behavior, or if there are any ideas for locating the source of the problem.
Do you use the TCP window tracking patch from the TProxy tarball? Although I don't use LVS myself, I've found this:
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.filter_rules.html
-- Regards, Krisztian KOVACS
_______________________________________________ tproxy mailing list tproxy@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/tproxy
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com