All About Networking.

How to use VPCS with GNS3 in Ubuntu.

noreply@blogger.com (ÇrashÖverride) — Fri, 14 Jan 2011 12:25:00 +0000

1.Download vpcs from here VPCS 0.20a

2.Extract and look for vpcs32.linux(for 32-bit systems) and vpcs64.linux (for 64-bit systems)

3.Fire up the Terminal and issue following command
chmod +x vpcs32.linux

4.Then we'll open and configure startup.vpc in gedit

gedit startup.vpc

5.Now configure startup.vpc according to your requirement. For example I'll add just two hosts for this tutorial.
Host 1 (VPCS1) with Ip 192.168.1.10/24 and 192.168.1.99 as its gateway.
Host 2 (VPCS2) with Ip 192.168.1.11/24 and 192.168.1.99 as its gateway.

** add # to the rest of the lines.

6.Now lets start VPCS by issuing the following command within the terminal.
./vpcs32.linux

7.Use show command to see all the configured ip addresses.

8. We are done with VPCS configuration part, minimize the vpcs window, and lets configure port settings for VPCS on GNS3.

Fire up GNS3 (run gns3 as a root).

9.This is a optional step where I'll be adding symbols to PC hosts.

10.Add computer symbol from 'available symbol' to 'customized nodes'
   on name = anyname ie, PC1
   on type = Cloud
   click ok
Do the same for PC2

11.Drag and Drop PC1 and PC2 into the GNS3 Workboard.
    Double click on PC1
   click on 'C1'
   go to tab 'NIO UDP'
   hold....
    go back to Step 7
    Check the LPORT and RPORT

12.On Local port add rport value
   on Remote port add lport value
   on Remote host add 127.0.0.1
   click add
    Do the same for PC2 (again check the respective ports)

13. Lets add a Ethernet switch to the GNS3 workboard and check the connectivity between the two hosts.

14. Maximize vpcs window and lets ping to each host to check the connectivity between them.
To navigate from 1 pc to another, simply type the number

As you see, a successful connectivity has been established between the two hosts.

Happy Learning :)

Configure Terminal Server

noreply@blogger.com (ÇrashÖverride) — Fri, 08 Oct 2010 17:34:00 +0000

1. Configure an IP address on the ethernet interface
cisco(config)# int fa0/0
cisco(config-if)# ip add 192.168.1.50 255.255.255.0
cisco(config-if)# no shut

2. Create a loopback interface
cisco(config)# int lo0
cisco(config-if)# ip add 1.1.1.1 255.0.0.0

3. Configure the line based on the “show line” output.
* If enabled, the port will be accessible through the network on TCP port 20xx where xx is the TTY of the port on the router
cisco(config)# line 1 16
cisco(config-line)# no exec //unwanted signals from the attached device do not launch.
cisco(config-line)# exec-timeout 0 0 //disable the line timeout period
cisco(config-line)# logging synchronous
cisco(config-line)# transport input all

4. Configure default route
cisco(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.1
cisco(config)# ip default-gateway 192.168.1.1
// ip default-gateway is configured as well in case routing is not enabled. E.g. the terminal server is in ROMMON mode as a result of a bad reboot after power outage.

5. Enable telnet line
cisco(config)# line vty 0 4
cisco(config-line)# password cisco
cisco(config-line)# login

6. Configure host and line mapping
*e.g. Router A is connected to line 1
cisco(config)# ip host RouterA 2001 1.1.1.1

Enable SSH in Switch and Router

noreply@blogger.com (ÇrashÖverride) — Fri, 08 Oct 2010 17:29:00 +0000

Assuming the IP address, enable password and default route are in place, the additional steps needed are as follows:

1. Configure a domain name
cisco(config)# ip domain-name cisco.com

2. Configure the RSA key generation for encryption
cisco(config)# crypto key generate rsa
* it may prompt user for the key length generated in the range of 360 to 2048. Default is 512-bit.

3. Configure authentication method
a) Using local database
cisco(config)# username cisco password cisco

OR

b) Using Radius server
cisco(config)# aaa new-model
cisco(config)# aaa authentication login Radius_Server group radius
cisco(config)# radius-server host 192.168.1.155

4. Configure the terminal line
cisco(config)# line vty 0 4
cisco(config-line)# login local // using local database

OR

cisco(config-line)# login authentication Radius_Server //using radius server
cisco(config-line)# transport input ssh

Subnet Chart:Internet Protocol (IPv4)

noreply@blogger.com (ÇrashÖverride) — Wed, 06 Oct 2010 07:01:00 +0000

This is an Internet Protocol (IPv4) Subnet Chart. You can use this to quickly look up how you might need to subnet your network. At the bottom there is a quick how-to on calculating subnets.

For more information on subnetting, see RFC 1817 and RFC 1812.

Class address ranges:

Class A = 1.0.0.0 to 126.0.0.0

Class B = 128.0.0.0 to 191.255.0.0

Class C = 192.0.1.0 to 223.255.255.0

Reserved address ranges for private (non-routed) use (see RFC 1918):

10.0.0.0 -> 10.255.255.255

172.16.0.0 -> 172.31.255.255

192.168.0.0 -> 192.168.255.255

Other reserved addresses:

127.0.0.0 is reserved for loopback and IPC on the local host

224.0.0.0 -> 239.255.255.255 is reserved for multicast addresses

Chart notes:

Number of Subnets - "( )" Refers to the number of effective subnets, since the use of subnet numbers of all 0s or all 1s is highly frowned upon and RFC non-compliant.

Number of Hosts - Refers to the number of effective hosts, excluding the network and broadcast address.

Class A

Network Bits	Subnet Mask	Number of Subnets	Number of Hosts
/8	255.0.0.0	0	16777214
/9	255.128.0.0	2 (0)	8388606
/10	255.192.0.0	4 (2)	4194302
/11	255.224.0.0	8 (6)	2097150
/12	255.240.0.0	16 (14)	1048574
/13	255.248.0.0	32 (30)	524286
/14	255.252.0.0	64 (62)	262142
/15	255.254.0.0	128 (126)	131070
/16	255.255.0.0	256 (254)	65534
/17	255.255.128.0	512 (510)	32766
/18	255.255.192.0	1024 (1022)	16382
/19	255.255.224.0	2048 (2046)	8190
/20	255.255.240.0	4096 (4094)	4094
/21	255.255.248.0	8192 (8190)	2046
/22	255.255.252.0	16384 (16382)	1022
/23	255.255.254.0	32768 (32766)	510
/24	255.255.255.0	65536 (65534)	254
/25	255.255.255.128	131072 (131070)	126
/26	255.255.255.192	262144 (262142)	62
/27	255.255.255.224	524288 (524286)	30
/28	255.255.255.240	1048576 (1048574)	14
/29	255.255.255.248	2097152 (2097150)	6
/30	255.255.255.252	4194304 (4194302)	2

Class B

Network Bits	Subnet Mask	Number of Subnets	Number of Hosts
/16	255.255.0.0	0	65534
/17	255.255.128.0	2 (0)	32766
/18	255.255.192.0	4 (2)	16382
/19	255.255.224.0	8 (6)	8190
/20	255.255.240.0	16 (14)	4094
/21	255.255.248.0	32 (30)	2046
/22	255.255.252.0	64 (62)	1022
/23	255.255.254.0	128 (126)	510
/24	255.255.255.0	256 (254)	254
/25	255.255.255.128	512 (510)	126
/26	255.255.255.192	1024 (1022)	62
/27	255.255.255.224	2048 (2046)	30
/28	255.255.255.240	4096 (4094)	14
/29	255.255.255.248	8192 (8190)	6
/30	255.255.255.252	16384 (16382)	2

