Screen OS

last person joined: 8 months ago 

This is a legacy community with limited Juniper monitoring.
  • 1.  SSG 20 - Web Filtering problem

    Posted 04-27-2009 03:21

    Hello all,

     

    I have configured Web Filtering rules at SSG 20

    I have added some custom categories and it works.

     

    But sometimes there are records in the event log like this one below ( for example 😞

     

     

    UF-MGR: URL BLOCKED: 192.168.100.3(2269)->74.125.153.147(80) bp0.blogger.com/_umr7psgwaaw/sf9qbd0b-mi/aaaaaaaaeji/baqjgjgm7gm/s400/yurika-m CATEGORY: default REASON: BY_FAIL_MODE PROFILE: Saintpeter

     

    It is so weird because i can't find the default category in my custom Web Filtering category or in the pre defined category.

    Has anybody got the same problem like this ?

     

     

    Regards,

     

    Leo

     

     



  • 2.  RE: SSG 20 - Web Filtering problem
    Best Answer

    Posted 04-29-2009 00:17

    Reason BY_FAIL_MODE implies that the URL was blocked as a result of URL filtering not able to send to UF server and fail mode was set to block. So basically the UF engine needed to check the URL, but the UF engine could not for whatever reason (could be UF server was not reachable at that time). So with fail-mode block the URL will not be permitted. You can set fail-mode to permit if you would rather allow the URL if there is a problem with the UF engine.

     

    Example:

    set url protocol sc-cpa

    set fail-mode permit

    exit

     

    -Richard



  • 3.  RE: SSG 20 - Web Filtering problem

    Posted 04-30-2009 01:29

    @ rkim

    Your idea is works.

    Thanks bro



  • 4.  RE: SSG 20 - Web Filtering problem

    Posted 06-15-2009 08:03

    Hi Richard,

     

    I search all around and only found this message you suggested.  I did your sample. but still showing the reason BY_FAIL_MODE, but the profile is different.

     

    Does the fail mode permission goes by profile? If so, how can I change to another profile and set the fail mode permission?

     

    Thanks,

    Eric.