Re: Private Address Spaces

• Previous message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "Conspiracy.com", R. J. Pineiro"
• In reply to: Bernie: "Re: Private Address Spaces"
• Next in thread: Kurt L: "Re: Private Address Spaces"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Thu, 10 Jul 2003 15:59:03 GMT

"Bernie" <Bernie@weekend.com> wrote in message
news:errqgvoj4pf4tnqa449nrkkq4q1u7fb66f@4ax.com...
> On Wed, 9 Jul 2003 23:19:10 -0700, "Kurt L" <kurtl@olypen.com> wrote:
>
> >
> >You can use any IP addresses you want as long as you use them
PRIVATELY.
> >That is, no traffic carrying a publicly owned ip address (unless you
are the
> >owner) leaves your private network. It's also perfectly acceptable to
use
> >public IPs privately if you use NAT to connect to the Internet, so the
> >inside IPs stay inside. Still, as pointed out, you have a full class A
> >(10), a Class B (172.16) and 256 class C's (192.168.0 - 192.168.254) -
OK,
> >255! With that much private space, why use anything else?
> >
> >...kurt
>
> As Don pointed out, there are real problems with this. Yes, you "can"
> use any public IP you want on your private network and use NAT to
> connect to the public network. It will appear to work 99.999% of the
> time too. Yes it is I suppose even legal to do so. However, you are
> stupid to do so because you are going to inevitably cause yourself
> problems...maybe not today or tomorrow, but possibly the next day.
>
> Suppose you are using 20.x.x.x internally. Suppose you go to a
> website whose DNS resolves to 20.x.x.x. That is, the company that is
> hosting this is the real owner of the 20.x.x.x pool. From your
> perspective the webserver is local, and you will never, ever send the
> packets out to the public network regardless of NAT or anything else.
> The webserver will just appear to be unreachable, and the same admin
> that set up the addressing scheme will be just as clueless in solving
> the "unreachable webserver" problem as he is in proper IP addressing.
> He will just point the finger at the other company's webserver or
> email server or whatever and it will never dawn on him that he is
> causing the problem, not the other company.
>
>
> --Bernie

Bernie,

Thanks for the reiteration.

I'd like to also add what was stated in my original reply and this would
be that no system within the registered 20.x.x.x range on the 'net will be
able to send traffic to the LAN where the 'pirated' 20.x.x.x range is
being used.

In essence the company using the 'pirated' IP's are effectively preventing
themselves from being able to send to or receive from 16.5 million IP
addresses. Not a good thing in my book. <grin>

-- 
Best regards,
Don Kelloway
Commodon Communications
Visit http://www.commodon.com to learn about the "Threats to Your Security
on the Internet".

• Previous message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "Conspiracy.com", R. J. Pineiro"
• In reply to: Bernie: "Re: Private Address Spaces"
• Next in thread: Kurt L: "Re: Private Address Spaces"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]