Class C

Network Bits	Subnet Mask	Number of Subnets	Number of Hosts
/24	255.255.255.0	0	254
/25	255.255.255.128	2 (0)	126
/26	255.255.255.192	4 (2)	62
/27	255.255.255.224	8 (6)	30
/28	255.255.255.240	16 (14)	14
/29	255.255.255.248	32 (30)	6
/30	255.255.255.252	64 (62)	2

Supernetting (CIDR) Chart

CIDR - Classless Inter-Domain Routing.

Note: The Number of Class C networks must be contiguous.
For example, 192.169.1.0/22 represents the following block of addresses:
192.169.1.0, 192.169.2.0, 192.169.3.0 and 192.169.4.0.

Class C

CIDR Block	Supernet Mask	Number of Class C Addresses	Number of Hosts
/14	255.252.0.0	1024	262144
/15	255.254.0.0	512	131072
/16	255.255.0.0	256	65536
/17	255.255.128.0	128	32768
/18	255.255.192.0	64	16384
/19	255.255.224.0	32	8192
/20	255.255.240.0	16	4096
/21	255.255.248.0	8	2048
/22	255.255.252.0	4	1024
/23	255.255.254.0	2	512

Quick Subnetting How-To

[Understanding decimal - Base 10]

The first thing you must know is that the common number system used world wide is the decimal system (otherwise known as base 10). What makes the decimal system a base 10 system is that it is based on grouping numbers by 10's. It is believed that the system evolved because we have ten fingers and ten toes which over the years we have used for counting. I use mine all the time (grin). We name the ten digits: zero, one, two, three, four, five, six, seven, eight and nine.

The decimal system has a 1's place, a 10's place, a 100's place, a 1000's place and so on. We say the number places are grouped by 10's because multiplying each number place by 10 gives you the next number place. So: 1x10=10 (the 10's place), 10x10=100 (the 100's place), 100x10=1000 (the 1000's place) etc.

Let's look at the decimal number 103 by place.

103 <- read from right to left

We have a 3 in the 1's place
We have a 0in the 10's place
We have a 1 in the 100's place

Thus: 100+0+3=103

By now you probably feel like you have attended Kindergarten for the second time in your life? Sorry about that but it is very important that you understand the concept of what a number system is, and what it is based on before we look at binary.

[Understanding binary - base 2]

Binary is a base 2 system, and thus groups numbers by 2's and not by 10's like the decimal system. We name the two digits: zero and one. The binary system has a 1's place, a 2's place, a 4's place, an 8's place, a 16's place and so on. We say the number places are grouped by 2's because multiplying each number place by 2 gives you the next number place. So: 1x2=2 (the 2's place), 2x2=4 (the 4's place), 4x2=8 (the 8's place), 8x2=16 (the 16's place) etc.

Let's look at the decimal number Let's look at the decimal number 103 in binary format:

01100111 <- read from right to left

We have a 1 in the 1's place
We have a 1 in the 2's place
We have a 1 in the 4's place
We have a 0 in the 8's place
We have a 0 in the 16's place
We have a 1 in the 32's place
We have a 1 in the 64's place
We have a 0 in the 128's place

Thus: 0+64+32+0+0+4+2+1=103

Okay, Let's test your skills. Here is a list of binary numbers, try converting them to decimal and check your answers at the end of this post.

10000000
11000000
11100000
01000000
10000011
10010001
11111111

If you were able to convert these numbers to decimal then congratulations! You're ready to move on to the next section.

[Understanding a subnet mask]

Now that you understand what binary is, let's have a look at our two subnet masks from the beginning of my post:

192.168.1.0 / 255.255.255.0
192.168.1.0/24

The concept of a subnet mask is simple. You have a network and you have hosts on the network (anything with an IP address is a host). The subnet mask determines what portion of the TCP/IP address represents your network and what portion can be used for your hosts. Because I am a simple person, I think of it like this; The network number represents the street I live on, and the host portion is used for the numbers on all the houses on my street.

A subnet mask of 255.255.255.0 means that the first three octets of the address will be used for the network, and thus our network number is 192.168.1. This means we can have 254 computers on this network, because the fourth octet is not being used by the network portion of the address. We know this because of the 0 in the subnet mask (255.255.255.0).

We call each of the number sections an octet because we think of them in binary, and there are eight possible bits in each section. Eight bits is an octet. 11111111 in binary is 255 in decimal (did you do the conversions?). So our decimal subnet mask 255.255.255.0 displayed in binary is going to be:

11111111.11111111.11111111.00000000

If you count all the ones, you will find that there are 24 of them. Now look at the subnet mask examples again.

192.168.1.0/255.255.255.0
192.168.1.0/24

Do you see why both subnet masks are the same? The number 24 is the number of bits used in the network portion of the address, and is short-hand for writing the address/subnet mask combination. It becomes important to understand this when you start dividing your network into multiple sub networks.

[Understanding Subnetting]

Before reading this section, you should have a good understanding of what a subnet mask is and how binary bits represent the subnet mask.

Simply put, subnetting is dividing your network into multiple sub networks. To go back to my silly example about houses and streets, subnetting gives you multiple streets in your neighborhood.

There are two methods for dividing your network into multiple sub networks; One is to simply change your network numbers keeping the same subnet mask. The other is to subnet your network into smaller sub networks.

Keeping the same mask:
Your network could be divided into two or more networks by changing the network portion of the address such as 192.168.1 and 192.168.2 and keeping the same subnet mask.

Example:
192.168.1.0/255.255.255.0
192.168.2.0/255.255.255.0

Doing this would give you two separate networks with 254 hosts per network. This is a very common method of dealing with multiple networks. However, back in the good old days you had to pay for every IP address you used, and if you had 25 computers on your network you probably would not want to pay for 254 addresses! The answer to the problem is...subnetting.

Subnetting a network:
Subnetting is when you use bits from the host portion of your address as part of your network number. This let's you subdivide your network at the cost of host addresses, which is great if you're paying for every host IP address. It will save you money because you pay for fewer TCP/IP addresses. Confused? Here is where understanding binary is important.

Lets look at a new subnet mask:
255.255.255.224

As you can see in the fourth octet, some of the host portion of this subnet mask is now being used for part of the network address. Which means we are now using some of the binary bits in the fourth octet for our network numbers, and that gives us fewer hosts than our old mask (which gave us 254), but gives us more networks (which is why we call it subnetting).

How can we tell how many networks and hosts per network this new subnet mask will give us? Well... we shall have to use some of our newly acquired binary skills.

The first task is to find out how many bits in the fourth octet are being used? The decimal number is 224, what is the decimal number 224 as represented in binary?

The decimal number 224 in binary is:
11100000

We have a 0 in the 1's place
We have a 0 in the 2's place
We have a 0 in the 4's place
We have a 0 in the 8's place
We have a 0 in the 16's place
We have a 1 in the 32's place
We have a 1 in the 64's place
We have a 1 in the 128's place

Thus: 128+64+32+0+0+0+0+0=224

So our complete subnet mask in binary is:
1111111.11111111.11111111.11100000

We now know that three bits from the fourth octet are used. How can we tell how many sub networks we're going to have? This requires some math- sorry. The formula is: 2ⁿ-2, where n is the number of bits being used from the host portion of our subnet mask.

