From: "Tim Evans" <tkevans@tkevans.com>
To: "Andre Guimarães " <ramoni@databras.com.br>,
netfilter@lists.netfilter.org
Cc: tkevans@tkevans.com
Subject: Re: NAT addresses - RFC or tradition?
Date: Tue, 22 May 2007 15:57:07 -0400 [thread overview]
Message-ID: <20070522195618.M46626@tkevans.com> (raw)
In-Reply-To: <200705221646.25925.ramoni@databras.com.br>
On Tue, 22 May 2007 16:46:25 -0300, Andre Guimarães wrote
> It's quite simple.
> You're using public IPs in your internal networks.
> Some of these IPs may exist and have an owner an maybe even a web site.
> You'll be in trouble in the day you wish to acess one of these IPs
> on the internet because you won't reach them because you have them
> on your network and so won't route the packets to the internet.
In other words, the RFC addresses are specifically for use in internal
networks, since they are guaranteed not to be used on the public internet, and
not routed to by any public internet router.
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
tkevans@tkevans.com | Owings Mills, MD 21117
http://www.tkevans.com/ | 443-394-3864
http://www.come-here.com/News/ |
next prev parent reply other threads:[~2007-05-22 19:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 14:28 Bridge Transparent Proxy Jon Tim
2007-05-22 14:35 ` Robert LeBlanc
2007-05-22 16:06 ` Pascal Hambourg
2007-05-23 5:56 ` Jon Tim
2007-05-23 13:39 ` Gáspár Lajos
2007-05-22 16:09 ` Grant Taylor
2007-05-22 17:07 ` Robert LeBlanc
2007-05-22 18:30 ` Grant Taylor
2007-05-22 18:36 ` Pascal Hambourg
2007-05-22 18:51 ` Grant Taylor
2007-05-22 19:26 ` NAT addresses - RFC or tradition? Paul Blondé
2007-05-22 19:46 ` Andre Guimarães
2007-05-22 19:57 ` Tim Evans [this message]
2007-05-22 20:02 ` Marius-Iulian Corici
2007-06-18 17:27 ` R. DuFresne
2007-06-18 17:25 ` R. DuFresne
2007-05-22 20:02 ` Leonardo Rodrigues Magalhães
2007-05-22 20:22 ` Grant Taylor
2007-05-22 21:39 ` Bridge Transparent Proxy Petr Pisar
2007-05-22 22:07 ` Pascal Hambourg
2007-05-23 0:25 ` Grant Taylor
2007-05-22 18:39 ` Robert LeBlanc
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=20070522195618.M46626@tkevans.com \
--to=tkevans@tkevans.com \
--cc=netfilter@lists.netfilter.org \
--cc=ramoni@databras.com.br \
/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.