Re: using public ip address on private networ

Well, using globally assigned address space in your network is a bad
idea. When you start with a bad idea that you need to implement, the
only way to make it work is CF.

This thread is about a bad idea :-). I offered the solution for a
problem that results from it. Don't shoot the messenger ... :-)

--
Marko Milivojevic - CCIE #18427
Senior Technical Instructor - IPexpert
YES! We include 400 hours of REAL rack
time with our Blended Learning Solution!
Mailto: markom_at_ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
Web: http://www.ipexpert.com/
On Mon, Apr 26, 2010 at 12:40, Ryan West <rwest_at_zyedge.com> wrote:
> Marko,
>
>> -----Original Message-----
>> Sent: Monday, April 26, 2010 1:32 PM
>> To: dls152_at_cox.net; groupstudy
>> Subject: Re: using public ip address on private networ
>>
>> > What happens if there is a host on internet with same addressing we use
>> > internally? The host B destination address is being routed on lan what
>> happens?
>> > How does the users gain access to public host?
>>
>> Obviously, you can't access it directly. However, you can translate
>> the name of the ouside hosts with overlapping addresses to something
>> else. For example, you can map external hosts, 1:1, to some of the
>> RFC1918 ranges and be done with it.
>>
>
> That sounds like a CF :) B It's bad enough to deal with RFC1918 overlap, why try to translate allocated public space.
>
> -ryan
Blogs and organic groups at http://www.ccie.net