Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: NAT external/Public IP

Subject: Re: NAT external/Public IP
Date: 25 Oct 2007 13:39:31 -0000
There is no problem wrt using a public IP address internally, the only reason 
you would not use valid IP addresses internally is if you do not have 
sufficient public addresses, then you would use RFC1918 addrsses internally and 
then Nat them outbound onto a valid Public address, this also stops persons 
knowing what your internal network range is, as it will show as coming from 
your nat'd address.

What do you want to use a public address internally for anyway? If it is for a 
web server or FTP server internally, then you can do a NAT inbound rather, to a 
private address.

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