|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [FW1] Seemingly "broken" objects in FW1 4.1
Johan, Seems like you've used reserved word(s) by CP or the objects.C file has some corruption. What is the name of the object(s)? Robert - - Robert P. MacDonald, Network Engineer Team Lead, e-Business Infrastructure G o r d o n F o o d S e r v i c e Voice:email: [email protected] >>> Johan Lindstrom <[email protected]> 11/24/00 11:01:55 AM >>> > >Hi! > >I found this list yesterday when trying to find information about a problem >we have. If this isn't the correct forum, please enlighten me :) > >Anyway, we recently performed a new install of FW1 4.1 >(patchlevel/upgrade/whatever 2). During testing the weirdest things >happened. Traffic that should be matched by a rule simply didn't match and >would then bump into the last rule (drop and alert) instead. > >We tried to isolate the problem and after a few tests the problem seemed to >be a particular Network Object, a workstation in the Source-field of the >rule. We could not find anything wrong with the workstation object (apart >from the fact that it didn't actually work). > >So we created an _identical_ object only with a different name. With that >object in place of the broken one the rule worked fine, matching the >traffic we expected. Further testing revealed a number of other objects >that also seems to be broken. > >So my question is if this behaviour rings a bell. Does it look like >anything you guys have experienced before? > >/J >-- >Johan Lindström, Sourcerer, Boss Casinos Ltd, Antigua ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
