topic Re: playboy.com and dropbox.com categorized as "unknown" in General Topics

playboy.com and dropbox.com categorized as "unknown"

jambulo — Wed, 12 Oct 2011 15:30:38 GMT

I just realized that playboy.com and dropbox.com are being catergorized as "unknown". "Unknown" has been set to alert only, and not block. I have no idea how long it has been like this, or what other sites may be doing the same thing. I'm on URL Filtering version 3713.

Anyone else have this issue? Should I upgrade or revert my URL Filter version?

Re: playboy.com and dropbox.com categorized as "unknown"

gswcowboy — Wed, 12 Oct 2011 15:34:34 GMT

What PANOS version are you running?

Re: playboy.com and dropbox.com categorized as "unknown"

jambulo — Wed, 12 Oct 2011 15:44:47 GMT

I'm on 3.1.7, but I think I found my answer...

(Link removed, Issue fixed in 3.1.9)

...clearing the cache fixed it.

Re: playboy.com and dropbox.com categorized as "unknown"

gswcowboy — Wed, 12 Oct 2011 16:00:04 GMT

Clearing the cache is a temporary solution. The bug is fixed in 3.1.9 but I'd recommend upgrading to 3.1.10 when you're able to get a maintenance window approved.

Re: playboy.com and dropbox.com categorized as "unknown"

jambulo — Wed, 12 Oct 2011 16:05:08 GMT

I will plan on upgrading. Is there a reason you did not suggest upgrading to 4.0.5?

Re: playboy.com and dropbox.com categorized as "unknown"

gswcowboy — Wed, 12 Oct 2011 22:34:49 GMT

I figured you wanted to stay on 3.1.x branch. I wasn't sure if you were interested in the 4.0.x features such as active/active HA, Global Protect, etc.

Re: playboy.com and dropbox.com categorized as "unknown"

camkim_MDEA — Wed, 12 Oct 2011 22:47:00 GMT

Unless there is a must have feature on 4.x, I think its ok to stay on 3.1.x. One of the more noticeable things on 4.x is that the GUI is slower than on 3.1.x. Plus a few minor issues that are affecting the stability (there are other threads here floating around...)

We are on 3.1.9 on a pair of 500's and we are sitting put until they work out the kinks.

I would definitely upgrade to 3.1.9 or 3.1.10 to address that unknown issue.