AdminSky.org

“The difference between the Cisco WebVPN and SSL VPN Client is that Cisco WebVPN uses SSL/TLS and port forwarding via a java app for application support, it also only supports unicast TCP traffic, no IP address is assigned to the client, and all the web-browsing down the tunnel is done with an SSL web-mangle that allows you to stuff things into the SSL session.”

“However, the Cisco SSL VPN Client is a full tunneling client using SSL/TCP that installs an app on the machine and envelopes the VPN traffic into the SSL session and also has an IP address assigned so the tunnel is two way, not uni-directional. It allows for application support over the tunnel without having to set up a port forward for each application.”

“It is a fact that the Cisco SSL VPN Client provides more support than the Cisco WebVPN does, but in regards to features WebVPN has more features because every little bit of it has to be configured. The Cisco SSL VPN Client provides wider support with less to configure and is much more functional.”

“In conclusion, Cisco SSL VPN runs SSL over TCP, has a small impact to all traffic to determine if traffic is destined for STC client and is faster than mangled WebVPN.”

Note:

“SSL and IPSec use different protocols, but they are both secure in terms of security. SSL is easy to deploy as compared to IPSec. Imagine you have 200+ users and to make them login to VPN you need to give them client software and PCF file, which is not required in case of SSL.”

 Configuring SPAN is pretty simple. Keep in mind that there are a number of “rules” for source and destination ports. You also need to understand how SPAN works with other protocols, such as STP, VTP, and CDP. I recommend reading the Cisco IOS documentation listed below before you begin.

Here’s an example for configuring SPAN. Let’s say we want to mirror all traffic going to and from the first 23 Ethernet ports on a 24-port switch. Then we want to send copies of all that traffic to port 24 for protocol analysis. Here’s what we would do:

Switch(config)# monitor session 1 source interface FastEthernet 0/1 -  23 both
Switch(config)# monitor session 1 destination interface FastEthernet0/24

  Continue reading Configure Cisco RSPAN

 With the various features that some switches now include, nearly a minute is sometimes necessary before a switch begins to service a newly connected workstation. This delay affects the workstation every time you turn on or reboot the workstation. The four main features that cause this delay are:

• Spanning Tree Protocol (STP)
• EtherChannel negotiation
• Trunking negotiation
• Link speed/duplex negotiation between the switch and the workstation Continue reading Switch Delay Factors