<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-1143005373466289397</id><updated>2012-01-17T20:19:43.932Z</updated><category term='linux'/><category term='ccip'/><category term='cisco'/><category term='bgp'/><category term='firewalls'/><category term='VSS'/><category term='switching'/><category term='frame-relay'/><category term='checkpoint'/><category term='security'/><category term='storm-control'/><category term='random'/><category term='eigrp'/><category term='ccie'/><category term='snmp'/><category term='qos'/><category term='vpn'/><category term='layer2'/><category term='gotchas'/><category term='ospf'/><category term='mpls'/><category term='osx'/><category term='spanning-tree'/><title type='text'>Sabotage Networks</title><subtitle type='html'>Yet another networking blog</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>47</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-6396987073224261567</id><published>2011-08-17T13:06:00.006+01:00</published><updated>2011-08-17T13:41:13.044+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Cisco ASA 8.4 - Global Access Lists</title><summary type='text'>Handy new feature in version 8.4 of the ASA software is the ability to do global access lists.The Cisco ASA allows security levels to be applied to interfaces, traffic is automatically allowed from a high to low security level interface but not vice versa. It's probably designed for the fairly common use case of a perimeter device between a LAN and the internet. The internet link is set to </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/6396987073224261567/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2011/08/cisco-asa-84-global-access-lists.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6396987073224261567'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6396987073224261567'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2011/08/cisco-asa-84-global-access-lists.html' title='Cisco ASA 8.4 - Global Access Lists'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-D84sRJ7wubc/Tku0a5GAFbI/AAAAAAAAANc/lgMumWvGUVA/s72-c/fw.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8933069328324648564</id><published>2011-04-13T16:17:00.029+01:00</published><updated>2011-04-14T09:10:02.891+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Evaluation Assurance Levels - EAL</title><summary type='text'>EAL stands for evaluation assurance level and is a certificate of security for IT products measured against a set of common security criteria. The main source of information on EAL levels is the common criteria portal where you can find details of approved products and information on the criteria used for the EAL certifications.Who uses it?Your average network bod may not come across EAL very </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8933069328324648564/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2011/04/evaluation-assurance-levels-eal.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8933069328324648564'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8933069328324648564'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2011/04/evaluation-assurance-levels-eal.html' title='Evaluation Assurance Levels - EAL'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-3255642289713451844</id><published>2011-02-14T13:41:00.007Z</published><updated>2011-02-14T13:55:53.146Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='frame-relay'/><category scheme='http://www.blogger.com/atom/ns#' term='qos'/><category scheme='http://www.blogger.com/atom/ns#' term='ccie'/><title type='text'>Legacy FRTS &amp; Subinterfaces</title><summary type='text'>FRTS and subinterfaces. This page follows on from the previous article on legacy FRTS configuration here and shows the default behaviour of FRTS with subinterfaces.The legacy frame-relay traffic shaping has to be enabled on a physical interface. Any subinterfaces will then inherit the configuration, which is 56kbps by default. The network is shown below:In the example below FRTS is turned on but </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/3255642289713451844/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2011/02/legacy-frts-subinterfaces.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/3255642289713451844'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/3255642289713451844'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2011/02/legacy-frts-subinterfaces.html' title='Legacy FRTS &amp; Subinterfaces'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/-4mql3dHaP_U/TVk0WlaXp_I/AAAAAAAAAKY/HYKYF1xRAIY/s72-c/FRTS-subints.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5091327157722845353</id><published>2011-02-13T15:38:00.012Z</published><updated>2011-02-13T16:04:21.250Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='frame-relay'/><category scheme='http://www.blogger.com/atom/ns#' term='qos'/><category scheme='http://www.blogger.com/atom/ns#' term='ccie'/><title type='text'>Frame Relay Traffic Shaping - Legacy Configuration</title><summary type='text'>This is a basic lab to play around with frame-relay traffic shaping, FRTS. It uses the legacy configuration method rather than MCQ. INE have a great article here describing the other options.This article assumes some knowledge of QoS terms such as CIR, Bc, Be and Tc.The lab used looks like this:I'll use the GNS3 built in frame switch to make life easier, the config is below:The basic router </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5091327157722845353/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2011/02/this-is-basic-lab-to-play-around-with.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5091327157722845353'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5091327157722845353'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2011/02/this-is-basic-lab-to-play-around-with.html' title='Frame Relay Traffic Shaping - Legacy Configuration'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-tbNZ62kYDp4/TVf7mPEapGI/AAAAAAAAAJg/k30X19CBTZM/s72-c/network.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2911976645252524966</id><published>2010-12-21T19:47:00.006Z</published><updated>2010-12-22T09:23:38.604Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Zone Based Firewall &amp; Port Forwarding</title><summary type='text'>This article covers setting up port forwarding with Cisco Zone Based Firewall (ZBF) on a typical home connection.There are a couple of steps:1 - Give your LAN host a static IP.2 - Set up NAT to handle the port forwarding3 - Set up ZBF rules to allow the traffic1 - Static IPYou can either manually configure the client or use a DHCP reserved address.DHCP reservation is a royal pain on the Cisco 800</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2911976645252524966/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/12/zone-based-firewall-port-forwarding.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2911976645252524966'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2911976645252524966'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/12/zone-based-firewall-port-forwarding.html' title='Zone Based Firewall &amp; Port Forwarding'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8081883614086381310</id><published>2010-05-27T20:36:00.003+01:00</published><updated>2010-05-27T20:49:59.602+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='gotchas'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>MST - Multiple Spanning Tree - Don't change the mappings!</title><summary type='text'>MST allows you to create spanning-tree instances and map VLANs into them.Combined with VTP version 3 means you can advertise the MST mappings automatically, as shown here.MST has the concept of regions.Whether a switch is a member of a particular region depends on three things:The configured MST region name.The configured MST revision number.The VLAN to MSTI mappings.The entire VLAN to MSTI </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8081883614086381310/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/mst-multiple-spanning-tree-dont-change.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8081883614086381310'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8081883614086381310'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/mst-multiple-spanning-tree-dont-change.html' title='MST - Multiple Spanning Tree - Don&apos;t change the mappings!'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4370132741846259582</id><published>2010-05-26T21:30:00.010+01:00</published><updated>2010-05-27T21:28:34.680+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='frame-relay'/><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='ccie'/><title type='text'>Bundling Frame Relay Links</title><summary type='text'>Frame-relay study time!There are several ways to bundle links together in frame-relay:Frame-relay Multilink - FRF.16PPP MultilinkFRF16 requires configuration all along the path, so the service provider must support it. PPP multilink can be used on any frame-relay links and doesn't require anything from the SP. Frame-relay Multilink - FRF.16I'll be using the incredibly complicated topology shown </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4370132741846259582/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/bundling-frame-relay-links.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4370132741846259582'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4370132741846259582'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/bundling-frame-relay-links.html' title='Bundling Frame Relay Links'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_Ei-JpCG-fYY/S_2F_W5bn2I/AAAAAAAAAHs/5ubucVES3y8/s72-c/R1R2-FR.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8048411821648764950</id><published>2010-05-24T19:59:00.012+01:00</published><updated>2010-05-25T21:31:13.702+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='VSS'/><title type='text'>SNMP Trap on VSS Failover</title><summary type='text'>One of the big things that Cisco VSS is missing is the ability to clearly see when it's failed over.You set up your spanking new 6500 with 10Gig supervisors, plug it into your network management, lose one of the boxes and get a few traps about routing problems. What you really want is a big in-your-face message saying "HELP ME THE VSS JUST FAILED OVER OH MY GOD THE SKY IS FALLING!!11!one" and </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8048411821648764950/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/snmp-trap-on-vss-failover.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8048411821648764950'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8048411821648764950'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/05/snmp-trap-on-vss-failover.html' title='SNMP Trap on VSS Failover'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8542718328792218654</id><published>2010-03-22T20:05:00.004Z</published><updated>2010-03-22T20:22:09.981Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><title type='text'>Basic PPPoE Lab</title><summary type='text'>Configurations below for a PPPoE lab, directly connecting two routers. This uses the new broad-band access (bba) command instead of the old VPDN ones.Client:interface Dialer1 ip address 192.168.0.10 255.255.255.0 encapsulation ppp dialer pool 1interface FastEthernet0/0 pppoe-client dial-pool-number 1Server:interface Virtual-Template1 ip address 192.168.0.1 255.255.255.0bba-group pppoe global </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8542718328792218654/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/03/basic-pppoe-lab.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8542718328792218654'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8542718328792218654'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/03/basic-pppoe-lab.html' title='Basic PPPoE Lab'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-7080347755881801367</id><published>2010-03-18T14:52:00.002Z</published><updated>2010-03-18T14:55:12.795Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Generate Strong Passwords from a Unix Box</title><summary type='text'>Works from any form of unix that has a /dev/urandom and has uuencode installed.head -n 2 /dev/urandom | uuencode -m -</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/7080347755881801367/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/03/generate-strong-passwords-from-unix-box.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7080347755881801367'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7080347755881801367'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/03/generate-strong-passwords-from-unix-box.html' title='Generate Strong Passwords from a Unix Box'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5698950874510523731</id><published>2010-02-20T11:31:00.012Z</published><updated>2010-02-20T16:08:51.398Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>IBM Blade Centers - CIGESM Configuration</title><summary type='text'>There are lots of docs from IBM explaining the blade center architecture but it's a lot of information to filter through if you're only interested in the network side.The blade center in this example holds 14 blades which are best thought of as individual physical servers. It can use the Cisco switching module called a Cisco Systems Intelligent Gigabit Ethernet Switch Module, or CIGESM. They do </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5698950874510523731/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/ibm-blade-center-architecture.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5698950874510523731'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5698950874510523731'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/ibm-blade-center-architecture.html' title='IBM Blade Centers - CIGESM Configuration'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_Ei-JpCG-fYY/S3_KRbhxvGI/AAAAAAAAAGw/5J5HySuDGoo/s72-c/IBM-bladecenter.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8690592375296209222</id><published>2010-02-17T20:03:00.007Z</published><updated>2010-02-17T20:28:03.615Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='osx'/><title type='text'>Creating a CRL for an OSX keychain CA</title><summary type='text'>OSX has a handy keychain utility that can be used to create a CA among other things. I needed a CRL generated for my keychain-created CA in order to use certificate-based VPNs on a Netscreen box.There are probably 101 ways of doing this, mine is:Make a CA structure as per /opt/local/etc/openssl/openssl.cnf(or alternately you could provide the suitable CLI options to openssl each time)</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8690592375296209222/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/creating-crl-for-osx-keychain-ca.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8690592375296209222'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8690592375296209222'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/creating-crl-for-osx-keychain-ca.html' title='Creating a CRL for an OSX keychain CA'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-9078293189349716255</id><published>2010-02-12T12:12:00.007Z</published><updated>2010-02-12T12:30:36.389Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='ccip'/><category scheme='http://www.blogger.com/atom/ns#' term='qos'/><title type='text'>ToS DSCP Mappings</title><summary type='text'>Reference table of ToS to DSCP mappings below..nobrtable br { display: none }       PHB Value   ToS Byte   String   DSCP Value       CS0   0   Routine   0       CS1   32   PRIORITY   8       AF11   40   10       AF12   48   12       AF13   56   14       CS2   64   IMMEDIATE   16       AF21   72   18       AF22   80   20       AF23   88   22       CS3   96   FLASH   24       AF31   104   26       </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/9078293189349716255/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/tos-dscp-mappings.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/9078293189349716255'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/9078293189349716255'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/tos-dscp-mappings.html' title='ToS DSCP Mappings'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-1478378136362722319</id><published>2010-02-09T12:53:00.014Z</published><updated>2010-03-12T07:57:44.987Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>VTP Version 3 and MSTP Walkthrough.</title><summary type='text'>This article assumes you are familiar with MSTP and VTP.The latest incarnation of VTP version 3 is now available on versions of IOS from 12.2(50)SE3 onwards for 3560, 3750 and 2960s.It supports distribution of two databases:VLAN Database.MSTP Vlan-to-MSTI mapping database.Other than support for extended ID VLANs the VLAN database functionality is the same as previous versions. The MST mappings </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/1478378136362722319/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/vtp-version-3-and-mstp.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1478378136362722319'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1478378136362722319'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/vtp-version-3-and-mstp.html' title='VTP Version 3 and MSTP Walkthrough.'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2397884022962497043</id><published>2010-02-06T10:32:00.013Z</published><updated>2010-02-07T09:57:59.305Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='linux'/><category scheme='http://www.blogger.com/atom/ns#' term='osx'/><title type='text'>How to get USB serial adapters working in OSX</title><summary type='text'>There are loads of cheap USB serial adapters around, the difficulty can be working out what chipset they use. The easiest way to identify them is with a Linux live-CD.Identify the chipset in LinuxYou could just install the two drivers linked below, it won't do any harm if they're the wrong ones and there probably aren't that many different USB serial chipsets around so there's a good chance it'll</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2397884022962497043/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/how-to-get-usb-serial-adapters-working.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2397884022962497043'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2397884022962497043'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/how-to-get-usb-serial-adapters-working.html' title='How to get USB serial adapters working in OSX'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/S22ZHgJN6tI/AAAAAAAAAGo/Anft_Do8iSU/s72-c/apple.jpg' height='72' width='72'/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8970615868392814770</id><published>2010-02-05T12:32:00.003Z</published><updated>2010-05-27T20:35:41.098+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>Cisco Gotchas - 1800 Virtual Ports</title><summary type='text'>This is a (very late) addition to the article here.Cisco 6500 doesn't directly limit the number of spanning-tree instances. It has limits on the number of virtual ports per line card.A virtual port is a VLAN being forwarded on a trunk. So if you have 10 VLANs and 5 active trunks with no pruning then you have 50 virtual ports.A 6500 is limited to 1800 virtual ports per line-card (with caveats, see</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8970615868392814770/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-1800-virtual-ports.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8970615868392814770'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8970615868392814770'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-1800-virtual-ports.html' title='Cisco Gotchas - 1800 Virtual Ports'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-9199028493431208930</id><published>2010-02-05T12:31:00.007Z</published><updated>2010-05-27T20:36:11.354+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='gotchas'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>Cisco Gotchas - Max VLANs and STP Instances</title><summary type='text'>Cisco switches have separate limitations on:The number of VLANs that can exist in the database.The number of Spanning-Tree Instances that can run.Cisco kit tends to use per-VLAN spanning-tree in which case the two values will be the same. To understand the problem and solution requires knowledge of the different types of spanning-tree available, this subject is huge but very briefly the types are</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/9199028493431208930/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-max-vlans-and-stp.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/9199028493431208930'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/9199028493431208930'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-max-vlans-and-stp.html' title='Cisco Gotchas - Max VLANs and STP Instances'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2872834580231921192</id><published>2010-02-05T12:14:00.004Z</published><updated>2010-02-05T12:31:23.028Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='gotchas'/><title type='text'>Cisco Gotchas - 16 Unique Standby Groups</title><summary type='text'>HSRP is configured in standby groups, each one having an identifier value in the switch configuration.The acceptable range of values is 0-255 and you can create as many as you want. Cisco don't recommended using more than 500 on a 6500 series or 64 on the 3550.There are limitations on the number of unique ID values you can assign however.Each instance is configured using the standby command:</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2872834580231921192/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-16-unique-standby-groups.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2872834580231921192'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2872834580231921192'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/cisco-gotchas-16-unique-standby-groups.html' title='Cisco Gotchas - 16 Unique Standby Groups'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5631408193974667639</id><published>2010-02-01T17:04:00.012Z</published><updated>2010-02-19T13:36:05.914Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='snmp'/><title type='text'>Configure IOS by SNMP - Password Recovery</title><summary type='text'>This is useful if you ever end up without a password for a router but you do know the SNMP read-write community values or usernames. It can save you the need to reboot a device and do a full password recovery, useful if the device is a thousand miles away and running some vital service.You can load a configuration snippet into IOS from a TFTP server, triggered over SNMP.The steps are:Warning:  </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5631408193974667639/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/configure-ios-by-snmp-password-recovery.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5631408193974667639'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5631408193974667639'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/02/configure-ios-by-snmp-password-recovery.html' title='Configure IOS by SNMP - Password Recovery'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-322801847166746073</id><published>2010-01-16T14:40:00.008Z</published><updated>2010-01-16T17:44:14.268Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='VSS'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>VSS Introduction</title><summary type='text'>VSS stands for Virtual Switching System and is a technology for use on 6500 series switches.It works in a similar way to stackwise on the 3750s, you have two physical devices that end up with a single logical management plane.In a large Cisco-style network you would have two core/distribution devices for redundancy. The network topology will typically need an active/standby topology. With </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/322801847166746073/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/vss-introduction.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/322801847166746073'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/322801847166746073'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/vss-introduction.html' title='VSS Introduction'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/S1H5P7_IBlI/AAAAAAAAAF4/FZH5u0wUixA/s72-c/VSS-classic.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-3247843738756390269</id><published>2010-01-16T12:04:00.007Z</published><updated>2010-02-09T13:17:48.124Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>3750 Stackwise Upgrades</title><summary type='text'>Upgrading a Cisco switch is very easy:Copy IOS image to the flash drive on the switch.Point the boot statement at the new image.Reboot the switch.The 3750 stack is made up of several physical devices with just a single logical management interface so Cisco has implemented the archive-sw command to make upgrading it easy. It doesn't quite work as well as it should and I wouldn't recommend using it</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/3247843738756390269/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/3750-stackwise-upgrades.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/3247843738756390269'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/3247843738756390269'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/3750-stackwise-upgrades.html' title='3750 Stackwise Upgrades'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-1066018792855970848</id><published>2010-01-11T18:24:00.005Z</published><updated>2010-01-11T21:19:28.787Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>Rapid Spanning Tree Notes</title><summary type='text'>Just been reading a bit on RSTP, there are plenty of excellent detailed resources around. Here's my summary.PDF version available hereRapid Spanning Tree - 802.1w Port Roles               Role          Description          Detailed              Root          Path to root bridge          The    port that is closest to the root bridge in terms of path cost.              Designated          </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/1066018792855970848/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/rapid-spanning-tree-notes.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1066018792855970848'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1066018792855970848'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/rapid-spanning-tree-notes.html' title='Rapid Spanning Tree Notes'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5945489074382419817</id><published>2010-01-03T01:35:00.007Z</published><updated>2010-01-03T15:25:51.965Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>DSL Firewalls and PPP Half Bridges</title><summary type='text'>A PPP Half Bridge lets you extend the public IP address of your network into the LAN. This is useful if you have a firewall that doesn't have it's own DSL modem and want to do VPNs.It's also known as DHCP spoofing.Half bridging is a hack where your DSL modem makes the PPPoA connection to your ISP and is issued a public address, then advertises that same IP back on the LAN with a very short DHCP </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5945489074382419817/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/dsl-firewalls-and-ppp-half-bridges.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5945489074382419817'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5945489074382419817'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2010/01/dsl-firewalls-and-ppp-half-bridges.html' title='DSL Firewalls and PPP Half Bridges'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_Ei-JpCG-fYY/S0CqjtYdPxI/AAAAAAAAAFY/7glgy2tAfB0/s72-c/halfbridge.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5427309515999310803</id><published>2009-12-09T19:13:00.006Z</published><updated>2009-12-09T19:26:28.240Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='ospf'/><title type='text'>OSPF Reference Bandwidth Table</title><summary type='text'>Comparison of costs that are returned for various size links when the reference bandwidth is changed.     &lt;!--    BODY,DIV,TABLE,THEAD,TBODY,TFOOT,TR,TH,TD,P { font-family:"Liberation Sans"; font-size:x-small }    --&gt;                         OSPF Interface Cost           Ref Speed    Ref BW Value    10mbit link    100mbit link    1gbit link    10gbit link          100mbit    100    10    1    1</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5427309515999310803/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/12/ospf-reference-bandwidth-table.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5427309515999310803'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5427309515999310803'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/12/ospf-reference-bandwidth-table.html' title='OSPF Reference Bandwidth Table'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-52213850287425906</id><published>2009-11-29T11:05:00.012Z</published><updated>2009-11-29T11:22:29.541Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>PPPoA Password Retrieval on Netgear DG834</title><summary type='text'>I wanted to install a new firewall on my home DSL connection recently, nothing against the Netgear as it works great, but I had a Juniper box that I wanted to try out. The UK uses PPPoA for home DSL connections so you need a username and password to get onto the network.The DG834 has a web interface for management, Netgear's own FAQ has help with retrieving that password if you've lost it. Once </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/52213850287425906/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/11/pppoa-password-retrieval-on-netgear.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/52213850287425906'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/52213850287425906'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/11/pppoa-password-retrieval-on-netgear.html' title='PPPoA Password Retrieval on Netgear DG834'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/SxJZa_zT2WI/AAAAAAAAAFQ/fAwa90YPci0/s72-c/Screenshot-NETGEAR+Router+-+Mozilla+Firefox.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5812022912518592367</id><published>2009-10-31T10:34:00.007Z</published><updated>2009-10-31T10:58:17.980Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='linux'/><title type='text'>Fixing VirtualBox VRMMRO.r0 Error on Ubuntu</title><summary type='text'>I'd just rebuilt my eeepc recently and decided to install Virtualbox. Unfortunately after installing it from the Ubuntu repository it didn't quite work, giving the error "Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND)".From googling around it quickly became apparent that there's an easy fix, to uncomment a single line in a Makefile and re-compile the Virtualbox kernel modules. Unfortunately the </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5812022912518592367/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/fixing-virtualbox-vrmmror0-error-on.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5812022912518592367'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5812022912518592367'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/fixing-virtualbox-vrmmror0-error-on.html' title='Fixing VirtualBox VRMMRO.r0 Error on Ubuntu'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5337488433774374609</id><published>2009-10-23T19:13:00.005+01:00</published><updated>2010-02-09T13:20:47.619Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>ASA Site-to-Site VPN Using Certificates from OpenSSL</title><summary type='text'>To provide increased security over pre-shared keys you can authenticate VPN endpoints using certificates. Ideally this would be using a full PKI solution but a simpler method is available if you don't need revocation.This guide is for the Cisco ASA. As with most things it's a doddle in the ASDM because you can take full advantage of the GUI and be prompted for each step, however I'll show the CLI</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5337488433774374609/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/asa-site-to-site-vpn-using-certificates.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5337488433774374609'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5337488433774374609'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/asa-site-to-site-vpn-using-certificates.html' title='ASA Site-to-Site VPN Using Certificates from OpenSSL'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4844491146966083184</id><published>2009-10-23T17:08:00.008+01:00</published><updated>2009-10-23T18:13:25.938+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>OpenSSL CA for VPN Certificates</title><summary type='text'>The aim of this article is to provide some pointers to getting a certificate authority (CA) up and running with OpenSSL and provide a few handy commands for reference. This will be used in some future articles about certificate based VPNs.To do certificate based VPNs you need a couple of things:A Certificate Authority (CA) that your end devices trust.Host certificates signed by the CA.I'll use </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4844491146966083184/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/openssl-ca-for-vpn-certificates.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4844491146966083184'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4844491146966083184'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/openssl-ca-for-vpn-certificates.html' title='OpenSSL CA for VPN Certificates'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-6072962877867201047</id><published>2009-10-19T19:15:00.003+01:00</published><updated>2009-10-19T19:30:29.641+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><title type='text'>Checkpoint Traffic Sniffing</title><summary type='text'>There are a couple of handy commands for sniffing traffic on Checkpoint.Tcpdump and fw monitor.The following runs a tcpdump capture on IPSO, snagging the entire packet to a file:tcpdump -s1700 -w output.cap -ni &lt;interface&gt; host &lt;IP-addr&gt;Without the -s1700 it'll just grab the first part of each packet and not the full contents. If you're running it on a newer platform (e.g. SPLAT) then you can </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/6072962877867201047/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/checkpoint-traffic-sniffing.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6072962877867201047'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6072962877867201047'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/10/checkpoint-traffic-sniffing.html' title='Checkpoint Traffic Sniffing'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-6856005126545297420</id><published>2009-09-28T19:59:00.004+01:00</published><updated>2010-02-09T13:25:51.532Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='eigrp'/><category scheme='http://www.blogger.com/atom/ns#' term='ccip'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><title type='text'>MPLS: EIGRP as CE-PE Routing Protocol</title><summary type='text'>Following the OSPF sham links and OSPF as PE-CE routing protocol articles, this entry shows how to use EIGRP as the PE-CE routing protocol.The network topology is as before.EIGRP is fairly easy to configure in this case. The CE router is just configured as per a vanilla EIGRP network with no special entries needed, on router CE1:CE1#show ip int brief | inc upFastEthernet0/0            10.0.255.1</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/6856005126545297420/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-eigrp-as-ce-pe-routing-protocol.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6856005126545297420'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6856005126545297420'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-eigrp-as-ce-pe-routing-protocol.html' title='MPLS: EIGRP as CE-PE Routing Protocol'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-6160964142376683391</id><published>2009-09-19T09:38:00.007+01:00</published><updated>2009-09-19T10:14:56.531+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ccip'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='ospf'/><title type='text'>OSPF Sham Links</title><summary type='text'>If you install a backup link between sites in an MPLS VPN then you can run into problems as shown below.This article follows on from OSPF as a PE-CE routing protocol and uses the same network layout.I've set everything into area 0 to simplify things a bit, however there is now a serial link between the two customer sites. Topology is shown below:Before the link is brought up the routing table on </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/6160964142376683391/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/ospf-sham-links.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6160964142376683391'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/6160964142376683391'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/ospf-sham-links.html' title='OSPF Sham Links'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_Ei-JpCG-fYY/SrSY9HVan-I/AAAAAAAAAEY/NxBK52XW5-w/s72-c/lab1-ospfareas-shamlink.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-7251826366512512503</id><published>2009-09-19T08:34:00.008+01:00</published><updated>2009-09-19T09:27:47.953+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ccip'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='bgp'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><category scheme='http://www.blogger.com/atom/ns#' term='ospf'/><title type='text'>MPLS: OSPF as PE-CE Routing Protocol</title><summary type='text'>This article shows a basic configuration for using OSPF as the PE-CE routing protocol. It follows on from the basic VRFs entry and uses the same network topology, with a couple of networks added to represent each sites internal LAN.OSPF uses a hierarchical network structure where normally all areas would be connected directly to area 0. In the case of MPLS VPNs, there is always a redistribution </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/7251826366512512503/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-ospf-as-pe-ce-routing-protocol.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7251826366512512503'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7251826366512512503'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-ospf-as-pe-ce-routing-protocol.html' title='MPLS: OSPF as PE-CE Routing Protocol'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/SrSNZOlorFI/AAAAAAAAAEE/NtYu0gCOgkk/s72-c/lab1-ospfareas.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2223182226803694566</id><published>2009-09-09T20:20:00.007+01:00</published><updated>2009-09-09T20:57:06.214+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='ccip'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='bgp'/><title type='text'>MPLS Lab #3 -Simple VRFs</title><summary type='text'>This follows on from the previous article part 2.In this article I'll get the customer sites connected up in a very simple VRF.The first step is to create a VRF for the customer sites to use. This is done by naming it on each PE router, assigning a route distinguisher (RD) and setting route targets (RT) for BGP to use. The simplest way to do this is to allocate the RD in the format AS:nn where AS</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2223182226803694566/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-3-simple-vrfs.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2223182226803694566'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2223182226803694566'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-3-simple-vrfs.html' title='MPLS Lab #3 -Simple VRFs'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_Ei-JpCG-fYY/SqgHsr0MCvI/AAAAAAAAAD4/uq1a-lSYkUM/s72-c/lab1-vpnv4.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-8905685271041405552</id><published>2009-09-09T17:20:00.004+01:00</published><updated>2009-09-09T17:48:02.164+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><title type='text'>Minimal Downtime Checkpoint Upgrade</title><summary type='text'>This is an old process I worked out for an R55-&gt;R65 upgrade on a Nokia VRRP cluster to provide minimal downtime. In lab tests this worked with under a second of lost packets. In reality I wouldn't bet on a busy cluster being upgraded without losing traffic under any circumstances!My preferred method is to wipe everything completely and re-build from config backups rather than try to do software </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/8905685271041405552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/minimal-downtime-checkpoint-upgrade.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8905685271041405552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/8905685271041405552'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/minimal-downtime-checkpoint-upgrade.html' title='Minimal Downtime Checkpoint Upgrade'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-1239976153407934026</id><published>2009-09-09T17:03:00.004+01:00</published><updated>2009-09-09T19:47:20.983+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><title type='text'>Useful Checkpoint Commands</title><summary type='text'>Some useful Checkpoint commands for reference:fw unloadlocal - Unload the local policy.fw stat - Show the policy version that is currently installed.fw log - Show the log file.fw ver - Show the installed Checkpoint version.fw lslogs - List all log files available.fw logswitch - Force a log cycle.cp_conf sic state - Show SIC (secure internal comms) status.cp_conf ha enable/disable - Enable/Disable</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/1239976153407934026/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/useful-checkpoint-commands.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1239976153407934026'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/1239976153407934026'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/useful-checkpoint-commands.html' title='Useful Checkpoint Commands'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2542171002250095140</id><published>2009-09-06T21:31:00.007+01:00</published><updated>2009-09-09T20:19:34.728+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='bgp'/><title type='text'>MPLS Lab Part 2</title><summary type='text'>Follows on from part 1.Now to get MP-BGP up and running on the MPLS lab. BGP-4 (as described in RFC 1771) can only carry IPv4 prefixes. RFC 2858 adds multiprotocol capability to BGP-4, which is needed to work with the vpnv4 routes that MPLS uses.vpnv4?In an MPLS network you may have customers with overlapping IP address space. In order to provide unique addressing, a vpnv4 prefix is used </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2542171002250095140/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-part-2.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2542171002250095140'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2542171002250095140'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-part-2.html' title='MPLS Lab Part 2'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_Ei-JpCG-fYY/Sqf_Pnq-fSI/AAAAAAAAADo/XQV67cM3QJE/s72-c/SP-overview.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-7616357989323206676</id><published>2009-09-06T21:30:00.006+01:00</published><updated>2009-09-09T20:01:35.747+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='mpls'/><category scheme='http://www.blogger.com/atom/ns#' term='ospf'/><title type='text'>MPLS Lab Part 1</title><summary type='text'>I'm currently studying MPLS for the CCIP qualification so will be putting up a series of articles on building a basic service-provider network to test various MPLS configurations.The first article puts together a simple WAN running OSPF.The network will look as below:(These diagrams are all created using the excellent open source software dia)The idea here is simply to get the provider part of </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/7616357989323206676/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-part-1.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7616357989323206676'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/7616357989323206676'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/09/mpls-lab-part-1.html' title='MPLS Lab Part 1'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_Ei-JpCG-fYY/SqQdvObpZdI/AAAAAAAAADg/1U-Y6vFSSUU/s72-c/lab1.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2345062703261719335</id><published>2009-08-24T19:13:00.009+01:00</published><updated>2009-09-06T11:10:39.850+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><title type='text'>Checkpoint Software Blade Architecture</title><summary type='text'>I received an email this morning from Checkpoint advertising their new software blade architecture.Checkpoint already provide a hardware virtualization platform in the VSX-1, so could this be a blade-center version? No, the blades here are not actual blades in the sense that the rest of the industry uses the term, they are infact software modules.So what is it?It's a "new" architecture to </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2345062703261719335/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/08/checkpoint-software-blade-architecture.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2345062703261719335'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2345062703261719335'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/08/checkpoint-software-blade-architecture.html' title='Checkpoint Software Blade Architecture'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-5111194123335191912</id><published>2009-07-03T21:31:00.005+01:00</published><updated>2009-09-05T11:32:28.201+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='random'/><title type='text'>Caribbean?</title><summary type='text'>The image below comes from a beach on the west coast of Scotland, taken while visiting one of my clients sites recently.A slight departure from the technical nature of this site, but you've got to stop and enjoy moments like this when they occur:</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/5111194123335191912/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/07/caribbean.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5111194123335191912'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/5111194123335191912'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/07/caribbean.html' title='Caribbean?'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/Sk5tlF0ioOI/AAAAAAAAADI/_JmGVQxPmT8/s72-c/east_kilbride.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4337872939660683960</id><published>2009-06-22T19:01:00.010+01:00</published><updated>2009-09-05T11:32:55.770+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>Locating a host</title><summary type='text'>Something that often comes in handy is the ability to physically locate hosts on a large campus network from their IP address. This article assumes the device is correctly configured on the network.The steps are:Find the devices MAC address.Locate the STP root bridge.On the root bridge follow the path to the MAC address.1. Find the devices MAC address.The MAC address can be found in the ARP cache</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4337872939660683960/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/locating-host.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4337872939660683960'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4337872939660683960'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/locating-host.html' title='Locating a host'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2814536681581587450</id><published>2009-06-22T17:55:00.011+01:00</published><updated>2009-11-09T17:14:58.528Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='snmp'/><title type='text'>SNMPv3 in CiscoWorks</title><summary type='text'>A brief article on how I've got SNMPv3 working in older versions of CiscoWorks. This follows on from the SNMPv3 intro.Ciscoworks only allows you to associate a single SNMP user account with each device. The same SNMP user account is used to poll the device and receive traps.The new version of Device Fault Manager apparently has full SNMPv3 support. The older ones don't seem to, but they support </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2814536681581587450/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/snmpv3-in-ciscoworks.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2814536681581587450'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2814536681581587450'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/snmpv3-in-ciscoworks.html' title='SNMPv3 in CiscoWorks'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-276747461064820677</id><published>2009-06-22T17:46:00.007+01:00</published><updated>2009-09-05T11:34:13.252+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='snmp'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>SNMPv3</title><summary type='text'>Quick article on SNMP version 3, focused on Cisco kit.Previous versions of SNMP were configured using community strings and single-line commands in IOS.SNMPv3 management is more like user/account management and the configuration does not appear in "show run" but is instead hidden in the private config. You access SNMPv3 configuration information via "show snmp x" commands.SNMPv3 </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/276747461064820677/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/snmpv3.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/276747461064820677'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/276747461064820677'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/snmpv3.html' title='SNMPv3'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4605424859676291785</id><published>2009-06-08T18:42:00.015+01:00</published><updated>2009-09-05T11:34:47.065+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Checkpoint to Cisco VPNs #2</title><summary type='text'>This is part 2 of the article started here. I'll be creating traditional mode VPN rules, because they are less abstracted than VPN communities and a bit easier to understand (in my opinion). There are some complications*.To follow a similar methodology to that used on the Cisco router, the steps are as follows:Define the ISAKMP (phase 1) policy.Define the IPsec (phase 2) policy.Create the </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4605424859676291785/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/checkpoint-to-cisco-vpns-2.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4605424859676291785'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4605424859676291785'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/06/checkpoint-to-cisco-vpns-2.html' title='Checkpoint to Cisco VPNs #2'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_Ei-JpCG-fYY/Si1PSZlElcI/AAAAAAAAACg/_jv0MXmOqJ8/s72-c/cp-cisco-phase1.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4402249169235604635</id><published>2009-05-24T21:57:00.009+01:00</published><updated>2009-09-05T11:35:09.855+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='checkpoint'/><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='firewalls'/><category scheme='http://www.blogger.com/atom/ns#' term='vpn'/><title type='text'>Checkpoint to Cisco VPNs #1</title><summary type='text'>Article #1 - Intro &amp; Cisco Setup.To show some of the finer points of Checkpoint VPNs I'll rig up a test lab with a site-to-site VPN linking a Cisco IOS router and a Checkpoint R65 splat box.This article is not intended to be a general VPN introduction, rather the specifics of Checkpoint/Cisco interaction.The network will look like this:The local end is using 10.0.0.0/24, the Smart Center sits in </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4402249169235604635/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/checkpoint-to-cisco-vpns-1.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4402249169235604635'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4402249169235604635'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/checkpoint-to-cisco-vpns-1.html' title='Checkpoint to Cisco VPNs #1'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_Ei-JpCG-fYY/Shm1W2juGII/AAAAAAAAACQ/8Ff1g4O5Y8M/s72-c/checkpoint-map.png' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4474635613220641663</id><published>2009-05-19T19:17:00.007+01:00</published><updated>2009-09-05T11:35:39.028+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='spanning-tree'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><title type='text'>BDPU Guard Vs Filter</title><summary type='text'>Spanning-tree BPDU Guard or BPDU Filter?A question that has cropped up on more than one occasion is which of these options should be used? BPDU Guard or BPDU filter?You may think it safest to use both, however that isn't the case.BPDU GuardThe port is error disabled when a BPDU is received.BPDU FilterIf the port receives BPDUs then portfast is disabled and it functions as a normal STP port.You </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4474635613220641663/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/bdpu-guard-vs-filter.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4474635613220641663'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4474635613220641663'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/bdpu-guard-vs-filter.html' title='BDPU Guard Vs Filter'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_Ei-JpCG-fYY/ShL9jQOx71I/AAAAAAAAABw/xdJW9J_1mVo/s72-c/bridgingloop.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-2830751114938594737</id><published>2009-05-19T18:47:00.012+01:00</published><updated>2009-09-05T11:36:04.372+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Secure Switchport Template</title><summary type='text'>There are several reasons why you might want to use a switch port template.Make life easier for administrators.Standardize configuration.Allow people without specific Cisco knowledge to configure ports.Increase security.An example template in macro form:macro name accessportswitchport mode accessswitchport nonegotiateswitchport access vlan 99no cdp enablespanning-tree portfastspanning-tree </summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/2830751114938594737/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/secure-switchport-template.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2830751114938594737'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/2830751114938594737'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/secure-switchport-template.html' title='Secure Switchport Template'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-1143005373466289397.post-4624620759122287888</id><published>2009-05-19T17:17:00.006+01:00</published><updated>2009-09-05T11:36:23.413+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='layer2'/><category scheme='http://www.blogger.com/atom/ns#' term='switching'/><category scheme='http://www.blogger.com/atom/ns#' term='storm-control'/><title type='text'>Storm Control</title><summary type='text'>Storm-control is a very useful command for all switch-ports which allows you to set limits for Broadcast and Multicast traffic. When those limits are exceeded, traffic of that type is blocked on the interface until the storm has passed.The configuration for the storm control level as a percentage of the link size is:storm-control {broadcast|multicast} level {level} [level-low]You can also set the</summary><link rel='replies' type='application/atom+xml' href='http://sabotage-networks.blogspot.com/feeds/4624620759122287888/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/storm-control.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4624620759122287888'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1143005373466289397/posts/default/4624620759122287888'/><link rel='alternate' type='text/html' href='http://sabotage-networks.blogspot.com/2009/05/storm-control.html' title='Storm Control'/><author><name>Matt Bennett</name><uri>http://www.blogger.com/profile/17975039074220496861</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