Note: We subtract 2 from the total because you do not count all 0's or all 1's.

The formula for three bits is:
2³-2=6

In simpler terms:
(2x2x2)-2=6

So our network is sub divided into 6 networks. Next, we want to know what the network numbers are, and how many hosts we can have on each of the 6 networks?

What is the first subnet? Let's have a look at the bits in our fourth octet again. The bit that gives us the answer is the (1) closest to the first zero, and in this case it is the 3rd bit from the left.

11100000

The 3rd bit will start our first network, and the 3rd bit is in the 32's place (remember binary). Start adding the value 32 to itself six times to get the six network numbers.

Note: A quicker way to find our starting network number is to subtract our mask from 256.
256-224=32

Here are our network numbers:

32
64
96
128
160
192

A better way to display this is:

192.168.1.32
192.168.1.64
192.168.1.96
192.168.1.128
192.168.1.160
192.168.1.192

The host addresses will fall between the network numbers, so we will have 30 hosts per network. You're probably wondering why it's not 31? The answer is that the last address of each subnet is used as the broadcast address for that subnet.

Example:
Subnet:192.168.1.32 / 255.255.255.224
Address Range: 192.168.1.33 through 192.168.1.62 (30 hosts)
Subnet Broadcast Address:192.168.1.63

Quiz:
Let's test your skills- write the address range and broadcast address for the following subnet. You will find the answer at the end of this post.

Subnet: 192.168.1.128 / 255.255.255.224
Address Range?
Subnet Broadcast Address?

If we we're paying for our TCP/IP addresses, we would only pay for one network and host combination, thus paying for 30 hosts and not 254. It could mean some real savings, it also frees up the remaining addresses for other organizations to use.

Let's look at another subnet mask:
255.255.255.240

How many bits are used from the host portion? To find this out, we need to know how the decimal number 240 is represented in binary.

The answer is:
11110000

So four bits are taken from the host portion of our mask. We do the same math as before:

2⁴-2=14

In simpler terms:
(2x2x2x2)-2=14

We will have 14 sub networks, and what will the network numbers be? Look at the fourth bit, it's in the 16's place:
11110000

Note: A quicker way to find our starting network number is to subtract the value of our mask from 256. So: 256-240=16

Start adding 16 to itself- fourteen times to get all 14 network numbers:

16
32
48
64
80
96
112
128
144
160
176
192
208
224

A better way to display our subnets is:

192.168.1.16
192.168.1.32
192.168.1.48
192.168.1.64
192.168.1.80
192.168.1.96
192.168.1.112
192.168.1.128
192.168.1.144
192.168.1.160
192.168.1.176
192.168.1.192
192.168.1.208
192.168.1.224

The host addresses fall between the network numbers. So we will have 14 host addresses on each of our 14 sub networks (remember: the last or 15th address is the broadcast address for that subnet).

If you had a small company with 10 hosts and needed to have a static IP address for all of your hosts, you would be assigned a network/subnet mask and a valid IP address range.

Here is an example of what that might look like:

Network: 205.112.10.16/.255.255.255.240
Address Range: 205.112.10.17 through 205.112.10.30
Subnet Broadcast Address: 205.112.10.31

[Answers to Binary Conversions]

10000000 = 128
11000000 = 192
11100000 = 224
01000000 = 64
10000011 = 131
10010001 = 145
11111111 = 255

[Answer to Subnet Question]

Subnet:192.168.1.128 / 255.255.255.224
Address Range: 192.168.1.129 through 192.168.1.158
Subnet Broadcast Address: 192.168.1.159

Add GUI QEMU Host in GNS3

noreply@blogger.com (ÇrashÖverride) — Tue, 05 Oct 2010 10:01:00 +0000

Today I’ll show you how to add graphical host in GNS3 using Qemu. We’ll be using tinycore which is based on Linux 2.6 kernel, Busybox, Tiny X, and Fltk. Tiny Core includes ssh, iptables, iproute, tcpdump and IPv6 support. It is quite well integrated and doesn't require much tuning. This is a graphical version of Microcore linux image, we used in previous tutorial Add Qemu host in GNS3 .

Download Tinycore Linux Qemu image

Tinycore Linux 2.11.5 Qemu image can be downloaded separately from here.

Setup image for Qemu host

Go to Edit | Preferences | Qemu | Qemu Host

Setup new image with following properties

Identifier: tiny_core
image: local path to linux-tinycore-2.11.5.img
Memory: 64 MB
NIC: e1000
Qemu options: -no-acpi

Press Save and just added image will appear into Qemu Host images list.

Drag Host >> Select Name >> Right Click >> Start

Watch Tinycore in Action here.

Happy Learning

Putty Connection Manager

noreply@blogger.com (ÇrashÖverride) — Sat, 02 Oct 2010 05:51:00 +0000

If you work with Cisco or Linux you are probably used to working with a terminal window. When you have several terminal windows on your desktop this might become a bit annoying when they are all scattered around the screen. Putty connection manager solves this problem! Best Part is Putty Manager can be used with GNS3.

By using Putty Connection Manager you can use tabs to keep your terminal windows under control. You can split windows horizontally or vertical and customize it exactly the way you like...very nice!

You can download putty connection manager from this website:

http://puttycm.free.fr/cms/

Cisco Routing & Switching Certifications

noreply@blogger.com (ÇrashÖverride) — Fri, 01 Oct 2010 17:14:00 +0000

Cisco offers different "tracks" when it comes to certification:

Routing & Switching
Design
Network Security
Service Provider
Service Provider Operations
Storage Networking
Voice
Wireless

Most of the tracks have 3 "levels" of certification:

CCNA (Cisco Certified Network Associate)
CCNP (Cisco Certified Network Professional)
CCIE (Cisco Certified Internetwork Expert)

The most popular track is routing & switching, most people first start with routing & switching and take on another track later on. If you are interested in configuring networks for VoIP you will need to know some routing & switching protocols, especially quality of service. Implementing security is also kind of hard if you have no idea what to secure...

On the Cisco website you will always see this pyramid when they are talking about certifications:

At the bottom you see the "entry" level, I'm skipping that one and jumping right to the "Associate" level (CCNA) because that's where most people are starting. As you can see the bottom is very width, and if you go to the professional (CCNP) and expert (CCIE) level it's narrow.This image is chosen for a reason.

CCNA

If you start with studying Cisco, you'll start with the Associate level (CCNA). There are a lot of topics and technologies that you might have never heard about, so there's a lot of studying for you to do...I believe this makes it a hard exam for newcomers. If you want to self-study for CCNA I recommend you to get this book:
CCNA: Cisco Certified Network Associate Study Guide: Exam 640-802

It covers all the topics for the exam, if you read this book a couple of times and do all the exercises...you'll have a very good basic understanding of networking. It shows you the basics of networking, switching, routing, ip, etc.

You can get the CCNA certification by doing 2 separate or a combined exam. If you do the combined exam you need to get a higher score and I only suggest doing this when you feel really confident about your networking knowledge or already have experience.

To beat Cisco exams you need to get hands-on experience. You can achieve this by buying old equipment (from eBay) and practice. This is what you will need at least:

2x Cisco 2950 Catalyst Switch. (any version will do)
2x Cisco 2610 Router with at least 1x Fast Ethernet and 1x Serial Connection.
1x Serial Console Cable (those are the famous blue Cisco cables for console connections)
1x Serial Cable
1x Serial 2 USB (in case you don't have a serial port on your PC or laptop).

If you are planning to continue studying Cisco I would suggest to buy Cisco 2550 Catalyst Switches instead of the 2950's, they are more useful for your CCNP.

It's possible to skip the routers because you can run Cisco IOS (Cisco's Operating System) on your PC or laptop by using GNS3. You can find a brief tutorial on GNS3 here.

Cisco 2610 Router

Cisco Catalyst 2950 Switch

Cisco Serial Console Cable:

Cisco Serial Cable:

CCNP

This equipment and the study guide should help you to pass your CCNA, Now if you want to continue studying your CCNP you will find that this is much easier (that's my opinion) then when you studied for your CCNA. When you started with the CCNA you had to study complete new material that you perhaps never heard or read about before, now you have a basic level of networking knowledge that you will further develop.

To achieve your CCNP certification you need to pass 3 exams:

Route (Routing)
Switch (Switching)
Tshoot (Troubleshooting)

For passing your CCNP I'd suggest to read the following books:
Routing TCP/IP Volume 1:
This book isn't special for the CCNP but covers all the interior routing protocols and is written very well, a must read for every networking professional.

Routing TCP/IP Volume 2:
Sometimes more is better and that is definitely true for Routing TCP/IP. This book is more about BGP (Border Gateway Protocol), NAT and some IPv6.

The other books you should read are the Cisco Press books that cover the exam goals:
CCNP Route:
This is the official Cisco Press book, covers everything you need to know for the "Route" exam.

CCNP Switch:
Also the official Cisco Press book about the Switch exam. Teaches you everything about switching you need to know to pass the exam.

CCNP Tshoot:
Troubleshooting networks is fun, this book will show you everything you need to know.

Besides reading books you need to increase your hands-on experience...do more labs, build networks and so on. You can do a lot of labs with routers by using the dynamips/gns3 software. Checkout my tutorials on GNS3 here.

The new Cisco exams are very "practical". This means you will get a lot of questions you cannot answer if you don't have the hands-on experience. You need to build networks...do labs, try stuff out. Just reading the books is not going to be enough!

CCIE

Now the CCIE is a completely different beast. Honestly you can't compare this to CCNA or CCNP level. To pass the CCIE you need to do a written exam and pass the lab.

How to run Linux Router Vyatta in GNS3

noreply@blogger.com (ÇrashÖverride) — Wed, 29 Sep 2010 07:41:00 +0000

What is the Vyatta ?

Vyatta is bringing innovation and affordability to the networking industry by delivering advanced routing and security in a software-based network OS that scales from the branch office to the service provider edge. Vyatta has decoupled networking software from proprietary hardware allowing users to leverage the price and performance advantages of standard x86-based hardware and components as well as Citrix XenServer and VMWare virtual or cloud environments.

http://www.vyatta.com/

In this tutorial brezular shows us how to install Vyatta 6.1 Core LiveCD on Qemu image and run it from GNS3.

1. Download Vyatta Core 6.1 LiveCD iso (You need to fill short questionnaire for Vyatta download)

Vyatta download    http://www.vyatta.com/downloads/index.php

2. Create Qemu qcow2 image

/usr/local/bin/qemu-img create -f qcow2 ./vyatta6.1vc.img 1G

3. Boot Qemu image with Vyatta 6.1 LiveCD

/usr/local/bin/qemu -boot d -hda ./vyatta6.1vc.img -cdrom ./vyatta-livecd_VC6.1-2010.08.20_i386.iso -m 512

login/password: vyatta/vyatta

4. Install Live CD

To install Live CD to Qemu image enter this command (as user vyatta)

install-system

The tutorial is opened and it walk you through installation process:

Would you like to continue? (Yes/No) [YES]: Enter

Partition (Auto/Union/Parted/Skip) [Auto]: Enter

Install the image on? [sda]: Enter

This will destroy all data on /dev/sda.
Continue? (Yes/No) [No]: Yes

How big of root partition should I create? (1000MB – 1074MB) [1074]MB: Enter

I found the following configuration files
/opt/vyatta/etc/config/config.boot
Which one should I copy to sda? [/opt/vyatta/etc/config/config.boot] Enter

Enter password for administrator account
Enter vyatta password: your_password
Retype vyatta password: your_password

Which drive should GRUB modify the boot partition on? [sda]: Enter

Done!
Now you successfully install Vyatta.

5. Adapt Vyatta NIC behavior to GNS3 Qemuwrapper

GNS3 qemuwrapper always changes MAC address of presented NIC during the boot of Qemu instance. Vyatta is programmed to save MAC address of existing ethernet interfaces. If MAC address of particular NIC is changed (by GNS3 qemuwrapper) Vyatta preserves the interface with old MAC and create new interface with new MAC.

Each time Qemu instace is restarted the number of interfaces doubled.

These are my steps how to solve it (it must be a better solution but I didn’t find any with Google search):

a) Enable root account on Vyatta 6.1

thank to Tim Peerlings blog   http://www.timpeerlings.nl/enable-root-account-on-vyatta-6-1/

vyatta$ configure
vyatta#set system login user root authentication plaintext-password test
vayata# commit
vyatta# save

exit

Now you should switch to user root:

su
Password: test

b) Remove vyatta_net_name script (root account needed)

cd /lib/udev/
mv ./vyatta_net_name ./vyatta_net_name_backup
rm ./vyatta_net_name

6. Setup serial console login

thanks to Petr’s blog    http://linux.xvx.cz/2009/08/debian-with-grub2-and-serial-connection/

This configuration redirects output to serial ttyS0 and allows you to use Console in GNS3.
Login as root with su command and modify grub configuration file:

vim /etc/default/grub

Change the lines in configuration file according to these lines

# This file is sourced by update-grub, and its variables are propagated
# to its children in /etc/grub.d/

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=”console=tty0 console=ttyS0,9600n8″

# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=serial
GRUB_SERIAL_COMMAND=”serial –speed=9600 –unit=0 –word=8 –parity=no –stop=1″

# Uncomment if you don’t want GRUB to pass “root=UUID=xxx” parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

Now update grub with command:

update-grub

7. Setup GNS3 for Vyatta qemu image

- Start GNS3
- Edit-> Preferences-> Qemu-> Qemu Host

Set your settings according to picture:

Check Kvm option only if your processor supports hardware virtualization. Check Kqemu option only if it is installed and running. If you are not sure with these options let them unchecked otherwise Qemu will be not started.

You need also set Qemu general settings like path to qemu, qemu-img and qemuwrapper.

- Edit-> Preferences-> Qemu-> General Settings

Check the picture for details:

Login to Vyatta:

login/password: vyatta/your_password

8. Conclusion

Brezular has made a video to prove functionality of Yvatta Qemu image. In this video three Vyatta Qemu instances run RIP routing protocol.

Video: RIP configuration on Vyatta box:

http://rapidshare.com/files/419301470/vyatta_on_qemu_gns3.rar.html

You can download Vyatta 6.1 Qemu image from here:

http://rapidshare.com/files/420013925/vyatta6.1vc.part1.rar
http://rapidshare.com/files/420013926/vyatta6.1vc.part2.rar

login/pass: vyatta/skuska

root account: root/skuska (Don’t use root account for router configuration)

If you use Linux and there is already non-patched Qemu installed in your distro don’t forget to patch, compile and install Qemu for udp tunnels and multicast. The great How to is here:

http://blog.gns3.net/2009/10/olive-juniper/2/

Special Thanks to Brezular for this great tutorial.

All About GNS3

noreply@blogger.com (ÇrashÖverride) — Mon, 27 Sep 2010 15:53:00 +0000

You can find some user based support on the Freenode network of IRC.

Server: irc.freenode.com

Channels:

#gns3: Focuses on support for the GNS3 product (bugs, recommendations, complaints)

#gns3-labs: Aimed to help with labs and trade topologies.. Not an official GNS3 support channel.

GNS3-Labs Facebook Page

Dynamips Tutorial: Dynagen is a front-end for use with the Dynamips Cisco router emulator

Dynamips

7200emu.hacki.at: A forum for everything GNS3, Dynamips, Dynagen and overall help.

BlindHog.net: Great website with videos, configs and files on setting up working labs with some troubleshooting and testing exercises.

BrainBump: This website is dedicated for helping those who are working towards achieving their CCIE.Personally, The author is working towards CCIE voice and this blog will help those who are pursuing Voice/Security/RS CCIE’s.

Need help installing GNS3 on Windows XP?
A new tutorial for GNS3 0.5 is available here (highly recommended for beginners). OUTDATED
Need help installing GNS3 on a Linux platform?
Video tutorials

Beginners
Internet LAB Tutorial Part 2
Installation Tutorial for Linux
How to build an Internet Lab
GNS3 Graphical router emulation software
Switching lab Part 2 (router on a stick)

Switching

Cisco Packet Tracer Video Tutorials

noreply@blogger.com (ÇrashÖverride) — Mon, 27 Sep 2010 15:36:00 +0000

English | MP4 | 1920x1080 | AVC - 1108 Kbps | AAC - 126 Kbps | 916.16 MB
Genre: Video Training

Cisco Networking Academy is a comprehensive e-learning initiative that enables students to develop valuable information and communication technology skills for increased access to opportunities in the global economy. To learn more about the program, how to get involved, career resources for students, how we are addressing the digital divide, and more. Packet Tracer is an application produced by Cisco Systems to provide a virtual simulation of real life equipment and situations.
Contains

Cisco Systems Packet Tracer
Packet Tracer OSPF
Packet Tracer Subinterfaces
Packet Tracer Video
Switch VLAN
WAN connection ADSL
CCNA 3 Ch 1 Lab Intro using Packet Tracer 5.0.mp4
Cisco Systems Packet Tracer
configuration frame relay.mp4
EIGRP,FRAME RELAY, HTTP AND DNS Packet Tracer.mp4
Frame-Relay Packet Tracer 5.2 (Cisco) Tagalog Tutorial.mp4
How to configure OSPF in Packet Tracer..mp4
How to configure RIPv2 in Packet Tracer..mp4
Multiuser Connection Packet Tracer 5.1.mp4
OSPF Authentication Lab using Packet Tracer 5.mp4
Packet Tracer - DHCP Server with IP Helper.mp4
Packet Tracer - DHCP Setup.mp4
Packet Tracer OSPF
Packet Tracer Sub interfaces
Packet Tracer Video
Packet Tracer VLANS
Static Routing using Packet Tracer 5.0.mp4
Switch Router Vlan Packet Tracer.mp4
Switch VLAN
Testing Security Policies with Packet Tracer.mp4
Tutorial Packet Tracer 5.1 Nube Fame Relay.mp4
using packet tracer Connecting to a web server using IP.avi.mp4
VTP Trunk VLAN.mp4
WAN connection ADSL
Wifi con Packet Tracer.mp4

http://hotfile.com/dl/68710663/8efd2b5/PacketTracerTutorial.part01.rar_gigatraining.net.html
http://hotfile.com/dl/68710657/a691c62/PacketTracerTutorial.part02.rar_gigatraining.net.html
http://hotfile.com/dl/68710660/26ace7c/PacketTracerTutorial.part03.rar_gigatraining.net.html
http://hotfile.com/dl/68710655/f104c16/PacketTracerTutorial.part04.rar_gigatraining.net.html
http://hotfile.com/dl/68710658/73c885f/PacketTracerTutorial.part05.rar_gigatraining.net.html
http://hotfile.com/dl/68710661/bb0f5a3/PacketTracerTutorial.part06.rar_gigatraining.net.html
http://hotfile.com/dl/68710656/b9b8886/PacketTracerTutorial.part07.rar_gigatraining.net.html
http://hotfile.com/dl/68710659/9174699/PacketTracerTutorial.part08.rar_gigatraining.net.html
http://hotfile.com/dl/68710662/a02ca42/PacketTracerTutorial.part09.rar_gigatraining.net.html
http://hotfile.com/dl/68710664/7f953f1/PacketTracerTutorial.part10.rar_gigatraining.net.html

Password default: gigatraining.net

Configure Vmware to work with GNS3.

noreply@blogger.com (ÇrashÖverride) — Mon, 27 Sep 2010 15:26:00 +0000

These are links to videos created by Timw of hacki.at. Timw is a helpful guy on the forums over there and took time to create some videos on configuring VMWare to work with Dynamips/Dynagen & GNS3. In one of the Videos he also teaches you how to setup a simple frame-relay lab.

Video 1: VMWare Server Network Setup

Setting up a virtual network in VMWare Server for use with Dynamips, Dynagen and GNS3

http://www.4shared.com/file/40989090/6e056245/VMWare_Server_Network_Setup.html

Video 2: Frame Relay

How to use GNS3 to setup a Frame relay network using 2 routers and 2 virtual machines running in VMWare Server on a local work station.

http://www.4shared.com/file/40874613/803e59ec/Frame_Relay.html

Video 3: VMWare Server Network Setup 2

Shows how to create a virtual network adapter and then connect it to a Virtual machine using VMWare Server. After that it shows how to connect the Network Adapter to a cloud in GNS3.

http://www.4shared.com/file/41078214/19a152f2/VMWare_Server_Network_Setup2.html

Video 4: Saving Configs in GNS3

How to save your router configs in GNS3.

http://www.4shared.com/file/50577485/d99a2f50/GNS3_Save_Configs.html

Labs & videos created by Timw @ 7200emu.hacki.at

How to Install Gns3 on Mac Os X

noreply@blogger.com (ÇrashÖverride) — Fri, 24 Sep 2010 13:09:00 +0000

Here are instructions to install GNS3 from the sources on Mac os X. You will have to install or compile dependencies like Qt, Sip and PyQt. This will allow you to use the latest development version of GNS3 that you can download from http://code.gns3.net.

Method 1

Install the Apple Devs Tools (on your Mac OS X DVD or download it on ADC account). Run and install XcodeTools.mpkg.

Download Python 2.6 for MacOS X and install it.

Download Qt libraries for Mac and install them.

Download SIP, open a terminal and go in the folder where you downloaded the tar file and compile using the following commands (example for SIP 4.9.3):

Macintosh:$  tar xvzf sip-4.9.3.tar.gz
Macintosh:$  cd sip-4.9.3
Macintosh:sip-4.9.3$  python configure.py
Macintosh:sip-4.9.3$  make
Macintosh:sip-4.9.3$  make install

Download PyQt and run the following commands to decompress and compile PyQt (example for PyQt 4.6.2):

Macintosh:$  tar xvzf PyQt-mac-gpl-4.6.2.tar.gz
Macintosh:$  cd PyQt-mac-gpl-4.6.2
Macintosh:PyQt-mac-gpl-4.6.2$  python configure.py
Macintosh:PyQt-mac-gpl-4.6.2$  make
Macintosh:PyQt-mac-gpl-4.6.2$  make install

Download GNS3 source from here or the development version and start the script named gns3.

Method 2

This method can take a few hours as everything is compiled but this is the most flexible as you can switch between dependencies versions very easily.

Download and install Mac Ports (you will need the Apple Devs Tools).

Open a terminal and install GNS3 dependencies.

Macintosh:$ sudo port install python26
Macintosh:$ sudo port install python_select
Macintosh:$ sudo python_select python26
Macintosh:$ sudo port install py26-sip
Macintosh:$ sudo port install py26-pyqt4
Macintosh:$ sudo port install qt4-mac

Download GNS3 source from here or the development version and start the script named gns3.

Notes about Mac Ports

Optionally, to prevent Mac Ports to install the last version of the dependencies (which may not work properly with GNS3), you can force a specified version with @.

Example:

Macintosh:$ sudo port install py26-sip @4.9.3_0
Macintosh:$ sudo port install py26-pyqt4 @4.6.2_0
Macintosh:$ sudo port install qt4-mac @4.5.3_0

Also, let say you have installed the latest version of Qt but this one doesn’t work very well with GNS3, you can revert back to your previous Qt version using the command sudo port activate qt4-mac @version_number. This will automatically deactivate the current version of Qt and activate the one you want.

2a Configure IP address

noreply@blogger.com (ÇrashÖverride) — Mon, 20 Sep 2010 07:44:00 +0000

LAB 2 (Basic IOS of Routers + Security)

Today we’ll start off with Lab 2, Which will comprise labs related to Routers, its basic commands, configuration of Ip Address, Telnet, SSH server, Serial connectivity, Static Routes and PPP on a router. We’ll start with 2a Configure IP address today.

Configure IP Address on Fast Ethernet 0/1

Router(config)#hostname R1

R1(config)#interface fastEthernet 0/1

R1(config-if)#ip address 10.0.0.10 255.0.0.0

R1(config-if)#no shutdown

R1(config-if)#exit

R1(config)#exit

R1#show ip interface brief

!!! Make sure the Connectivity is established between PC 10.0.0.1 and Router 10.0.0.10 after assigning the ip, by pinging the router from windows command prompt.

If you have any questions regarding this, please leave a comment below.

Add Qemu Host in GNS3.

noreply@blogger.com (ÇrashÖverride) — Sat, 18 Sep 2010 13:46:00 +0000

By: Jaakko Rautanen
13.8.2010
v1.1

Version history of this document:

v1.1	Added instructions for console connection
v1.0	Published

Overview

Qemu image of Microcore Linux 2.10, is small linux image ready to be used in GNS3 and which includes ssh, iptables, iproute, tcpdump and IPv6 support. It is quite well integrated and doesn't require much tuning.

Download Microcore Linux Qemu image

Microcore Linux 2.10 image can be downloaded separately from GNS3 web site.

Setup image for Qemu host

Go to Edit | Preferences | Qemu | Qemu Host
Setup new image with following properties
Identifier: MicrocoreBinary image: local path to linux-microcore-2.10.imgMemory: 64 MBNIC: e1000Qemu options: -no-acpi

Press Save and just added image will appear into Qemu Host images list

Create topology and drop Qemu host on workspace

Here is the topology used in this tutorial. One directly connected subnet between host and router and one "remote" network in the Lo0 interface of R1 so that default route can be verified.

Add devices on workspace and connect link between them. If you want to get IP-addresses on the diagram use Add a note tool for that.

Start and Configure R1

Here are configurations of R1 used in this example.

Current configuration : 946 bytes

!

upgrade fpd auto

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname R1

!

boot-start-marker

boot-end-marker

!

logging message-counter syslog

enable password cisco

!

aaa new-model

!

!

aaa authentication login SSH-LOGIN local

!

!

aaa session-id common

ip source-route

ip cef

!

!

!

!

ip domain name cisco.com

no ipv6 cef

!

multilink bundle-name authenticated

!

!

username cisco password 0 cisco

archive

log config

hidekeys

!

!

interface Loopback0

ip address 192.168.0.1 255.255.255.0

!

interface FastEthernet0/0

ip address 10.10.10.1 255.255.255.0

duplex half

!

ip forward-protocol nd

no ip http server

no ip http secure-server

!

control-plane

!

gatekeeper

shutdown

!

!

line con 0

stopbits 1

line aux 0

stopbits 1

line vty 0 4

password cisco

login authentication SSH-LOGIN

transport input telnet ssh

!

end

Remember to type crypto key generate command in config mode to get SSH enabled.

Start Qemu host and assign ip address and default gateway

Start Qemu Host by right clicking and pressing Start button Qemu window will open
Assign IP address for eth0 interface using command:

sudo su
ifconfig eth0 10.10.10.2 netmask 255.255.255.0 up

To verify what ip address eth0 interface has use following command

ifconfig eth0

You can also set hostname to host using hostname command:

hostname Qemu1

Try to reach directly connected network

Try to ping router (10.10.10.1) stop by pressing CRTL + C.

Setup default gateway to reach remote networks

Try to ping the Loopback interface of R1. It's not answering because of host doesn't know any route to it. To see routing table in linux use route command. To add default route use again route command. After adding default route towards R1 you can reach remote networks.

Using telnet and SSH

You can use Qemu host as telnet and SSH client when connection to R1 for example.

Making IP-address and default gateway persistent

By default when added using ifconfig and route commands IP-address and default gateway do not remain during reboot.

To make settings persistent do following:

sudo su
vi /opt/bootlocal.sh

Add follwing lines to the file:

hostname Qemu1
ifconfig eth0 10.10.10.2/24
route add default gw 10.10.10.1

Save file:
- Press Esc
- Type :wq!

Run following command:

/usr/bin/filetool.sh backup

Now you can reboot the router and settings will remain.

Running multiple host simultaneously

Currently you can't run multiple Microcore host simultaneuosly. GNS3 Development team is trying to resolve this issue...

Using console connection

As you might have noticed there is Qemu window appears after starting Qemu host. However, you have also option to use normal console connection with PuTTY or some other telnet application. To get this working you have to have correct Qemu image. Currently you can download one from here:

http://rapidshare.com/files/412603669/linux-microcore-2.11.5.img

Special Thanks to Jaakko Rautanen for making this tutorial .

Happy simulations using Qemu! :)

How to install a loopback interface in Linux for GNS3.

noreply@blogger.com (ÇrashÖverride) — Sat, 18 Sep 2010 13:00:00 +0000

After successful installation of GNS3, we will install loopback adapter on our Ubuntu, Centos, Redhat and Fedora systems, so that we can telnet into your routers.

Loopback tap installation on Ubuntu
user@admin-desktop:~$ sudo –i
root@ admin-desktop:~#apt-get install uml-utilities
root@ admin-desktop:~#modprobe tun
root@ admin-desktop:~#tunctl             This will create loopback interface tap0
root@ admin-desktop:~#ifconfig tap0 10.100.100.100 netmask 255.255.255.0 up
root@ admin-desktop:~#ifconfig            verify that tap0 is up and given ip is assigned.

If you want to add one more loopback interface
root@ admin-desktop:~#tunctl             This will create loopback interface tap1
root@ admin-desktop:~#ifconfig tap1 10.100.101.100 netmask 255.255.255.0 up

