Tuesday, September 4, 2012

POLICING


policy-map rate-limit
class class-default
police 1000000 8000 exceed-action drop

int gi1/0/3
service-policy input rate-limit
service-policy output rate-limit

That should limit inbound and outbound at 1Mb

Monday, July 16, 2012

802.1x

Take everything one step at a time. 802.1x is EAP. You can choose to use either PEAP or EAP-TLS which PEAP is most widely used and simpler to implement. The only difference between PEAP and EAP-TLS, is to make it simple, PEAP only requires a certificate on the radius server. EAP-TLS requires a certificate on the radius server and each client device. PEAP you can authenticate via AD username or password or machine authentication, NOT BOTH! Machine authentication will require you to make sure these devices are joined to the domain. If you have devices you don't have on the domain and those devices need to also be on the wireless, then use PEAP. EAP-TLS requires devices to have a certificate and these devices have to be joined to the domain or you will need to manually add the certificate into the device. Again, if you want to use your CA and authenticate users via Active Directory, its easier to go with PEAP and that is what you should start out with first. If you can get PEAP to work with AD, then play around and get PEAP using machine authentication to work and the EAP-TLS.

Wednesday, June 27, 2012

cisco 2504

http://www.cisco.com/en/US/products/ps11630/products_tech_note09186a0080b8450c.shtml

Tuesday, June 26, 2012

Neflow on Router

interface GigabitEthernet0/1
ip address <Interface IP Address>
ip route-cache flow
!
ip flow-export source GigabitEthernet0/1
ip flow-export version 5
ip flow-export destination <Solarwinds Server IP> 2055

Friday, June 15, 2012

Wednesday, May 30, 2012

port forwarding via router

ip nat inside source static tcp <internal ip> <port> <public ip> <port>

Friday, April 6, 2012

Friday, February 24, 2012

guest vlan

You would create a vlan on the 4500 for your wireless guest (ex. vlan 998). Do not create an svi interface you do not want this routing. You then assign an access port to vlan 998 and connect your adsl router. If your router is providing dhcp, then let that do dhcp. You will need to allow vlan 998 on the wlc trunk port. The wlc will need an ip address also on vlan 998. If the adsl router doesn't provide dhcp the have the wlc do that. If the adsl does provide dhcp, then make sure the ISP excludes the wlc ip address.

With no vlan 998 layer 3 interface, there is routing between your guest and internal. You can create a vlan acl also.

Wednesday, February 22, 2012

cisco qlm

http://www.cisco.com/web/learning/le31/le29/configuring_asa_pix_security_appliances.html

Saturday, February 4, 2012

CCNP Security FIREWALL Official Certification Guide

http://www.wupload.com/file/2657510587/CCNP_Security_FIREWALL_642-617_Official_Cert_Guide.pdf

Sunday, January 15, 2012

Links

http://windowshell.wordpress.com/2011/01/04/a-sample-802-1x-configuration-guide/
https://supportforums.cisco.com/message/3535209