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: RE: NAT external/Public IP

Subject: RE: RE: NAT external/Public IP
Date: Mon, 29 Oct 2007 09:21:58 -0700
Without NAT you 
may require to inject external IP/subnet into the internal 
network. 

  No -- that's not how networking with TCP/IP works.

  Responses to those packets can almost certainly rely on 
default routing back to the Internet.

David Gillett


-----Original Message-----
From: listbounce@securityfocus.com 
[mailto:listbounce@securityfocus.com] On Behalf Of 
smarts_buy@yahoo.com
Sent: Saturday, October 27, 2007 12:57 AM
To: security-basics@securityfocus.com
Subject: Re: RE: NAT external/Public IP

My query is more abt the requiremnt for NAT the external IP 
coming into the enterprise network like bank. Without NAT you 
may require to inject external IP/subnet into the internal 
network. Does this pose any security risk? We do hide our 
internal IPs.


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