From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Some weird issue with return traffic with redirect rule
Date: Fri, 17 Oct 2008 12:19:26 -0500 [thread overview]
Message-ID: <48F8C91E.5010608@riverviewtech.net> (raw)
In-Reply-To: <cc64e8ce0810162330i44d61166xc16eafc0cfbf3834@mail.gmail.com>
On 10/17/08 01:30, Pranav Desai wrote:
> We are seeing cases where the return traffic is going out using the
> proxyIP and port 8001, instead of using the origin servers IP and
> port 80. I have added the traces for both cases below. Most of the
> traffic goes out correctly using the origin server IP and port, but
> the traffic using port 8001 is not insignificant, hence we are a bit
> concerned about it.
*nod*
> There are no connections coming in to port 8001.
Ok...
I have to ask, is there a reason you are not configuring clients to talk
directly to the proxy? In my experience this works a lot better than
transparent proxying. I tend to use direct proxying as the primary
method and then transparent proxying as a backup and to catch devices
that don't know how to talk to a proxy.
> I am not sure what could be causing this behavior or how I should go
> about debugging this. Could the conntrack table or its usage be
> screwed up?
Are there any DMESG or syslog entries about the connection table being full?
Grant. . . .
next prev parent reply other threads:[~2008-10-17 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 6:30 Some weird issue with return traffic with redirect rule Pranav Desai
2008-10-17 17:19 ` Grant Taylor [this message]
2008-10-17 19:46 ` Pranav Desai
2008-10-20 21:24 ` Grant Taylor
2008-10-21 2:02 ` Pranav Desai
2008-10-21 22:53 ` Pranav Desai
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=48F8C91E.5010608@riverviewtech.net \
--to=gtaylor@riverviewtech.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.