EL5373

INTERNET ARCHITECTURE AND PROTOCOLS

DIEGO LIRA
0501296
dlira01@students.poly.edu

Workstation: AGNI
MAC: 00:04:75:B5:20:B5

Lab Report 4
Due March 20, 2013

Exercise 1
PING initiated from my computer:
35
41.374728
seq=8/2048, ttl=64

128.238.63.102 128.238.62.101 ICMP

42

Echo (ping) request id=0xca28,

Ethernet II, Src: 3Com_b5:20:b5 (00:04:75:b5:20:b5), Dst: Cisco_76:4a:3f (00:00:0c:76:4a:3f)

Internet Protocol Version 4, Src: 128.238.63.102 (128.238.63.102), Dst: 128.238.62.101 (128.238.62.101)
The ETHERNET source for the Echo request was AGNI and the destination was ROUTER 2. The IP source
for the Echo request was AGNI and the destination was VAYU.
36
41.375376
seq=8/2048, ttl=63

128.238.62.101 128.238.63.102 ICMP

60

Echo (ping) reply id=0xca28,

Ethernet II, Src: Cisco_76:4a:3f (00:00:0c:76:4a:3f), Dst: 3Com_b5:20:b5 (00:04:75:b5:20:b5)

Internet Protocol Version 4, Src: 128.238.62.101 (128.238.62.101), Dst: 128.238.63.102 (128.238.63.102)
The ETHERNET source for the Echo reply was ROUTER 2 and the destination was AGNI. The IP source was
VAYU and the destination was AGNI.

PING initiated from my partners computer:

1
0.000000
seq=1/256, ttl=63

128.238.62.101 128.238.63.102 ICMP

60

Echo (ping) request id=0x6341,

Ethernet II, Src: Cisco_76:4a:3f (00:00:0c:76:4a:3f), Dst: 3Com_b5:20:b5 (00:04:75:b5:20:b5)

Internet Protocol Version 4, Src: 128.238.62.101 (128.238.62.101), Dst: 128.238.63.102 (128.238.63.102)
The ETHERNET source for the Echo request was ROUTER 2 and the destination was AGNI. The IP source
for the Echo request was VAYU and the destination was AGNI.

2
0.000031
seq=1/256, ttl=64

128.238.63.102 128.238.62.101 ICMP

42

Echo (ping) reply id=0x6341,

Ethernet II, Src: 3Com_b5:20:b5 (00:04:75:b5:20:b5), Dst: Cisco_76:4a:3f (00:00:0c:76:4a:3f)

Internet Protocol Version 4, Src: 128.238.63.102 (128.238.63.102), Dst: 128.238.62.101 (128.238.62.101)
The ETHERNET source for the Echo reply was AGNI and the destination was ROUTER 2. The IP source was
AGNI and the destination was VAYU.
2

Delay: [(41.375376 - 41.374728) - 0.000031]/2 = [0.000648 - 0.000031]/2 = 0.000617/2 = 0.0003085

This is more than for the bridge, since the router has more processing functions (match the address in
the routing table).
We can see that the addresses change on the Ethernet layer when we send messages to another subnet,
as they must pass by the router, but the IP address (final destination) remains the same.

Exercise 2
1

0.000000

128.238.63.2

255.255.255.255

RIPv1 86

Response

3.125920

128.238.63.3

255.255.255.255

RIPv1 86

Response

The network segment is directly connect to 2 routers, so they forward only 2 RIP messages.

The Ethernet frame encapsulates the IP frame, IP encapsulates UDP, and the RIP information is the
innermost.

Ethernet frame:
Destination
Address

Source
Address

Frame
Type

Data

CRC

Destination: Broadcast (ff:ff:ff:ff:ff:ff)

Source: Cisco_76:4a:3f (00:00:0c:76:4a:3f) ROUTER 2
Type: IP (0x0800)

IP frame:
Version

Hdr Len

Differentiated
Services

Identification
Time to Live

Total Length
Flags

Protocol

Fragment Offset
Header Checksum

Source IP Address
Destination IP Address
Options (if any, <= 40 bytes)

Data

Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable
Transport))
Total Length: 72
Identification: 0x0000 (0)
Flags: 0x00
Fragment offset: 0
Time to live: 2
Protocol: UDP (17)
Header checksum: 0xf8b5 [correct]
Source: 128.238.63.2 (128.238.63.2) ROUTER 2
Destination: 255.255.255.255 (255.255.255.255)

UDP header:

Source Port Number

Destination Port
Number

Length

Checksum

Source port: router (520)

Destination port: router (520)
Length: 52
Checksum: 0xbca0 [validation disabled]

RIP message format:

command(1-6)

version(1)

set to zero

address family (2)

set to zero
4-byte IP address
set to zero
set to zero
metric (1-16)

up to 24 more routes, with the same format as the above 20 bytes

Command: Response (2)

Version: RIPv1 (1)
IP Address: 128.238.62.0, Metric: 1
Address Family: IP (2)
IP Address: 128.238.62.0 (128.238.62.0)
Metric: 1
IP Address: 128.238.61.0, Metric: 2
Address Family: IP (2)
IP Address: 128.238.61.0 (128.238.61.0)
Metric: 2

The contents of the RIP messages are very similar for all computers. Each message shows two subnets
and their distance (metric), that is 1 for the nearer subnet and 2 for the farthest subnet. The subnet that
would have distance 3 doesnt show because RIP routers only maintain the best route, so this subnet
shows as being with distance 1 using another router to reach it.
5

Distance table for Router 1 eth0:

Destination

No. of hops

128.238.62.0

128.238.63.0

128.238.64.0

Distance table for Router 1 eth1:

Destination

No. of hops

128.238.61.0

128.238.63.0

128.238.64.0

Distance table for Router 2 eth0:

Destination

No. of hops

128.238.61.0

128.238.63.0

128.238.64.0

Distance table for Router 2 eth1:

Destination

No. of hops

128.238.61.0

128.238.62.0

128.238.64.0

Distance table for Router 3 eth0:

Destination

No. of hops

128.238.61.0

128.238.62.0

128.238.64.0

Distance table for Router 3 eth1:

Destination

No. of hops

128.238.61.0

128.238.62.0

128.238.63.0

Distance table for Router 4 eth0:

Destination

No. of hops

128.238.61.0

128.238.62.0

128.238.63.0

Distance table for Router 4 eth1:

Destination

No. of hops

128.238.62.0

128.238.63.0

128.238.64.0

Routing table for Router 1:

Destination

No. of hops

Next Hop
7

128.238.61.0

128.238.61.0

128.238.62.0

128.238.62.0

128.238.63.0

128.238.62.0

128.238.64.0

128.238.61.0

Routing table for Router 2:

Destination

No. of hops

Next Hop

128.238.61.0

128.238.62.0

128.238.62.0

128.238.62.0

128.238.63.0

128.238.63.0

128.238.64.0

128.238.63.0

Routing table for Router 3:

Destination

No. of hops

Next Hop

128.238.61.0

128.238.64.0

128.238.62.0

128.238.63.0

128.238.63.0

128.238.63.0

128.238.64.0

128.238.64.0

Routing table for Router 4:

Destination

No. of hops

Next Hop

128.238.61.0

128.238.61.0

128.238.62.0

128.238.61.0

128.238.63.0

128.238.64.0

128.238.64.0

128.238.64.0

Exercise 4

2
host)

0.002127

128.238.63.3

128.238.63.102 ICMP

70

Redirect

(Redirect for

Type: 5 (Redirect)
Code: 1 (Redirect for host)
Checksum: 0x660c [correct]
Gateway address: 128.238.63.2 (128.238.63.2)

The routing table wont change because we prevented automatic updating in the router settings, but if
not for this the routing table would be update and an entry would have the D flag (route created by
redirect).

Kernel IP routing table

Destination

Gateway

128.238.63.0 *
127.0.0.0
default

Genmask

Flags MSS Window irtt Iface

255.255.255.0 U
255.0.0.0

128.238.63.3 0.0.0.0

00
00

UG

0 eth0
0 lo

00

0 eth0

U means the route is up, G means it is a route to a router.

Exercise 5

1
0.000000
128.238.66.4 255.255.255.255
Advertisement (Normal router advertisement)

ICMP

60

Mobile IP

Ethernet II, Src: Cisco_81:cd:69 (00:10:7b:81:cd:69), Dst: Broadcast (ff:ff:ff:ff:ff:ff)

Internet Protocol Version 4, Src: 128.238.66.4 (128.238.66.4), Dst: 255.255.255.255 (255.255.255.255)
Type: 9 (Mobile IP Advertisement)
Code: 0 (Normal router advertisement)
Router address: 128.238.66.4

Preference level: 0

Router 4 sends the advertisement in broadcast. SHAKTI has 1 default router entry.

Kernel IP routing table

Destination

Gateway

Genmask

Flags MSS Window irtt Iface

128.238.66.0 128.238.66.100 255.255.255.0 UG

128.238.66.0 0.0.0.0

255.255.255.0 U

169.254.0.0

255.255.0.0

127.0.0.0

0.0.0.0
0.0.0.0

255.0.0.0

U
U

00

00
00
00

0 eth0

0 eth0
0 eth0
0 lo

10