From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: On vanilla Fedora 3, can't do a transparent proxy (-j REDIRECT)
Date: Mon, 2 May 2005 16:57:42 -0400 [thread overview]
Message-ID: <20050502205742.GA12530@bender.817west.com> (raw)
In-Reply-To: <df31c404050502120435134f8@mail.gmail.com>
On Mon, May 02, 2005 at 03:04:20PM -0400, John G. Norman wrote:
> tcp 0 0 :::8080 :::* LIST
k--so the cheap -n- easy stab was that nothing was listening on TCP port
8080.
here's how i would go about checking this...first--use the REDIRECT
method, as it's the "normal" way to do transparent proxying. next:
even though your firewall is wide-open, create a rule like:
iptables -A INPUT -i $INSIDE_IF -p tcp --dport 8080 -j ACCEPT
with the REDIRECT rule and the ACCEPT rule in place, generate some HTTP
traffic from a client behind the firewall.
using "iptables -t nat -vnxL" is the REDIRECT rule getting hits?
if not--HTTP traffic is never making it to this gateway.
using "iptables -vnxL" is the ACCEPT rule getting hits?
if not--there's something wrong with your REDIRECT rule (most likely the
inbound interface). if it is--packets should be making it to the squid
proxy--is squid setup for transparent proxying?
HTH...
-j
--
"Brian: Whose leg do I have to hump to get a dry martini around here?"
--Family Guy
next prev parent reply other threads:[~2005-05-02 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 18:42 On vanilla Fedora 3, can't do a transparent proxy (-j REDIRECT) John G. Norman
2005-05-02 18:51 ` Jason Opperisano
2005-05-02 19:04 ` John G. Norman
2005-05-02 20:57 ` Jason Opperisano [this message]
2005-05-02 19:42 ` Taylor, Grant
2005-05-02 20:55 ` John G. Norman
2005-05-02 21:01 ` Jason Opperisano
2005-05-02 21:12 ` Ramoni
2005-05-02 21:18 ` John G. Norman
2005-05-02 21:55 ` Taylor, Grant
2005-05-03 2:27 ` iptables ip forwarding elg3ne
2005-05-02 21:15 ` On vanilla Fedora 3, can't do a transparent proxy (-j REDIRECT) John G. Norman
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=20050502205742.GA12530@bender.817west.com \
--to=opie@817west.com \
--cc=netfilter@lists.netfilter.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.