Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: jpb@entel.ca
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT addresses - RFC or tradition?
Date: Tue, 22 May 2007 17:02:52 -0300	[thread overview]
Message-ID: <46534C6C.3050706@solutti.com.br> (raw)
In-Reply-To: <001c01c79ca7$0c1717e0$5a05a8c0@nisgaa.net>



Paul Blondé escreveu:
> I've noticed that a lot of people use the 192.168.X.X subnet for internal
> networks, is this (and the less-used 10-series) a requirement of some RFC,
> or a recommendation that has become tradition?
>
> We are using a completely different subnet, something similar to (for
> example) 42.127.129.X to further obfuscate the internal network from
> outside. This, and many other examples, produces a class-A subnet mask (some
> produce a class-B) when entered in WinXP's TCP/IP dialog, although the
> actual mask we use with it is class-C.
>
> Is this a no-no? Will it break our server's IPTables when communicating with
> it? Am I in for a lot of trouble? The addresses don't seem to cause any
> problems, but I don't want this to jump up and bite us in the bottom
> sometime down the road.
>   

    Yes, those 'reserved' IP addresses are declared by RFC 1918. Please 
check:

http://tools.ietf.org/html/rfc1918
http://en.wikipedia.org/wiki/Private_network

    Your network will work with no problems, except if you had to access 
some far-far-far away network which uses your local addresses, which 
should never be used as local ones.

   

-- 


	Atenciosamente / Sincerily,
	Leonardo Rodrigues
	Solutti Tecnologia
	http://www.solutti.com.br

	Minha armadilha de SPAM, NÃO mandem email
	gertrudes@solutti.com.br
	My SPAMTRAP, do not email it






  parent reply	other threads:[~2007-05-22 20:02 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
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 [this message]
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=46534C6C.3050706@solutti.com.br \
    --to=leolistas@solutti.com.br \
    --cc=jpb@entel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox