NetFilter
[Top] [All Lists]

NAT addresses - RFC or tradition?

To: <netfilter@lists.netfilter.org>
Subject: NAT addresses - RFC or tradition?
From: Paul Blondé <jpb@entel.ca>
Date: Tue, 22 May 2007 12:26:07 -0700
Delivered-to: sp-com-lists@consult.net
Delivered-to: netfilter-list1@securepoint.com
Importance: Normal
In-reply-to: <46533B98.9030706@riverviewtech.net>
List-archive: </pipermail/netfilter>
List-help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-id: General discussion and user questions <netfilter.lists.netfilter.org>
List-post: <mailto:netfilter@lists.netfilter.org>
List-subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
List-unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>, <mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
Organization: enTel Communications Inc
Reply-to: jpb@entel.ca
Sender: netfilter-bounces@lists.netfilter.org
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.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Paul Blondé



<Prev in Thread] Current Thread [Next in Thread>