All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Gibson" <paul.gibson@subspace.net.au>
To: 'Netfilter' <netfilter@lists.netfilter.org>
Subject: RE: Query....  redirecting traffic
Date: Fri, 13 Dec 2002 20:57:15 +1100	[thread overview]
Message-ID: <009201c2a28e$044bfde0$0501a8c0@gndn.subspace.au.com> (raw)
In-Reply-To: <1039772820.15363.4.camel@sander>

Wow

Thanks very much for all the replies.....  and examples too :)
Looks like I can get rid of the dodgy redir.

thanks again! :)

-----Original Message-----
From: Sander Sneekes [mailto:sander@dmdsecure.com]
Sent: Friday, 13 December 2002 8:47 PM
To: paul.gibson@subspace.net.au
Cc: Netfilter
Subject: Re: Query.... redirecting traffic


iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -j MASQUERADE

iptables -A FORWARD -p tcp --dport 80 -d 192.168.1.1 -j ACCEPT
iptables -A PREROUTING -t nat -p tcp --dport 80 -d 10.10.10.10 -j DNAT
--to
192.168.1.1:12345

On Fri, 2002-12-13 at 10:02, Paul Gibson wrote:
> Hello,
>
> 	I am wondering if netfilter can do the following.....
>
> http connection comes in on 10.10.10.10 port 80, can iptables then
redirect
> this to go to 192.168.1.1 port 12345 & also allow the returning data to go
> back the opposite way ???
>
> We are currently using "redir" to do it and are having some porblems with
it
> due to an application we run.
>
> TIA
>
> Paul.
--
Sander Sneekes
sander@dmdsecure.com

--
Never argue with an idiot. They drag you down to their level, then beat
you with experience.



  reply	other threads:[~2002-12-13  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  0:34 Does IPTables have a 1:1 port-forwarding capability for a DNAT port-range ? Ranjeet Shetye
2002-12-13  9:02 ` Query.... redirecting traffic Paul Gibson
2002-12-13  9:47   ` Sander Sneekes
2002-12-13  9:57     ` Paul Gibson [this message]
2002-12-13 12:02 ` Does IPTables have a 1:1 port-forwarding capability for a DNAT port-range ? Andrea Rossato
2002-12-13 17:45   ` Ranjeet Shetye

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='009201c2a28e$044bfde0$0501a8c0@gndn.subspace.au.com' \
    --to=paul.gibson@subspace.net.au \
    --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.