********************************************************************************

Loopback tap installation on Centos/Redhat/Fedora
We need tunctl which is not available in our local repositories. So we’ll have to add RPMForge repository. Steps to add this repo is given here
http://wiki.centos.org/AdditionalResources/Repositories/RPMForge (Steps are the same for other 2 distros as well)

Ok lets install tunctl

[user@admin ~]$ su
Password: (Type in your root password here)
[root@admin /]# yum install tunctl
[root@admin /]# modprobe tun
[root@admin /]# cd /usr/sbin
[root@admin sbin]#./tunctl           This will create loopback interface tap0
[root@admin sbin]# /sbin/ifconfig tap0 10.100.100.100 netmask 255.255.255.0 up
[root@admin sbin]# /sbin/ ifconfig     verify that tap0 is up and given ip is assigned.

If you want to add one more loopback interface
[root@admin sbin]#./tunctl                 This will create loopback interface tap1
[root@admin sbin]# /sbin/ifconfig tap1 10.100.101.100 netmask 255.255.255.0 up

Change the ip with ifconfig according to your requirement.

Run GNS3 with root privileges, or you won’t be able to add these tap interfaces to GNS3.
Fire up GNS3

Drag the cloud onto the work-board and right click on it, Select Configure. Then Select NIO TAP, type tap0, press Add. Click Apply & ok. Now connect it to your router.

Important: Add these lines to iptables

sudo iptables -I INPUT -j ACCEPT -i tap0
sudo iptables -I OUTPUT -j ACCEPT -o tap0

Happy Learning :)

1g Port Security

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 14:23:00 +0000

Sw1# show mac-address-table

Sw1#show port-security interface fastEthernet 0/1

!!! Configure Port Security on Fast Ethernet 0/1

Sw1(config)#interface fastEthernet 0/1

Sw1(config-if)#switchport mode access

Sw1(config-if)#switchport port-security

Sw1(config-if)#switchport port-security maximum 1

Sw1(config-if)#switchport port-security mac-address sticky

Sw1(config-if)#switchport port-security violation shutdown

Sw1# show port-security interface fastEthernet 0/1

Sw1#show mac-address-table

Sw1#show port-security address

Sw1# show ip interface fastEthernet 0/1

!!! After changing the PC on Fast Ethernet 0/1

Sw1#show port-security

Sw1#show port-security interface fastEthernet 0/1

Sw1# show ip interface fastEthernet 0/1

We are done with our LAB 1.

Hope this was helpful to you guys. Please leave a comment.

1h Configure VLAN & assign interface

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 13:52:00 +0000

Create VLAN and Assign a Port to that VLAN

!!! Switch port 1 is a Part of Vlan 10 and Switch port 2 is a part of Vlan 20

Sw1(config)#vlan 10

Sw1(config)#name cisco

Sw1(config)#exit

Sw1(config)#vlan 20

Sw1(config)#name linux

Sw1(config)#exit

Sw1(config)#interface fastEthernet 0/1

Sw1(config-if)#switchport access vlan 10

Sw1(config)#interface fastEthernet 0/2

Sw1(config-if)#switchport access vlan 20

Sw1#show vlan brief

After assigning each port to a different Vlan. 10.0.0.1 and 10.0.0.2 won’t be able to ping each other.

Next Lab 1g Port Security

1f Switch Static IP address Configuration

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 13:35:00 +0000

!!! To manage Telnet, SSH Session on a Switch we need IP address

!!! Enter Vlan1 Configuration Mode

Sw1(config)#interface vlan1

Sw1(config-if)#ip address 10.0.0.10 255.0.0.0

Sw1(config-if)#no shutdown

Sw1(config-if)#exit

Sw1(config)#ip default-gateway 10.0.0.100

Verify Command’s

Sw1# show running-config

Sw1# show ip interface vlan1

Sw1# show ip interface brief

Sw1# copy running-config startup-config

Lets Verify SSH Session

!!! Fire up Putty and enter the ip address of Switch and Select SSH as Protocol

!!! Enter Username and Password to authentication

Sw1(config)#show line

!!! “*“ shows that one VTY Session is active

Sw1#show vlan

!!! By Default all ports are member of Vlan 1

The connectivity is established between all ports because they are in the same Vlan.

Next Lab 1h Configure VLAN & assign interface

1e SSH Configuration

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 13:06:00 +0000

!!! Create a Local User Name

Sw1(config)#username naresh password cisco

!!! Assign a Domain Name

Sw1(config)#ip domain-name cisco.com

!!! Next we’ll generate encryption keys

Sw1(config)#crypto key generate rsa

Sw1(config)#line vty 0 15

Sw1(config-line)#password cisco

Sw1(config-line)#login local

!!! Configure vty ports for using SSH

Sw1(config-line)#transport input telnet ssh

Verify Command’s

Sw1#show crypto key mypubkey rsa

Next Lab 1f Switch Static IP address Configuration

1d Configure Banner

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 12:51:00 +0000

How to Set Banner

Sw1(config)#banner login # Welcome #

Verify the Banner

Sw1(config)#exit

Sw1#exit

Welcome

User Access Verification

Username:naresh

Password:

Sw1>enable

Password:

Sw1#

Next Lab 1e SSH Configuration

1c Telnet Password

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 08:23:00 +0000

How to Set Telnet Password

Sw1#configure terminal

Sw1(config)#line vty 0 15

Sw1(config-line)#password cisco

Sw1(config-line)#login

Sw1(config-line)#exit

!!! Encrypt Telnet password by

Sw1(config)#service password-encryption

Sw1(config)#exit

Sw1#copy running-config startup-config

Next Lab 1d Configure Banner

1b User Authentication

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 08:09:00 +0000

Sw1#configure terminal
Sw1(config)#line console 0
Sw1(config-line)# login local
Sw1(config-line)#exit
Sw1(config)#username naresh password cisco

Verify the Authentication

Sw1(config)#exit
Sw1#copy running-config startup-config
Sw1#exit

Sw1 con0 is now available

Press RETURN to get started.

User Access Verification

Username:naresh
Password:

Sw1>enable
Password:

Verify the User Status

!!! This command will show active user connected to console port.

Sw1#show users

Next Lab 1c Telnet Password

1a Configure Basic Password and Hostname

noreply@blogger.com (ÇrashÖverride) — Thu, 16 Sep 2010 07:41:00 +0000

We'll start off with LAB 1 (Basic IOS of Switches + Security)

Instruction’s Before LAB

Before Configuration on Switch the Connectivity is established between PC 10.0.0.1 and PC 10.0.0.2.

A terminal is connected to console port.

Erase the entire configuration.

Putty Software is used to manage the SSH Session.

If you don't have real cisco switches, you can practice this labs on Gns3 network emulator. Get it from here.

Please note that Gns3 does not emulate switch. But you can configure cisco router image to run as a swich. The c3640-ik9o3s-mz.124-18.bin ios image supports most of the switch commands. Google 4 it or leave a comment below with your e-mail id and I'll e-mail the link of ios image asap.

1a Configure Basic Password and Hostname

Switch>enable

Switch# configure terminal

How to Set Hostname and Configure Console Password

The Switch’s Host Name is used for local identification.

Switch(config)# hostname Sw1

Then set password for Console login.

Sw1(config)#line console 0

Sw1(config-line)#password cisco123

Sw1(config-line)#login

How to Set Privilege Level password

The enable password controls access to privilege mode.

!!! Clear Text Password not encrypted(less secure)

