When the other engineer said the SA500 only filters content on port 80 we can only filter normal unencrypted web traffic. Since https is encrypted the router can't read the content at which the end user is accessing. Since the router can't read this content because it is encrypted then we can't filter any content that uses https or 443 traffic. That being said some people filter at the DNS query as i do. Instead of trying to block at content we can block the DNS query. OpenDns is a good way to accomplish blocking at DNS level.
Just an example if i blocking content for facebook.com
That does not make any sense. The url is not encrypted so url filtering should be able to block access to the URL. Real content filtering solutions such as sonicwall, websense etc seem to be able to block https site access. I'm positive this is just a Cisco SA520 short coming in that it only blocks port 80 url access.
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...
Introduction: This document describes how to connect SG300 with Catalyst
switch via STP. Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on mainly on switches. The specification for STP is IEEE 802.1D.
The main purpose of STP is to ensure tha...