ashok kumar
Network Engineer
CCNP/MCSA
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello,
I am having similar issue, while other social media sites are not working twitter is still working.
I have both application control and web control with SSL enabled.
i have to problem that my FGt sems to ignore static url filter on https sites.
in Policy webfilter profile is enabled and so is ssl inspection. Deep Inspection os on (since some said that url filtering wil not work if you only have cert inspectiomn on). Though the FGT keeps not applying any url filter rules.
It only seems to use the cathegories I chose under reputative sites.
Even TAC could not yet provide me with a solution...
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
I noticed the same thing as well.
If seems the FortiGuard category based filter takes precedence over the static url filter.
Some "weirdness" just off the top of my head....
This going back to the 4.1 to 4.2 days, where the script conversion process during an firmware upgrade had truncated any object name that a "space" character in the name. I wasn't around when someone on the team thought it would be a wonderful idea to trigger a firmware upgrade on some 50 fgts via FGR on a Friday - come Monday we were swamped with calls about non-working Internet - Took about 5 minutes performing a diff on the before/after configs to see some our URL filtering labels were "truncated" because they had a space character (e.g. "daytime urlfilter") and a few other places. Ended up manually fixing (renaming) those labels.
Don't know how this happen, but somehow a non-standard character code was introduced in the config file, at about where the url filter section was - would cause the fgt to "choke" and stop processing anything further in that section - same thing would happen if you are manually copying/pasting sections via the CLI and a quote " is missed.
URL filters are processed from top-to-down - with that in mind, someone on the team kept adding invalid URL entries to a URL list - sometimes moving them around, that caused something akin to a wildcard entry at or near the top of the URL list, so no further URL filter rules were processed after that entry.
Don't know if this still a problem on later firmware, but if you clone a Webfilter policy, all instance of that original policy will reference the same URL filter list. (e.g. edit/add an entry to the URL filter list in the cloned policy will show up in the original policy or vice versa. ). So when or if I need to clone a web filter policy, I ensure afterwards to deselect the URL filter list then reselect it so it gives a fresh (blank) URL filter list.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
ashok kumar
Network Engineer
CCNP/MCSA
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1713 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.