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 14:19:04 +0000 [thread overview]
Message-ID: <200402181419.04235.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <9908FCB837A50642B74E2BEC198843095CC652@csrees-exchsrvb.csrees.usda.gov>
On Wednesday 18 February 2004 2:06 pm, Martinez, Michael wrote:
> --> iptables -A PREROUTING -t nat -d a.b.c.d -p tcp --dport 80
> --> -j REDIRECT --to 8080
>
> This isn't working. I can "telnet `hostname` 8080" and get an http
> response, but when I do "telnet `hostname` 80" the response I get is
> "telnet: Unable to connect to remote host: Connection refused."
Given the ruleset you've posted, I don't see how a telnet to 8080 can work,
since you have no INPUT rule allowing packets to that port...
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;
iptables -L -t nat -nvx".
> -A PREROUTING -d 199.128.238.12 -p tcp -m tcp --dport 80 -j REDIRECT
> --to-ports 8080
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [417:40204]
> :RH-Firewall-1-INPUT - [0:0]
>
> -A INPUT -j RH-Firewall-1-INPUT
> -A FORWARD -j RH-Firewall-1-INPUT
> -A RH-Firewall-1-INPUT -i lo -j ACCEPT
> -A RH-Firewall-1-INPUT -p icmp -m icmp any -j ACCEPT
> -A RH-Firewall-1-INPUT -p esp -j ACCEPT
> -A RH-Firewall-1-INPUT -p ah -j ACCEPT
> -A RH-Firewall-1-INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
> -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j
> ACCEPT
> -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j
> ACCEPT
> -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
Regards,
Antony.
--
Never write it in Perl if you can do it in Awk.
Never do it in Awk if sed can handle it.
Never use sed when tr can do the job.
Never invoke tr when cat is sufficient.
Avoid using cat whenever possible.
next prev parent reply other threads:[~2004-02-18 14:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 14:06 Instructions on how to redirect port 80 to port 8080 Martinez, Michael
2004-02-18 14:19 ` Antony Stone [this message]
2004-02-18 17:28 ` Alexis
-- 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:31 Martinez, Michael
2004-02-18 15:08 ` Antony Stone
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=200402181419.04235.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