From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Instructions on how to redirect port 80 to port 8080
Date: Wed, 18 Feb 2004 15:08:26 +0000 [thread overview]
Message-ID: <200402181508.26102.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <9908FCB837A50642B74E2BEC198843095CC654@csrees-exchsrvb.csrees.usda.gov>
On Wednesday 18 February 2004 2:31 pm, Martinez, Michael wrote:
> --> Please flush the counters on your rules using "iptables -Z;
> --> iptables -Z -t nat", connect to port 8080, and then tell us the output
> --> of "iptables -L -nvx;
I've eliminated most of the lines which have zero packet counts, as they mean
no traffic was seen:
> Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 131 10661 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0
> 0.0.0.0/0
131 packets in total, all from your user-defined chain...
> Chain RH-Firewall-1-INPUT (2 references)
> pkts bytes target prot opt in out source
> destination
> 36 1828 ACCEPT all -- lo * 0.0.0.0/0
> 0.0.0.0/0
36 packets on the loopback interface - any idea what this is?
> 82 5404 ACCEPT all -- * * 0.0.0.0/0
> 0.0.0.0/0 state RELATED,ESTABLISHED
82 packets ESTABLISHED or RELATED came in
> 1 48 ACCEPT tcp -- * * 0.0.0.0/0
> 0.0.0.0/0 state NEW tcp dpt:22
One packet on port 22 (SSH)
> 0 0 ACCEPT tcp -- * * 0.0.0.0/0
> 0.0.0.0/0 state NEW tcp dpt:80
NO packets on port 80...
> 12 3381 REJECT all -- * * 0.0.0.0/0
> 0.0.0.0/0 reject-with icmp-host-prohibited
And 12 rejected packets - maybe LOGging these before rejecting them would be
helpful in this case, just so we know what they are?
> --> iptables -L -t nat -nvx".
>
> Chain PREROUTING (policy ACCEPT 19 packets, 4845 bytes)
> pkts bytes target prot opt in out source
> destination
> 0 0 REDIRECT tcp -- * * 0.0.0.0/0
> 199.128.238.12 tcp dpt:80 redir ports 8080
And NO packets got redirected from 80 to 8080...
I still don't see how you are successfully getting a connection on port 8080
when there is no rule to allow it.
Regards,
Antony.
--
There are two possible outcomes:
If the result confirms the hypothesis, then you've made a measurement.
If the result is contrary to the hypothesis, then you've made a discovery.
- Enrico Fermi
next prev parent reply other threads:[~2004-02-18 15:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 14:31 Instructions on how to redirect port 80 to port 8080 Martinez, Michael
2004-02-18 15:08 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 19:19 Martinez, Michael
2004-02-18 19:06 Martinez, Michael
2004-02-18 19:10 ` Antony Stone
2004-02-18 18:47 Martinez, Michael
2004-02-18 19:02 ` Antony Stone
2004-02-18 17:47 Martinez, Michael
2004-02-18 16:07 Martinez, Michael
2004-02-18 16:21 ` Antony Stone
[not found] <9908FCB837A50642B74E2BEC198843095CC655@csrees-exchsrvb.csrees.usda.gov>
2004-02-18 15:01 ` Fabian Hartmann
2004-02-18 15:11 ` Antony Stone
2004-02-18 14:41 Sven-Åke Larsson
2004-02-18 14:06 Martinez, Michael
2004-02-18 14:19 ` Antony Stone
2004-02-18 17:28 ` Alexis
2004-02-17 19:24 Martinez, Michael
2004-02-17 18:55 Martinez, Michael
2004-02-17 19:04 ` Alexis
2004-02-17 19:10 ` Alexis
2004-02-17 19:30 ` Antony Stone
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=200402181508.26102.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox