IPsec VPN Lab, with stateful failover (SSO, Dual Interface Model)

Lots of stuff going on here.
We have two sites for our company named Central-Office and Branch-33.

The CO is connected to our ISP w/ two edge routers, CE_1 w/ an E3 line and CE_2 w/ a backup E1 line. Our branch33 site is using R4, which will establish the IPSec tunnels, allowing the private networks 10.1.33.0/21 talk to the central office 10.1.8.0/21 networks.

Behing them are the two IPSec Concentrators (R1 and R2, 7200 Cisco routers) which have public IP addresses on their out facing interfaces. Here all 4 routers connected to a switch, but of course in a production network you would have redundant switches there also.

Two first hop redundancy plans are integrated as an HSRP group facing to our internal network and the HSRP group facing to our edge routers, which also provides the IPsec redundandcy.

Crypto maps are setup as SSO stateful failover, R1 acting as the primary IPsec point, with R2 being the standby.

There is an extra flavor as IP SLA and reachability tracking is done where R1 and R2 are checking their next-hop routers to the outside world, CE_1 & CE_2. No routing protocol is run inside our company, for claritys sake. Thus we have two static default routes w/ different AD and the mentioned icmp tracking.

One Note, considering the Stateful Failover: "Each time an active device relinquishes control to become the standby device, the active device will reload. This functionality ensures that the state of the new standby device synchronizes correctly with the new active device." (Ref) So since Dynamips doesnt support reloading, the Router dynamips process will crash and you must shut down and turn on the router again to get it going.

Download Project files for GNS3

Links:
Cisco High Availability Solution: Stateful Failover for IPsec
Fun with IPsec stateful failover @ packetlife

GRE over IPsec in a Hub-Spoke Topology w/ EIGRP (Lab) #2

Ok this is the enhanced version of the previous GRE lab I've posted.
We've decided to encrypt and secure all communications between our HQ and Branches.
As previously noted we needed GRE to run a dynamic routing protocol (EIGRP) between our networks. So here we implement an IPsec GRE tunnel that will encrypt all traffic including the multicast EIGRP messaging.

Download Project files for GNS3.

GRE Tunnels in a Hub-Spoke Topology w/ EIGRP (Lab) #1

Our company DasBoot Corp. has opened a few offices in Turkey.
The corporate offices are in sunny Izmir and there is one branch in Istanbul, and two in Ankara.

They all have basic Internet connectivity to our trusted ISP: DynamiteBBS. Which by the way is running IS-IS in its backbone with MPLS on top.

As the Network engineer of DasBoot, we decide to create tunnels in a hub-spoke fashion, connecting our branches to the corporate network. We use private addressing in our network (eg. 172.16.0.0). Here's a demonstration of running EIGRP to facilitate full connectivity between our networks. I know not too complicated but good practice and extensible lab anyways. Enjoy..
(Download GNS3 Project files)

GRE Tunnel w/ IPsec protection, (and ISAKMP association using RSA keys)

1. Generate an RSA Public Key for our router.

#crypto key generate rsa general-keys label R1

Here you can see the generated key. Do the above for also R2, and copy paste their public keys to each other in next step.

#sh crypto key mypubkey rsa
% Key pair was generated at: 12:35:34 UTC Jan 24 2010
Key name: R1
Usage: General Purpose Key
Key is not exportable.
Key Data:
305C300D 06092A86 4886F70D 01010105 00034B00 30480241 00D35594 62FB3925
22EBD28E A64B12A7 2D0D44C1 DD28F9BF 8BA52834 516FC231 F1791352 A90ADEE0
A61E77C7 5F132B9E 11193B08 B338D531 D40EE40D 9699E742 DF020301 0001
% Key pair was generated at: 13:35:36 UTC Jan 24 2010
Key name: R1.server
Usage: Encryption Key
Key is not exportable.
Key Data:
307C300D 06092A86 4886F70D 01010105 00036B00 30680261 00A4764D E3D85AFD
2E9254C0 DBB88E08 CE86FA63 8D82C08C D11F14DF AF9264C9 2F5C1CBC 7081C66D
DFE73BB3 66E5A354 48B73EF0 3773545B F5BACBA7 CEBA55DA 4D3D52A1 0B62BFFD
BA93A21E 9B65D23F 9A843994 FAAEB67E BF565A6F 38A8DC3A D5020301 0001

