All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: RE: Is this correct?
Date: 19 Jun 2003 21:41:59 -0500	[thread overview]
Message-ID: <1056076918.14334.24.camel@localhost> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A0192A0@wardrive.citadelcomputer.com.au>

Do you say add 10.0.0.1 to eth0 because you figure I lack an external
routing reference making packets arrive at my host?

Come to think of it, there probably wouldn't be a router that could do
that in my scenario. Sorry if I was confusing. It's probably more
accurate to say that some host "10.23.4.209" is going to try to reach
10.0.0.1, and 10.0.0.250 is the last hop on the way there.

Now does that sound better?

On Thu, 2003-06-19 at 17:10, George Vieira wrote:
> The only way I know of to do that is use iproute2 (or ifconfig) and add that IP to the firewalls eth0 device and fix your rule (lowercase J).
> 
> ip addr add 10.0.0.1/8 dev eth0
> iptables -t nat -I PREROUTING -i eth0 -d 10.0.0.1 -j DNAT \
>  --to 192.168.0.1
> 
> I think that'll work OK..
> 
> Thanks,
> ____________________________________________
> George Vieira
> Systems Manager
> georgev@citadelcomputer.com.au
> 
> Citadel Computer Systems Pty Ltd
> http://www.citadelcomputer.com.au
> 
> Phone   : +61 2 9955 2644
> HelpDesk: +61 2 9955 2698
>  
> 
> -----Original Message-----
> From: Shawn [mailto:core@enodev.com]
> Sent: Friday, June 20, 2003 7:07 AM
> To: netfilter@lists.netfilter.org
> Subject: Is this correct?
> 
> 
> I have a, iptables statement I would just like someone to say if I have
> it right.
> 
> Let's say I have a linux box with eth0=10.0.0.250 and
> eth1=192.168.0.250, and there's a host (192.168.0.1) connected to eth1.
> I want to route connections from hosts in 10.0.0.0/24 land to 10.0.0.1
> onto the linux box's eth0, and have them NATed to 192.168.0.1
> 
> Will the following statement do that?
> 
> iptables -t nat -I PREROUTING -i eth0 -d 10.0.0.1 -J DNAT \
> 	--to 192.168.0.1
> 
> 
> 


  parent reply	other threads:[~2003-06-20  2:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 22:10 Is this correct? George Vieira
2003-06-20  2:28 ` Shawn
2003-06-20  2:41 ` Shawn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 12:01 is this correct ? Aleksandr Guidrevitch
2004-02-11  0:03 ` Antony Stone
2003-06-20  3:52 Is this correct? George Vieira
2003-06-20  3:37 George Vieira
2003-06-20  3:23 George Vieira
2003-06-20  2:49 George Vieira
2003-06-20  3:19 ` Shawn
2003-06-20  2:39 George Vieira
2003-06-20  3:10 ` Shawn
2003-06-19 22:06 Daniel Chemko
2003-06-20  2:30 ` Shawn
2003-06-20  2:35   ` Shawn
2003-06-19 21:07 Shawn
2003-06-19 22:06 ` Alistair Tonner
2003-06-20  3:13   ` Shawn
2003-06-20  4:09     ` Alistair Tonner
2003-06-12 15:43 Is this correct ? Frank R Callaghan
2003-06-12 19:57 ` Frank R Callaghan

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=1056076918.14334.24.camel@localhost \
    --to=core@enodev.com \
    --cc=georgev@citadelcomputer.com.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.