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 FullDisclosure
[Top] [All Lists]

RE: [Full-Disclosure] PIX vs CheckPoint

Subject: RE: [Full-Disclosure] PIX vs CheckPoint
Date: Wed, 30 Jun 2004 15:41:26 -0400
That is odd.  When dealing with a Pix firewall, no traffic can go out an 
interface without some sort of translation statement.

Even the default configuration has this:

     nat (inside) 1 0.0.0.0 0.0.0.0 0 0

There must be either a static or dynamic translation statement in your 
configuration.


-----Original Message-----
From: full-disclosure-admin@lists.netsys.com 
[mailto:full-disclosure-admin@lists.netsys.com] On Behalf Of Cyril Guibourg
Sent: Wednesday, June 30, 2004 2:18 PM
To: Otero, Hernan (EDS)
Cc: full-disclosure@lists.netsys.com
Subject: Re: [Full-Disclosure] PIX vs CheckPoint

"Otero, Hernan         (EDS)" <HOtero@lanchile.cl> writes:

I think you do, because at least a nat 0 it´s needed to get traffic passing
through the pix.

This is odd, I do have a running config under 6.2 without any nat statement.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html



This e-mail is the property of Oxygen Media, LLC.  It is intended only for the 
person or entity to which it is addressed and may contain information that is 
privileged, confidential, or otherwise protected from disclosure. Distribution 
or copying of this e-mail or the information contained herein by anyone other 
than the intended recipient is prohibited. If you have received this e-mail in 
error, please immediately notify us by sending an e-mail to 
postmaster@oxygen.com and destroy all electronic and paper copies of this 
e-mail.



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