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: Tue, 17 Feb 2004 19:30:37 +0000 [thread overview]
Message-ID: <200402171930.37729.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1077045002.2397.54.camel@pepelui.baicom>
On Tuesday 17 February 2004 7:10 pm, Alexis wrote:
> iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to
> x.x.x.x:8080
You might prefer to use REDIRECT - it's like DNAT, but only allows you to
specify the port number, and forces the IP address to the local machine:
iptables -A PREROUTING -t nat -d a.b.c.d -p tcp --dport 80 -j REDIRECT --to
8080
(Note that I've added a "-d a.b.c.d" where a.b.c.d is the IP address of the
machine with the rule on it - otherwise it would redirect *all* TCP port 80
traffic, whether it was originally addressed to this machine or somewhere
else.)
Regards,
Antony.
> On Tue, 2004-02-17 at 16:04, Alexis wrote:
> > iptables -t mangle -A PREROUTING -p tcp --dport 80 -j DNAT --to
> > x.x.x.x:8080
> >
> > could be a start :)
> >
> > On Tue, 2004-02-17 at 15:55, Martinez, Michael wrote:
> > > Guys -
> > >
> > > I'm finding a lack of documentation describing how to do this. It ought
> > > to be simple. I know how to do it with ipchains.
> > >
> > > On a redhat linux system using /etc/sysconfig/iptables, what line(s) do
> > > I add to /etc/sysconfig/iptables to configure to redirect all inbound
> > > port 80 traffic to port 8080 on the same host?
> > >
> > > Thank you -
> > >
> > > Regards,
> > >
> > > Michael Martinez
> > > ISTM/CSREES
> > > United States Department of Agriculture
> > > ---
> > > This email is signed with my digital signature so that you may verify
> > > the authenticity of the sender.
--
These clients are often infected by viruses or other malware and need to be
fixed. If not, the user at that client needs to be fixed...
- Henrik Nordstrom, on Squid user's mailing list
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-02-17 19:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 18:55 Instructions on how to redirect port 80 to port 8080 Martinez, Michael
2004-02-17 19:04 ` Alexis
2004-02-17 19:10 ` Alexis
2004-02-17 19:30 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 19:24 Martinez, Michael
2004-02-18 14:06 Martinez, Michael
2004-02-18 14:19 ` Antony Stone
2004-02-18 17:28 ` Alexis
2004-02-18 14:31 Martinez, Michael
2004-02-18 15:08 ` Antony Stone
2004-02-18 14:41 Sven-Åke Larsson
[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 16:07 Martinez, Michael
2004-02-18 16:21 ` Antony Stone
2004-02-18 17:47 Martinez, Michael
2004-02-18 18:47 Martinez, Michael
2004-02-18 19:02 ` Antony Stone
2004-02-18 19:06 Martinez, Michael
2004-02-18 19:10 ` Antony Stone
2004-02-18 19:19 Martinez, Michael
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=200402171930.37729.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