Advance Computer Networks_Assignment No_3

8/11/2019 Advance Computer Networks_Assignment No_3

1/28

SAI KAUSHIK DEEPALA

ADVANCED COMPUTER NETWORKS

ASSIGNMENT-3

1) IPv4 is the fourth version in the development of the IP and is used for the most of theapplication on the Internet. IPv4 uses the packet-switched networking style. It runs on the besteffort delivery which does not guarantee delivery or does it assure the proper sequencing andavoidance of any duplicate packet.

In the format of IPv4 the 8 bit field is provided which is called as the Time to Live. TTL is anupper layer which is used to helps datagram's in circulating and it tracks the lifetime of adatagram in a network and prevents packets from circulating continuously and discards themafter a time span. So when time interval is set less than 1 sec it is rounded as 1, so whendatagram arrives at router the TTL fields set hop as zero then the packet is discarded in IPv4.Therefore this field limits a datagram's lifetime. In practical, the seconds has become a hop countwhen the datagram or a packet arrives at a router, the router decrements the TTL field by one asit proceeds to the next router. If the TTL circulates and reaches zero then the datagram isdiscarded and ICMP sends an error report to the sender. In IPv4 time to live is an 8-bit field.

The Trace route and Ping are used in measuring transit delays in the network. They make use ofTTL values in reaching the destination or to trace the route over a router. In general it is

primarily provided to avoid the clogging in the route that is it does not allow any packet toremain in the network for the long period depending on the priorities.

2) Trace route: It is used for displaying the path and measuring transit delays of packets acrossan Internet Protocol network. In this process it recorded the path or route as the round-trip timesof the packets received from each remote node in the route, the sum of the mean times in eachhop indicates the total time spent to establish the connection.

Work around description:

Trace route attempts to trace the route an IP packet would take to reach the internet host bylaunching probe packets with a small TTL as possible, then listening for an ICMP "timeexceeded" reply from a gateway. It start its probes with a TTL of 1 and increases this by 1 until itgets an ICMP "port unreachable", which means we got to the "host", or hit a max .i.e. by defaultsto 30 hops. Three probes are sent by default for each TTL setting and a line is printed showing

the TTL, address of the gateway and round trip time of each probe. If the probe answers comefrom different gateways, the address of each responding system will be printed. If there is noresponse within a 5.0 seconds which is by default, an "*" is printed for that probe.

From given exp:

Here we can see that the trace path took 31 hops in total, whereas out of 31 it took only 16 hopsto reach the destination server. Trace route sends three packets of data at a time by default andmeasures the time taken for each packet. From this example, we can see that each hop took


2/28

different time varying from 0.170ms to 103.308ms. therefore we can conclude that it took103.308ms to retrie ve data from the destination server and after hop number 16 a message noreply is shown, it means that there is a problem with the route as it could not find the route tothe host.

3) Below are the websites which I picked to find out trace route output:

a) North America - coca-cola company

Output:(Day-1)Tracing route to coca-colacompany.com [205.218.8.249]

over a maximum of 30 hops:

1 6 ms 23 ms 1 ms 192.168.0.1

2 7 ms 2 ms 2 ms 192.168.1.13 4 ms 2 ms 3 ms 207.179.124.129

4 10 ms 10 ms 14 ms 207.179.77.5

5 11 ms 7 ms 9 ms ns2.iti.net [208.77.128.153]

6 15 ms 12 ms 12 ms 9-1-5.ear1.Chicago2.Level3.net [4.35.108.129]

7 15 ms 15 ms 13 ms ae-1-51.edge4.Chicago3.Level3.net [4.69.138.134]

8 12 ms 14 ms 15 ms 208.174.226.213

9 18 ms 23 ms 18 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

10 80 ms 45 ms 55 ms cr1-te-0-13-2-0.dck.savvis.net [204.70.200.90]

11 76 ms 101 ms 101 ms hr1-tengig-2-0-0.sterling2dc2.savvis.net [204.70.197.74]

12 122 ms 37 ms 33 ms das14-v3049.dc4.savvis.net [205.138.145.226]

13 * * * Request timed out.








3/28



Output:(Day-2)Tracing route to coca-colacompany.com [205.218.8.249]


1 1 ms 1 ms 3 ms 192.168.0.1

2 22 ms 1 ms 1 ms 192.168.1.1

3 7 ms 2 ms 3 ms 207.179.124.129

4 26 ms 13 ms 10 ms 207.179.77.5

5 14 ms 18 ms 8 ms ns2.iti.net [208.77.128.153]



8 20 ms 31 ms 13 ms 208.174.226.213















4/28




25 * * * Request timed out.26 * * * Request timed out.





Trace complete.

Output: (Day-3)

Tracing route to coca-colacompany.com [205.218.8.249]


1 3 ms 1 ms 1 ms 192.168.0.1

2 32 ms 9 ms 12 ms 192.168.1.1

3 4 ms 2 ms 2 ms 207.179.124.129

4 10 ms 7 ms 7 ms 207.179.77.5

5 9 ms 6 ms 8 ms ns2.iti.net [208.77.128.153]



8 22 ms 14 ms 13 ms 208.174.226.213







5/28

















Trace complete.

Output:(Day-4)

Tracing route to coca-colacompany.com [205.218.8.249]


1 3 ms 1 ms 1 ms 192.168.0.1

2 4 ms 1 ms 2 ms 192.168.1.1

3 3 ms 3 ms 7 ms 207.179.124.129

4 43 ms 29 ms 11 ms 207.179.77.5

5 10 ms 8 ms 7 ms ns2.iti.net [208.77.128.153]


6/28



8 15 ms 13 ms 14 ms 208.174.226.213

9 17 ms 30 ms 22 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]10 82 ms 140 ms 95 ms cr1-te-0-13-2-0.dck.savvis.net [204.70.200.90]





















Trace complete.

Graph representing the 4 days output.


7/28

From the above trace out it is visible that the trace output is different each time we try reach thedestination. From this test results it is evident that when the source is trying to send data to thedestination it doesn't know the path to reach the destination but know only the destination and soit starts ping or reaching out for the nearest router. And if the router available it pass the datefrom there to the next nearest router and so on. In this process it tries to reach the destination ,

but all the time it might not be the same routers or path it might change the router or path toreach the destination , thus this explains the difference in delay time each when we try reach thedestination.

b) Europe - volkswagen.co.uk

Output:(Day-1)

Tracing route to volkswagen.co.uk [134.213.10.91]


1 2 ms 1 ms 1 ms 192.168.0.1

2 4 ms 1 ms 1 ms 192.168.1.1

3 5 ms 3 ms 2 ms 207.179.124.129

4 16 ms 13 ms 12 ms 207.179.77.5

5 11 ms 8 ms 19 ms 208.77.128.154

6 39 ms 77 ms 34 ms 100.xe-10-2-1.mpr1.cle1.us.above.net [128.177.116.53]

7 38 ms 63 ms 100 ms 64.125.20.85.available.above.net [64.125.20.85]

0

20

40

60

80

100

120

140

160

180

0 0.5 1 1.5 2 2.5 3 3.5 4 4.5

Y-Values

Y-Values


8/28

8 104 ms 45 ms 46 ms xe-2-2-1.mpr3.phl2.us.above.net [64.125.20.18]

9 66 ms 101 ms 49 ms ae4.mpr4.phl2.us.above.net [64.125.21.74]

10 49 ms 60 ms 53 ms 64.125.31.25

11 157 ms 197 ms 206 ms xe-4-1-0.mpr1.lhr3.uk.above.net [64.125.24.42]12 127 ms 123 ms 135 ms ae5.mpr1.lhr23.uk.above.net [64.125.20.97]

13 131 ms 125 ms 153 ms 94.31.42.254.IPYX-076520-ZYO.above.net [94.31.42.254]

14 175 ms 121 ms 175 ms corea-edge4.lon3.rackspace.net [164.177.137.34]

15 219 ms 204 ms 119 ms core7-corea.lon3.rackspace.net [164.177.137.101]

16 149 ms 199 ms 202 ms aggr341a-3-core7.lon3.rackspace.net [94.236.62.149]

17 123 ms 202 ms 202 ms 134.213.10.91

Trace complete.

Output:(Day-2)



1 3 ms 2 ms 3 ms 192.168.0.1

2 2 ms 2 ms 1 ms 192.168.1.1

3 5 ms 4 ms 2 ms 207.179.124.129

4 10 ms 12 ms 8 ms 207.179.77.5

5 10 ms 8 ms 6 ms 208.77.128.154





10 49 ms 47 ms 121 ms 64.125.31.25

11 153 ms 192 ms 188 ms xe-4-1-0.mpr1.lhr3.uk.above.net [64.125.24.42]

12 123 ms 182 ms 191 ms ae5.mpr1.lhr23.uk.above.net [64.125.20.97]


9/28




16 210 ms 212 ms 195 ms aggr341b-3-core8.lon3.rackspace.net [94.236.62.155]17 209 ms 203 ms 181 ms 134.213.10.91

Trace complete.

Output:(Day-3)



1 4 ms 1 ms 1 ms 192.168.0.1

2 2 ms 9 ms 1 ms 192.168.1.1

3 208 ms 204 ms 202 ms 207.179.124.129

4 126 ms 204 ms 131 ms 207.179.77.5

5 127 ms 205 ms 202 ms 208.77.128.154





10 158 ms 199 ms 207 ms 64.125.31.25


12 386 ms 314 ms 298 ms ae5.mpr1.lhr23.uk.above.net [64.125.20.97]




16 316 ms 248 ms 266 ms aggr341b-3-core8.lon3.rackspace.net [94.236.62.155]

17 238 ms 257 ms 199 ms 134.213.10.91


10/28

Trace complete.

Output:(Day-4)

Tracing route to volkswagen.co.uk [134.213.10.91]over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1

2 3 ms 5 ms 2 ms 192.168.1.1

3 197 ms 203 ms 127 ms 207.179.124.129

4 129 ms 204 ms 203 ms 207.179.77.5

5 127 ms 109 ms 93 ms 208.77.128.154





10 163 ms 203 ms 211 ms 64.125.31.25


12 324 ms 304 ms * ae5.mpr1.lhr23.uk.above.net [64.125.20.97]




16 210 ms 216 ms 209 ms aggr341b-3-core7.lon3.rackspace.net [94.236.62.153]

17 241 ms 246 ms 256 ms 134.213.10.91

Trace complete.



11/28



c) Asian - asianpaints.com

Output:(Day-1)

Tracing route to asianpaints.com [180.179.202.106]


1 3 ms 1 ms 1 ms 192.168.0.1

2 3 ms 1 ms 1 ms 192.168.1.1

3 4 ms 4 ms 2 ms 207.179.124.1294 22 ms 11 ms 8 ms 207.179.77.5

5 18 ms 12 ms 16 ms 208.77.128.154



0

50

100

150

200

250

300

0 0.5 1 1.5 2 2.5 3 3.5 4 4.5

Y-Values

Y-Values


12/28


9 117 ms 54 ms 56 ms ae9.cr1.lga5.us.above.net [64.125.31.125]

10 66 ms 101 ms 101 ms ae8.er1.lga5.us.above.net [64.125.26.162]

11 123 ms 46 ms 123 ms ae4.er2.lga5.us.above.net [64.125.31.166]12 77 ms 42 ms 55 ms ix-1-1-3-0.tcore2.NTO-New-York.as6453.net [209.58.26.37]

13 181 ms 183 ms 119 ms if-14-14.tcore2.NJY-Newark.as6453.net [66.198.111.125]


15 128 ms * 191 ms if-7-2.tcore1.L78-London.as6453.net [66.198.70.26]

16 118 ms 202 ms 137 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]

17 303 ms 234 ms 290 ms 80.231.131.114



20 342 ms 303 ms 306 ms 14.140.210.34.static-Delhi-vsnl.net.in [14.140.210.34]

21 329 ms 305 ms 305 ms 180.179.197.50

22 333 ms 304 ms 306 ms 180.179.202.106









Trace complete.

Output:(Day-2)



13/28


1 1 ms 1 ms 2 ms 192.168.0.1

2 9 ms 18 ms 1 ms 192.168.1.1

3 4 ms 2 ms 2 ms 207.179.124.1294 11 ms 7 ms 7 ms 207.179.77.5

5 17 ms 8 ms 8 ms 208.77.128.154







12 142 ms 101 ms 101 ms ix-1-1-3-0.tcore2.NTO-New-York.as6453.net [209.58.26.37]





17 243 ms 235 ms 274 ms 80.231.131.114




21 311 ms 306 ms 306 ms 180.179.197.50

22 291 ms 268 ms 345 ms 180.179.202.106






14/28




30 * * * Request timed out.Trace complete.

Output:(Day-3)



1 16 ms 1 ms 3 ms 192.168.0.1

2 3 ms 1 ms 1 ms 192.168.1.1

3 8 ms 3 ms 2 ms 207.179.124.129

4 11 ms 7 ms 9 ms 207.179.77.5

5 42 ms 12 ms 7 ms 208.77.128.154










15 181 ms 126 ms * if-7-2.tcore1.L78-London.as6453.net [66.198.70.26]


17 329 ms 304 ms 233 ms 80.231.131.114



15/28



21 335 ms 299 ms 289 ms 180.179.197.50

22 333 ms 403 ms 409 ms 180.179.202.10623 * * * Request timed out.








Trace complete.

Output:(Day-4)



1 1 ms


16/28




14 125 ms 202 ms 164 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]15 120 ms 205 ms 118 ms if-7-2.tcore1.L78-London.as6453.net [66.198.70.26]

16 116 ms * 197 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]

17 236 ms 234 ms 259 ms 80.231.131.114




21 323 ms 313 ms 316 ms 180.179.197.50

22 331 ms 382 ms 406 ms 180.179.202.106









Trace complete


17/28




Here if we absorb the 18th and 19th hop we have got the request time out message and so thesource had to remap the path to reach the destination by start the above process all over again.

d) Africa - sappicareers.pnet.co.za

Output:(Day-1)

Tracing route to sappicareers.pnet.co.za [196.35.169.122]


1 1 ms 1 ms 1 ms 192.168.0.1

2 3 ms 2 ms 6 ms 192.168.1.1

3 2 ms 2 ms 2 ms 207.179.124.129

4 7 ms 7 ms 7 ms 207.179.77.5

5 7 ms 7 ms 25 ms ns2.iti.net [208.77.128.153]

0

50

100

150

200

250

300

350400

450

0 1 2 3 4 5

Y-Values

Y-Values


18/28


19/28

Output:(Day-2)


over a maximum of 30 hops:1 1 ms 1 ms 1 ms 192.168.0.1

2 8 ms 1 ms 3 ms 192.168.1.1

3 27 ms 12 ms 27 ms 207.179.124.129

4 8 ms 8 ms 7 ms 207.179.77.5

5 9 ms 8 ms 7 ms ns2.iti.net [208.77.128.153]


7 104 ms 105 ms 107 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]







14 122 ms 122 ms 101 ms ae-226-3602.edge3.London1.Level3.net [4.69.166.150]

15 113 ms 129 ms 113 ms INTERNET-SO.edge3.London1.Level3.net [195.50.124.34]

16 356 ms 278 ms 281 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

17 285 ms 284 ms 285 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]

18 287 ms 319 ms 279 ms core1a-pkl-te1-2.isnet.net [168.209.100.238]

19 339 ms 318 ms 355 ms 168.209.218.16

20 294 ms 327 ms 293 ms pnet-bry-fw01.fw.is.co.za [196.35.71.86]





20/28







Trace complete.

Output:(Day-3)



1 1 ms 1 ms 1 ms 192.168.0.1

2 1 ms 1 ms 1 ms 192.168.1.1

3 2 ms 2 ms 4 ms 207.179.124.129

4 7 ms 8 ms 9 ms 207.179.77.5

5 7 ms 7 ms 7 ms ns2.iti.net [208.77.128.153]












21/28




19 301 ms 342 ms 294 ms 168.209.218.1620 289 ms 419 ms 291 ms pnet-bry-fw01.fw.is.co.za [196.35.71.86]











Trace complete.

Output:(Day-4)



1 6 ms 1 ms 1 ms 192.168.0.1

2 32 ms 2 ms 1 ms 192.168.1.1

3 17 ms 2 ms 2 ms 207.179.124.129

4 7 ms 7 ms 6 ms 207.179.77.5

5 15 ms 9 ms 7 ms ns2.iti.net [208.77.128.153]




22/28











19 286 ms 285 ms 285 ms 168.209.218.16

20 291 ms 298 ms 287 ms pnet-bry-fw01.fw.is.co.za [196.35.71.86]











Trace complete.



23/28



Here if we absorb the 8th and 13th hop we have got the request time out message and so thesource had to remap the path to reach the destination by start the above process all over again.

e) South America - authenware.com

Output:(Day-1)

Tracing route to authenware.com [50.30.32.160]


1 18 ms 1 ms 1 ms 192.168.0.1

2 1 ms 7 ms 1 ms 192.168.1.1

3 95 ms 2 ms 2 ms 207.179.124.129

4 23 ms 38 ms 6 ms 207.179.77.5

5 59 ms 26 ms 27 ms ns2.iti.net [208.77.128.153]

286

287

288

289

290

291

292

293

294

0 1 2 3 4 5

Y-Values

Y-Values


24/28



8 21 ms 38 ms 22 ms ae-5-5.car2.StLouis1.Level3.net [4.69.201.2]

9 25 ms 56 ms 41 ms 4.28.92.19010 27 ms 40 ms 22 ms static-ip-209-239-125-38.inaddr.ip-pool.com [209.239.125.38]

11 62 ms 32 ms 27 ms usloft2618.serverloft.com [50.30.32.160]

Trace complete.

Output:(Day-2)



1 1 ms 4 ms 1 ms 192.168.0.1

2 3 ms 1 ms 2 ms 192.168.1.1

3 4 ms 2 ms 7 ms 207.179.124.129

4 11 ms 28 ms 32 ms 207.179.77.5

5 30 ms 26 ms 51 ms ns2.iti.net [208.77.128.153]




9 36 ms 75 ms 49 ms 4.28.92.190

10 40 ms 33 ms 32 ms static-ip-209-239-125-38.inaddr.ip-pool.com [209.239.125.38]


Trace complete.

Output:(Day-3)




25/28

1 1 ms 6 ms 1 ms 192.168.0.1

2 4 ms 1 ms 1 ms 192.168.1.1

3 2 ms 2 ms 2 ms 207.179.124.129

4 30 ms 41 ms 9 ms 207.179.77.55 24 ms 21 ms 20 ms ns2.iti.net [208.77.128.153]




9 36 ms 40 ms 28 ms 4.28.92.190



Trace complete.

Output:(Day-4)



1 6 ms 1 ms 1 ms 192.168.0.1

2 1 ms 7 ms 1 ms 192.168.1.1

3 2 ms 2 ms 5 ms 207.179.124.129

4 9 ms 36 ms 27 ms 207.179.77.5

5 37 ms 35 ms 31 ms ns2.iti.net [208.77.128.153]




9 32 ms 31 ms 24 ms 4.28.92.190




26/28

Trace complete.




4) SNMP uses the User Datagram Protocol as the transport protocol for passing data betweensource and destination. UDP is chosen because it is connectionless and is more relievable overTCP in case of connection failures; that is, no end-to-end connection is made. This aspect alsomakes UDP unreliable, since there is no acknowledgment of lost datagrams. And SNMPapplication plays a important part to determine if datagrams are lost, if it so retransmit them. Thisis typically accomplished with a simple timeout. The NMS sends a UDP request to an agent andwaits for a response, If the timeout is reached and the NMS has not heard back from the agent, itassumes the packet was lost and retransmits the request.

The advantage of UDP is that it requires low overhead and impact on your network's performance is reduced. SNMP is designed for working with networks in two ways , if yournetwork never failed, you wouldn't need to monitor it. When a network is failing, a protocol thattries to get the data through but gives up if it can't is almost certainly a better design choice thana protocol that will flood the network with retransmissions in attempt to achieve destination.

0

5

10

15

20

25

30

35

40

45

0 1 2 3 4 5

Y-Values

Y-Values


27/28

SNMP uses the UDP port 161 for sending and receiving requests, and port 162 for receivingtraps from managed devices.

5) Minimum TCP packet size:

Size of Ethernet frame = 24 Bytes

Size of IPv4 Header = 20 bytes

Size of TCP Header = 20 Bytes

Therefore total size of empty TCP Packet = 24 + 20 + 20 = 64 bytes

Minimum IP packet Size:

Size of Ethernet frame = 24 Bytes

Size of IPv4 Header = 20 bytes

therefore total size of empty IP Packet = 24 + 20 = 44 bytes

Maximum TCP packet Size = 64K

i.e. 2^16-1 = 65535 bytes.

Because it is the maximum value of 16 bit unsigned integer.

Maximum IP packet size:

Maximum IP packet size = 65535 bytes

Because the maximum word length in IP is 2 bytes

Therefore 1 byte = 8 bits

.i.e. 2^16 = 65536.

6) Next Header: The following figure shows the elements that appear in the IPv6 header and theorder in which the elements appear.

IPv6 Header Format


28/28

Next Header is a 8-bit selector. Identifies the type of header that immediately follows the IPv6header. it uses the same values as the IPv4 protocol field. IPv6 has improved option mechanismover IPv4. IPv6 options are in separate extension headers that is in between the IPv6 header andthe transport layer header in a packet. Most IPv6 extension headers are not examined or

processed by any router along a packet's delivery path until the packet arrives at its finaldestination. This feature is a major improvement in router performance for packets that containoptions. IPv6 extension headers can be of arbitrary length and also the number of options that a

packet carries are not limited to 40 bytes. This feature and the manner in which IPv6 options are processed, it allows IPv6 options to be used for functions that are not practical in IPv4. A goodexample of IPv6 options is the IPv6 authentication and security encapsulation options. , IPv6options are always an integer multiple of eight octets long this is to improve performance whenhandling subsequent option headers, and the transport protocol. The integer multiple of eightoctets retains the alignment of subsequent headers.

The following IPv6 extension headers are currently defined.

1. Routing Extended routing2. Fragmentation Fragmentation and reassembly3. Authentication Integrity and authentication, security4. Encapsulation Confidentiality5. Hop-by-Hop Option Special options that require hop-by-hop processing6. Destination Options Optional information to be examined by the destination node

IPv6 Features Changes from IPv4 to IPv6 are described in the following categories:

1. Expanded routing and addressing capabilities2. Header format simplification3. Improved support for options4. Quality-of-service capabilities5. Authentication and privacy capabilities

Advance Computer Networks_Assignment No_3

Documents

Transcript of Advance Computer Networks_Assignment No_3