Hi
folks!! Sorry, I have been away for some time. Let me share with you my problem
and my ‘thinkable’ solutions. Am trying to nail a networking job and interviews
have not been forthcoming.
MY
THINKABLE SOLUTION! Am getting myself involved in a little Microsoft Server and
Linux stuffs. Hopefully that would get me the job.
Let’s
get to business. I would be using gns3 for my simulation which is available
online. I also would be using vpcs to do my clients’ ping.
STATIC
ROUTING
I have
already created some configurations which I call default. This is what I do so
I can easily rush back to my topology anytime I need to get going. So my advice
is perform some basic configurations and save it to your start-up configs.IT
DEFINETLY MAKES YOUR WORK EASIER.
Default
{Hostnames, IP addresses}
The loopback addresses are 1.1.1.1, 2.2.2.2 and 3.3.3.3 for R1, R2 and R3 respectively. This would be acting like connected interfaces to the routers.
The loopback addresses are 1.1.1.1, 2.2.2.2 and 3.3.3.3 for R1, R2 and R3 respectively. This would be acting like connected interfaces to the routers.
TASK:
Ø
Configure
static routing in the topology so the routers can ping each other. Use ip route
*network* *ip add* method for R1 and R2. Use ip route *network* *int* for R3
Ø
Remove
the static route in R3 and use a default route instead
SYNTAX
IS
#ip
route ‘THE NETWORK I WANT TO REACH’ ‘THE SUBNET MASK OF THE NETWORK I WOULD LIKE TO REACH’
‘MY NEXT HOP ADDRESS i.e. THE ADDRESS OF MY
NEIGHBOUR THAT ALLOWS ME REACH THIS NETWORK’ OR
#ip
route ‘THE NETWORK I WANT TO REACH’ ‘THE SUBNET MASK OF THE NETWORK I WOULD LIKE TO REACH’
‘INT OF MY ROUTER THAT ALLOWS ME TO REACH THIS
ADDRESS’
R1(config)#ip
route 10.10.10.0 255.255.255.0 192.168.10.2
R1(config)#ip route 2.2.2.2 255.255.255.255 192.168.10.2
R1(config)#ip route 3.3.3.3 255.255.255.255 192.168.10.2
R1(config)#ip route 2.2.2.2 255.255.255.255 192.168.10.2
R1(config)#ip route 3.3.3.3 255.255.255.255 192.168.10.2
When we configured static route to 10.10.10.0
network only, we could ping 10.10.10.2 network successfully since r2 can reach
the interface it was sent from i.e. 192.168.10.1
..but if we ping 10.10.10.1 it won’t be
succesful since r3 can’t reach the ip of the sending ping (192.168.10.1).Also
note that if we do #ping 10.10.10.2
source lo 0.The ping would be unsuccessful since r2 can’t reach the source of
the PING
R2(config)#ip
route 1.1.1.1 255.255.255.255 192.168.10.1
R2(config)#ip route 3.3.3.3 255.255.255.255 10.10.10.1
R2(config)#ip route 3.3.3.3 255.255.255.255 10.10.10.1
R3(config)#ip route 2.2.2.2 255.255.255.255 s0/0
R3(config)#ip route 192.168.10.0 255.255.255.0 s0/0
R3(config)#ip route 1.1.1.1 255.255.255.255 s0/0
Results:
A show ip route would display the results of our connected network. I would
only display that of R1..Also run pings from all the Routers..e.g R1#ping
3.3.3.3
R1#sh ip
route
Gateway
of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
C 1.1.1.1 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
S 2.2.2.2 [1/0] via 192.168.10.2
S 2.2.2.2 [1/0] via 192.168.10.2
3.0.0.0/32 is subnetted, 1 subnets
S 3.3.3.3 [1/0] via 192.168.10.2
S 3.3.3.3 [1/0] via 192.168.10.2
C 192.168.10.0/24 is directly connected,
FastEthernet0/1
10.0.0.0/24 is subnetted, 1 subnets
S 10.10.10.0 [1/0] via 192.168.10.2….FIGURE OUT WHAT EACH LINE MEANS!!! 10.10.10.0 is the network, 1 is the Default Administrative Distance of Static Routing (AD).192.168.10.2 is the next hop to reach 10.10.10.0 network.
S 10.10.10.0 [1/0] via 192.168.10.2….FIGURE OUT WHAT EACH LINE MEANS!!! 10.10.10.0 is the network, 1 is the Default Administrative Distance of Static Routing (AD).192.168.10.2 is the next hop to reach 10.10.10.0 network.
NOTES
1.
CMD
ON R1 #ip route 10.10.10.0 255.255.255.0 192.168.10.2
OUTPUT
GENERATED WITH #sh ip route
10.0.0.0/24
is subnetted, 1 subnets
S 10.10.10.0 [1/0] via 192.168.10.2
2.
CMD
ON R3 #ip route 192.168.10.0 255.255.255.0 s0/0
OUTPUT
GENERATED WITH #sh ip route
S
192.168.10.0/24 is directly connected, Serial0/0
10.0.0.0/24
is subnetted, 1 subnets
C
10.10.10.0 is directly connected, Serial0/0
Compare the
two. One is static and one is directly connected. What separates them is just
the C and S...I LOVE CISCO
PROBLEM 2
R3(config)#no
ip route 2.2.2.2 255.255.255.255 s0/0
R3(config)#no ip route 192.168.10.0 255.255.255.0 s0/0
R3(config)#no ip route 1.1.1.1 255.255.255.255 s0/0
R3(config)#ip route 0.0.0.0 0.0.0.0 s0/0…………….MEANING I WILL FORWARD ANY NETWORK ADDRESS I DON’T KNOW VIA MY s0/0 INTERFACE
R3(config)#no ip route 192.168.10.0 255.255.255.0 s0/0
R3(config)#no ip route 1.1.1.1 255.255.255.255 s0/0
R3(config)#ip route 0.0.0.0 0.0.0.0 s0/0…………….MEANING I WILL FORWARD ANY NETWORK ADDRESS I DON’T KNOW VIA MY s0/0 INTERFACE
R3#sh ip
route
Gateway of last resort is 0.0.0.0 to
network 0.0.0.0…………DID
U SEE THAT
3.0.0.0/32
is subnetted, 1 subnets
C 3.3.3.3 is directly connected, Loopback0
C 3.3.3.3 is directly connected, Loopback0
10.0.0.0/24
is subnetted, 1 subnets
C 10.10.10.0 is directly connected, Serial0/0
C 10.10.10.0 is directly connected, Serial0/0
S*
0.0.0.0/0 is directly connected, Serial0/0………………….NOW YOU SEE THAT
RUN A
PING FROM ALL THE ROUTERS AND CHECK THEIR SUCCESS RATE
NOW AM
GOING TO MAKE YOU SNEEZE A LITTLE!!!ASSUMING WE HAVENT CFGED (my shortcut to
configured) STATIC ROUTING AT ALL
Ø
WITHOUT
ROUTING,IF R1 LO 0 PINGS 10.10.10.2 (#ping 10.10.10.2 source lo 0),IT WILLL
FAIL SINCE R1 DOES NOT HAVE A ROUTE FOR IT IN ITS ROUTING TABLE
Ø
BUT
IF WE CFG A DEFAULT ROUTE VIA ITS F0/1 INT, THE PING WLD SUCCED SINCE R1 WLD B
SENDING IT VIA ITS FAST ETHENET ADD AND NOT ITS LOOPBACK.
Ø
IF
WE DO A PING WITH SOURCE LO 0, D PING WLD FAIL.NOT THAT IT WONT GET TO R2, BUT
R2 WOULDN’T KNOW WAT TO DO WITH IT
!!!!I HOPE I HAVE SCORED A LITTLE POINT..ITS GONNA
BE FUN ALL THROUGH.AND PRAY I GET A JOB FAST THOUGH…..!!!AM OUT!!!