Title: rule 0
Rule 0 means it was dropped due to something not explicitly listed in the rulebase, due to policy---properties settings, anti-spoofing, etc..  With 4.0 you can go to view---implied pseudo rules to display the "policy properties" rules.  Phoneboy has a good description on his site www.phoneboy.com, search the faq's for rule 0.
 
Or wait a few minutes and see if he posts an answer himself  :-)
 
-PaulK

*********************************************
Paul Keser
Network Security Engineer
[EMAIL PROTECTED]
tel:   415.351.4037
fax:  415.474.6017

ShopExpert.com
1375 Sutter Street, Suite 400
San Francisco, CA  94109
*********************************************

-----Original Message-----
From: Wales, Holly [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 22, 2000 3:53 PM
To: '[EMAIL PROTECTED]'; Wales, Holly
Subject: [FW1] rule 0

I have successfully incorporated certificates into a client that is a secureremote user.
When I use secureremote, I see where the firewall generates a key and I see the information in the certificate that is being used.  (Yeah. It took me a while to get to that part.)

Anyway, the problem that I see is in the logs. Rule 0 rejects my secureremote connection. What is rule 0? I believe I heard that it is a spoofing rule. How do you modify Rule 0?

Holly Wales
Lockheed Martin
[EMAIL PROTECTED]
phone: 256-544-4179
fax: 256-544-2401



Reply via email to