All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Kehn <rdkehn@yahoo.com>
To: Jan Engelhardt <jengelh@medozas.de>, Patrick McHardy <kaber@trash.net>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrack and PREROUTING
Date: Fri, 20 Jun 2008 06:16:48 -0700 (PDT)	[thread overview]
Message-ID: <787076.65754.qm@web52011.mail.re2.yahoo.com> (raw)
In-Reply-To: <485B8494.7050608@trash.net>

Hi Patrick,


--- On Fri, 6/20/08, Patrick McHardy wrote:

> Jan Engelhardt wrote:
> > On Friday 2008-06-20 01:57, Doug Kehn wrote:
> > 
> >> iptables -t raw -A PREROUTING -d !
> 192.168.2.0/255.255.255.0 -i br0
> >> -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK ACK -m
> tcp --dport 80 -m
> >> conntrack --ctstate ESTABLISHED -j NOTRACK
> >>
> >> Does this even make sense?
> > 
> > Yes, but:
> 
> No. The raw table doesn't have conntrack information.

I assume the same holds for -m state as well?  If so, this would explain why the rules are never matched.

Is there a way to have ACKs bypass the proxy and not break connection tracking?

My theory is that when performing a streaming HTTP download (e.g. streaming video over HTTP) having the ACKs traverse the proxy introduces sufficient delay to degrade video playback.  I'm hoping to find a general solution.  Creating a NOTRACK rule for each site is possible but a little cumbersome.

Thanks,
...doug



      

  parent reply	other threads:[~2008-06-20 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 23:57 conntrack and PREROUTING Doug Kehn
2008-06-20  7:45 ` Jan Engelhardt
2008-06-20 10:21   ` Patrick McHardy
2008-06-20 10:55     ` Jan Engelhardt
2008-06-20 13:16     ` Doug Kehn [this message]
2008-06-20 13:26       ` Patrick McHardy
2008-06-20 13:58         ` Doug Kehn
2008-06-20 12:49   ` Doug Kehn
2008-06-20 13:03     ` Gáspár Lajos
2008-06-20 13:34       ` Doug Kehn
2008-06-20 14:18     ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=787076.65754.qm@web52011.mail.re2.yahoo.com \
    --to=rdkehn@yahoo.com \
    --cc=jengelh@medozas.de \
    --cc=kaber@trash.net \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.