From: Shawn <core@enodev.com>
To: Alistair@nerdnet.ca
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: Is this correct?
Date: 19 Jun 2003 22:13:06 -0500 [thread overview]
Message-ID: <1056078786.14334.88.camel@localhost> (raw)
In-Reply-To: <200306191806.33601.Alistair@nerdnet.ca>
> > iptables -t nat -I PREROUTING -i eth0 -d 10.0.0.1 -J DNAT \
> > --to 192.168.0.1
>
> Ummm .
> Where is 10.0.0.1? (since the network is /24)
> If eth0's ip is 10.0.0.250 why would any packets for 10.0.0.1 end up
> there? Unless there is an *external* routing reference that puts 10.0.0.1
> through 10.0.0.250 this cannot work. If there is such a routing, the rule
> should work.
My scenario was bogus. Sorry! 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, and should DNAT those
packets to 192.168.0.1.
The problem with my original scenario was that since the hosts needing
to reach 10.0.0.1/24 (which is really 192.168.0.1) were on the
10.0.0.1/24 network themselves. Why would they need to look up a route
for a host that's supposed to be on the same network as them?
So, others were saying to assign 10.0.0.1 to linux-router/eth0:1 (I
guess) so the host would actually get all the packets intended for
10.0.0.1. I guess it's surprising to me if this works, because at what
point does linux-router decide if a packet if to be forwarded or
accepted as it's own? If eth0 has 10.0.0.1, would DNATing the packet to
192.168.0.1 keep linux-router from owning the packet?
Hmmm...
next prev parent reply other threads:[~2003-06-20 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 21:07 Is this correct? Shawn
2003-06-19 22:06 ` Alistair Tonner
2003-06-20 3:13 ` Shawn [this message]
2003-06-20 4:09 ` Alistair Tonner
-- 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:10 George Vieira
2003-06-20 2:28 ` Shawn
2003-06-20 2:41 ` Shawn
2003-06-19 22:06 Daniel Chemko
2003-06-20 2:30 ` Shawn
2003-06-20 2:35 ` Shawn
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=1056078786.14334.88.camel@localhost \
--to=core@enodev.com \
--cc=Alistair@nerdnet.ca \
--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.