Sw1(config)#enable password ccna

You can securely encrypt the enable password, by using the enable secret command.

!!! Encrypted Password (more secure)

Sw1(config)#enable secret ccna123

IMP: If you set the password for both (enable password and enable secret), the password set for enable secret is used.

Verify the Password

Sw1(config)#exit

Sw1#exit

Sw1 con0 is now available

Press RETURN to get started.

User Access Verification

!!! TYPE HERE LINE CONSOLE Password

Password:

Sw1>enable

If you have set password for enable secret, then

!!! TYPE HERE Privilege Level Password

Password:

Next Lab 1b User Authentication

CCNA LAB GUIDE

noreply@blogger.com (ÇrashÖverride) — Wed, 15 Sep 2010 17:43:00 +0000

While studying for the Cisco CCNA certification, I couldn’t find any lab guides out there to get me started. There is a ton of information of course, but not what I was looking for. So after successful completion of my CCNA, I decided to make one for other CCNA aspirants.

Lab Layout

LAB 1 (Basic IOS of Switches + Security)
1a Configure Basic Password and Hostname
1b User Authentication
1c Telnet Password
1d Configure Banner
1e SSH Configuration
1f Switch Static IP address Configuration
1g Verify the SSH Session
1h Configure VLAN & assign interface
1g Port Security

LAB 2 (Basic IOS of Routers + Security)
2a Configure IP address
2b Configure Telnet & User Based Authentication
2c Configure SSH Server
2d Configure Serial Connectivity
2e Configure Static Routes
2f Configure PPP

LAB 3 (VTP and STP)
3a Configure VTP Server and Clients
3b Verify VTP
3c Configure & Verify STP

LAB 4 (Routing Protocols)
4a EIGRP
4b OSPF

LAB 5 (Security & Port Mapping)
5a Name Based Access-List
5b Static NAT, Dynamic NAT & PAT

LAB 6 (Wide Area Network)
6a Configure Hub and Spoke

LAB 7 (Inter VLAN Routing)
7a Configure Inter VLAN Routing.

LAB 8 (Configure IP v6 to IP v4 Tunnel)
8a Configure EIGRP for IPv4
8b Create 6 to 4 Tunnel
8c Configure IPv6 Static Routes

LAB 9 (Secure Device Manager)
9a How to Install SDM
9b How to configure SDM
9c Configure DHCP Server

We'll Start with Lab 1 from tomorrow. So stay tuned.

Download Packet Tracer 5.3 (deb, rpm, exe)

noreply@blogger.com (ÇrashÖverride) — Sun, 12 Sep 2010 15:42:00 +0000

New Version of Cisco Packet Tracer Available

Cisco Networking Academy is pleased to announce the release of Cisco Packet Tracer version 5.3, a minor release that includes the following new protocol support and enhanced functionality:

* Improved Linksys models, added WEP wireless security algorithm, Cable and DSL enhancements
* Call Manager Express (VOIP support)
* FTP server and routers/switches - server and client
* Email system (SMTP and POP3) - server and client
* Border Gateway Protocol (BGP) – limited implementation that allows for a more realistic representation of the Internet for scenarios
* Generic IP end devices – to create more versatility in device creation
* Activity Wizard Initial Tree enhancements – more scenario variations

The new protocol support and activity wizard enhancements in version 5.3 will enable instructors to teach concepts in CCNA Discovery, CCNA Exploration, and CCNP courses more effectively, including the following:
CCNA Discovery

* Networking for Home and Small Businesses: Improved Linksys models and wireless security protocols and algorithms, generic IP end devices
* Working at a Small-to-Medium Business or ISP: Better DNS, improved DHCP, wireless security, new FTP, SMTP, POP3
* Introducing Routing and Switching in the Enterprise: Improved multi-area OSPF, EIGRP, BGP
* Designing and Supporting Computer Networks: New VOIP, Call Manager Express

CCNA Exploration

* Network Fundamentals: Improved HTTP, DNS, DHCP; new FTP, SMTP, POP3
* Routing Protocols and Concepts: Improved multi-area OSPF, EIGRP, new BGP
* LAN Switching and Wireless: Improved Linksys models, wireless security algorithms, 802.11
* Accessing the WAN: New PPPoE, enhanced IPSec, Cable and DSL enhancements

CCNP

* Improved multiarea OSPF, EIGRP, new BGP

We recommend upgrading to the new version to take advantage of the many improvements included in this release. To learn more about how Packet Tracer can be used in each Networking Academy course, please view this new Packet Tracer 5.3 Curricula Support chart.
Packet Tracer 5.3 is currently available for download from the Packet Tracer resource pageon Academy Connection. To access this page, log in to Academy Connection and click the Cisco Packet Tracer graphic on the left of the page, select Software Downloads, then select the appropriate download package for your needs. The previous version of Packet Tracer, version 5.2.1.8, will continue to be available for download.
Packet Tracer 5.3 supports activities authored in Packet Tracer 5.0, 5.1, and 5.2.x. All activities included in IT Essentials: PC Hardware and Software, CCNA Discovery, CCNA Exploration, and CCNA Security are also fully compatible with Packet Tracer 5.3. Please note that activities authored or saved with Packet Tracer 5.3 can only be used with the version 5.3 software.

For more information, please review the Packet Tracer 5.3 FAQs and the updated resources available on the Packet Tracer resource page on Academy Connection.

LINKS:
Fedora, Red Hat, Centos (RPM)

http://hotfile.com/dl/40549184/2644bf6/PacketTracer53_(fedora)i386_installer-rpm.rar.html

Ubuntu, Debian and Others (DEB)

http://hotfile.com/dl/40549555/ccb91cb/PacketTracer53_i386_installer-deb.rar.html

Windows Xp, Vista, 7  (EXE)

http://hotfile.com/dl/40547663/974d1a5/PacketTracer53_setup.rar.html

All About Networking.

How to use VPCS with GNS3 in Ubuntu.

Configure Terminal Server

Enable SSH in Switch and Router

Subnet Chart:Internet Protocol (IPv4)

Add GUI QEMU Host in GNS3

Setup image for Qemu host

Putty Connection Manager

Cisco Routing & Switching Certifications

CCNA

Cisco 2610 Router

Cisco Catalyst 2950 Switch

Cisco Serial Console Cable:

Cisco Serial Cable:

CCNP

CCIE

How to run Linux Router Vyatta in GNS3

All About GNS3

Video tutorials

Beginners

Switching

Voice

Misc

Cisco Packet Tracer Video Tutorials

Configure Vmware to work with GNS3.

How to Install Gns3 on Mac Os X

Method 1

Method 2

Notes about Mac Ports

2a Configure IP address

Add Qemu Host in GNS3.

Overview

Download Microcore Linux Qemu image

Setup image for Qemu host

Create topology and drop Qemu host on workspace

Start and Configure R1

Start Qemu host and assign ip address and default gateway

Try to reach directly connected network

Setup default gateway to reach remote networks

Using telnet and SSH

Making IP-address and default gateway persistent

Running multiple host simultaneously

Using console connection

How to install a loopback interface in Linux for GNS3.

1g Port Security

1h Configure VLAN & assign interface

1f Switch Static IP address Configuration

1e SSH Configuration

1d Configure Banner

1c Telnet Password

1b User Authentication

1a Configure Basic Password and Hostname

CCNA LAB GUIDE

Download Packet Tracer 5.3 (deb, rpm, exe)