2. Create a key chain. Addressed to router R2 with its IP address and copy paste its public key in here.

#crypto key pubkey-chain rsa
addressed-key 10.1.1.6
key-string
Enter a public key as a hexidecimal number ....
(PASTE HERE)
and use quit to finish

Download project files for GNS3

IPsec VPN Lab, (using Dynamic crypto Map)

In this lab we connect the 3 sites of our company using secure IPsec VPN connections.

The ISP network consists of 4 Routers which are running EIGRP between them.

Our headquarters is connected to the ISP with the CE_4 router.
The branch offices, CE_5 being Branch1, and CE_8 Branch2.

Networks are 192.168.0.0/21 behing CE_4, edge router.
In Branch 1 we have 192.168.16.0/20 networks. (Simulated with loopback int)
In Branch 2 there are the 192.168.8.0/21 networks.

This setup demonstrates all the IPsec negotiation and tunnel establishment using a dynamic map on CE_4.. The key point is the create the relationship between the static crypto map and the dynamic one.

Due to our ISAKMP Policy we are using a Pre-Shared key for authentication. Which will be defined as a wildcard, so our VPN peers can connect using whichever address they have.

# crypto isakmp key address 0.0.0.0

Here are the lab files for gns3. Download

Good Reading:
Wildcard Pre-Shared Key Enhancement @cisco
Security Commands: crypto dynamic-map through ctype @cisco

AToM (Any Transport over MPLS) Lab

So here we have a AToM (Any Transport over MPLS) Lab which is also known as a Martini Pseudowire.

Provider Core Routers R1,R2,R3,R4 serve as the label switching MPLS Core. The Provider Edge routers PE_1,PE_2 connect to Customer networks. The IGP running on the provider network is IS-IS.
We have a Customer HQ and a Branch Office which have connections to the same ISP.
A VPN Tunnel is built between the PE_1 <-> PE_2 to connect the customer private network.

GNS3 Project file @ Filefront

Collection of OSPF Labs

Here are some of the labs I've created when studying for the CCNP Exams:

1. OSPF Network w/ two areas connected to the Backbone Area 0. One of the networks being a Totally Stub Area w/ redundant connections to the backbone. Download Project Files



2. Based on project above, with an extra Area 99 added via a Virtual-Link. Download Project Files



3. Backbone Area on a Point to Multipoint Frame-Relay network. A chance to observe different ospf area types. And also the DR/BDR relations and configurations in two different areas. Download

Collection of IS-IS Labs

A collection of IS-IS labs created by me, during CCNP Studies.

1. Based around a Frame-Relay Backbone, with 3 areas and their L1/L2 routers. Download project files



2. A different and more complex topology, with Frame Relay p2p links and other good stuff thrown in. Download

VRRP Lab

A fictional company "Kasifler", has connections to two different Service Providers, Avea (Primary) and Vodafone (Secondary).

Router R4 is the PE router for Avea and depicts the Avea network, included are some loopback networks.
Router R5 is the PE router for the Vodafone network which also has loopback interfaces to simulate networks inside Vodafone, or the Internet.

Remaining routers, R0 through R3 belong the our company Kasifler. R0 is really used for a client and test bed to control reachability to the inside/from the outside.

Our primary router R1 is connected the VRRP master, R2 and R3 being backup VRRP routers. They all have their WAN interface "tracked" and in a failure situation this is the prefered fail-over : R1 -> R2 -> R3

There is also BGP peerings with our providers, becareful not to be a transit network here! (Demonstrated with some as-path route maps)

Take down interfaces from R4 -> R1 or R4 -> R2 to test the VRRP action.


Link to Project file on Filefront

GNS3 Lab w/ pfSense Firewall

Here's a lab I've been working on.
It's based on a company topology from an article on cisco.com, which has access/distribution switches with STP load-balancing between Data/Voice/Service VLANs.
I connected it to an Edge router using EIGRP inside, which then connects to a pfSense VM Appliance Firewall, which in turn connects to an ISP Router. Some good exercises to try in here, security, nat, bgp (with a second ISP connection), pppoe, etc.

PPPoE Lab w/ GNS3

This is a simple lab using a 7200 router as a PPPoE server. Which in turn is querying the Radius server. The Radius server was a VMWare pfSense appliance. This appliance is very handy for testing purposes and AFAIK is also used in production environments. Download Project Files