[tproxy] connection go to CLOSE_WAIT after sending FIN

KOVACS Krisztian hidden at balabit.hu
Mon Dec 11 18:58:32 CET 2006


On Monday 11 December 2006 18:27, Jan Engelhardt wrote:
> >  This symptom is probably caused by the TCP window tracking patch
> >included in newer TProxy tarballs. (Ie. a new TCP connection tracking
> >engine with a revamped state machine.) So it has nothing to do
> > directly with tproxy, you'd have the same experience without
> > transparent proxying on recent 2.6 kernels.
> Window tracking? What does _that_ do? And when exactly is it active
> (when tproxy.ko is loaded, or always?)

  Always when ip_conntrack (or nf_conntrack plust the IPv4 conntrack 
module) is loaded.

> unidirectional (socket). "half-duplex" is word tainted by network
> electronics and can mean bidirectional communication over a
> (unidirectional-at-a-time) pipe.


  Krisztian Kovacs

More information about the tproxy mailing list