LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 08-20-2009, 12:26 PM   #1
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Rep: Reputation: 0
Cannot analyse normalised routing load as RTR packets show as dropped in trace file


Hi,

I need to measure a number of metrics for my Uni project which are data packet deliver ratio, end-to-end delay and normalised routing overhead. I am using an awk file called parameters.awk to analyse these metrics against the trace files. I am getting output for packet delivery ratio and end-to-end delay however the output for normalised routing overhead always returns zero. This is an important metric I must be able to analyse to check the routing protocols performance, I am simulating MANET routing protocols DSDV, DSR and AODV against a number of scenarios. The awk file I am using contains the following code:

Code:
BEGIN {
       sends=0;
       recvs=0;
       routing_packets=0.0;
       droppedBytes=0;
       droppedPackets=0;
       highest_packet_id=0;
       sum=0;
       recvnum=0;
     }
   
  {
  time = $3;
  packet_id = $41;
   
  # CALCULATE PACKET DELIVERY FRACTION
  if (( $1 == "s") &&  ( $35 == "cbr" ) && ( $19=="AGT" )) {  sends++; }
   
  if (( $1 == "r") &&  ( $35 == "cbr" ) && ( $19=="AGT" ))   {  recvs++; }
   
  # CALCULATE DELAY 
  if ( start_time[packet_id] == 0 )  start_time[packet_id] = time;
  if (( $1 == "r") &&  ( $35 == "cbr" ) && ( $19=="AGT" )) {  end_time[packet_id] = time;  }
       else {  end_time[packet_id] = -1;  }
   
  # CALCULATE TOTAL AODV OVERHEAD 
  if (($1 == "s" || $1 == "f") && $19 == "RTR" && $35 =="AODV") routing_packets++;
   
  # DROPPED AODV PACKETS 
  if (( $1 == "d" ) && ( $35 == "cbr" )  && ( $3 > 0 ))
       {
             droppedBytes=droppedBytes+$37;
             droppedPackets=droppedPackets+1;
       }
   
       #find the number of packets in the simulation
          if (packet_id > highest_packet_id)
             highest_packet_id = packet_id;
  }
   
  END {
   
  for ( i in end_time )
  {
  start = start_time[i];
  end = end_time[i];
  packet_duration = end - start;
  if ( packet_duration > 0 )  
  {    sum += packet_duration;
       recvnum++; 
  }
  }
   
     delay=sum/recvnum;
     NRL = routing_packets/recvs;  #normalized routing load 
     PDF = (recvs/sends)*100;  #packet delivery ratio[fraction]
     printf("send = %.2f\n",sends);
     printf("recv = %.2f\n",recvs);
     printf("routingpkts = %.2f\n",routing_packets++);
     printf("PDF = %.2f\n",PDF);
     printf("%.2f\t",PDF);
     printf("NRL = %.2f\n",NRL);
     printf("Average e-e delay(ms)= %.2f\n",delay*1000);
     printf("%.2f\n",delay*1000);
     printf("No. of dropped data (packets) = %d\n",droppedPackets);
     printf("No. of dropped data (bytes)   = %d\n",droppedBytes);
     printf("Packet Loss [%]= %.2f  \n", (droppedPackets/(highest_packet_id+1))*100);
  }
I get the following output after running this file:

----------
send = 6132.00
recv = 5403.00
routingpkts = 0.00
PDF = 88.11
NRL = 0.00
Average e-e delay(ms)= 385.88
No. of dropped data (packets) = 730
No. of dropped data (bytes) = 388380
Packet Loss [%]= 4.84
----------
send = 6104.00
recv = 5410.00
routingpkts = 0.00
PDF = 88.63
NRL = 0.00
Average e-e delay(ms)= 302.30
No. of dropped data (packets) = 694
No. of dropped data (bytes) = 369268
Packet Loss [%]= 5.09
----------
send = 6102.00
recv = 5362.00
routingpkts = 0.00
PDF = 87.87
NRL = 0.00
Average e-e delay(ms)= 621.30
No. of dropped data (packets) = 741
No. of dropped data (bytes) = 394292
Packet Loss [%]= 5.45
----------

Routing packets and normalised routing overhead always shows as zero for all the routing protocols and scenario trace file outputs I have simulated. An example of the trace files are as follows (this example is AODV):

M 0.0 prop Propagation/TwoRayGround ant Antenna/OmniAntenna
M 0.00000 0 (82.72, 325.82, 0.00), (226.30, 434.11), 18.09
M 0.00000 1 (326.63, 412.58, 0.00), (399.97, 432.73), 1.03
M 0.00000 2 (492.93, 381.84, 0.00), (211.08, 423.25), 10.76
M 0.00000 3 (332.36, 184.16, 0.00), (405.90, 361.21), 12.80
M 0.00000 4 (131.13, 404.61, 0.00), (67.43, 236.99), 6.01
M 0.00000 5 (171.77, 440.94, 0.00), (290.88, 242.27), 6.33
M 0.00000 6 (180.16, 422.85, 0.00), (308.31, 79.44), 5.85
M 0.00000 7 (142.55, 335.63, 0.00), (237.04, 130.22), 9.96
M 0.00000 8 (317.01, 333.29, 0.00), (25.34, 266.35), 9.37
M 0.00000 9 (372.85, 200.06, 0.00), (232.10, 229.03), 8.43
M 0.00000 10 (15.06, 0.65, 0.00), (431.78, 483.67), 6.53
M 0.00000 11 (272.96, 211.74, 0.00), (125.39, 271.21), 11.44
M 0.00000 12 (348.79, 226.90, 0.00), (429.71, 35.76), 12.86
M 0.00000 13 (212.69, 209.19, 0.00), (273.40, 478.01), 16.38
M 0.00000 14 (318.41, 482.16, 0.00), (409.22, 327.42), 1.82
M 0.00000 15 (414.80, 268.72, 0.00), (449.09, 291.43), 15.42
M 0.00000 16 (216.87, 235.87, 0.00), (408.46, 94.20), 5.13
M 0.00000 17 (492.74, 291.84, 0.00), (490.44, 308.50), 1.33
M 0.00000 18 (87.79, 348.25, 0.00), (167.02, 65.16), 8.18
M 0.00000 19 (399.56, 93.47, 0.00), (179.91, 452.08), 8.56
M 0.00000 20 (423.16, 373.73, 0.00), (363.38, 153.26), 11.81
M 0.00000 21 (2.24, 82.14, 0.00), (134.03, 494.15), 10.90
M 0.00000 22 (301.21, 494.64, 0.00), (314.03, 343.81), 19.06
M 0.00000 23 (362.36, 292.24, 0.00), (397.61, 419.89), 19.77
M 0.00000 24 (100.06, 30.31, 0.00), (94.06, 252.37), 18.82
M 0.00000 25 (294.05, 471.61, 0.00), (212.34, 347.41), 10.06
M 0.00000 26 (451.18, 80.03, 0.00), (53.74, 280.16), 8.19
M 0.00000 27 (43.30, 339.65, 0.00), (388.40, 14.22), 8.90
M 0.00000 28 (331.68, 183.59, 0.00), (460.90, 311.07), 16.46
M 0.00000 29 (270.25, 465.67, 0.00), (331.47, 278.30), 0.62
M 0.00000 30 (207.08, 461.11, 0.00), (447.44, 335.58), 11.25
M 0.00000 31 (405.45, 461.12, 0.00), (210.20, 124.01), 7.61
M 0.00000 32 (369.71, 283.32, 0.00), (256.32, 473.07), 14.15
M 0.00000 33 (84.93, 182.61, 0.00), (337.50, 482.66), 17.63
M 0.00000 34 (375.04, 360.15, 0.00), (288.65, 26.18), 15.72
M 0.00000 35 (447.81, 45.14, 0.00), (190.31, 418.20), 19.45
M 0.00000 36 (272.80, 257.75, 0.00), (110.47, 479.85), 4.14
M 0.00000 37 (437.28, 228.03, 0.00), (14.89, 170.75), 1.51
M 0.00000 38 (198.32, 438.45, 0.00), (141.76, 22.39), 4.48
M 0.00000 39 (223.62, 247.48, 0.00), (431.81, 270.19), 8.61
M 0.00000 40 (233.61, 17.96, 0.00), (352.83, 319.22), 0.20
M 0.00000 41 (288.04, 369.15, 0.00), (417.99, 365.55), 18.62
M 0.00000 42 (319.63, 124.98, 0.00), (419.51, 225.20), 16.98
M 0.00000 43 (71.10, 434.89, 0.00), (433.11, 150.52), 11.02
M 0.00000 44 (131.27, 386.14, 0.00), (89.34, 43.70), 11.68
M 0.00000 45 (50.76, 124.52, 0.00), (280.69, 220.13), 4.58
M 0.00000 46 (291.87, 290.64, 0.00), (299.08, 180.06), 14.85
M 0.00000 47 (26.10, 401.86, 0.00), (447.71, 356.21), 0.92
M 0.00000 48 (111.39, 252.15, 0.00), (166.98, 441.22), 16.36
M 0.00000 49 (315.17, 356.62, 0.00), (406.52, 294.87), 6.54
M 0.00000 50 (281.01, 27.61, 0.00), (279.28, 117.65), 19.63
M 0.00000 51 (259.84, 30.01, 0.00), (175.89, 15.25), 5.32
M 0.00000 52 (372.70, 459.39, 0.00), (209.45, 278.84), 14.95
M 0.00000 53 (11.30, 375.97, 0.00), (190.65, 151.16), 16.18
M 0.00000 54 (160.82, 171.93, 0.00), (412.66, 410.14), 8.24
M 0.00000 55 (291.22, 340.68, 0.00), (381.34, 65.27), 9.48
M 0.00000 56 (11.87, 484.05, 0.00), (361.47, 121.35), 19.24
M 0.00000 57 (386.86, 491.67, 0.00), (51.86, 125.12), 18.98
M 0.00000 58 (107.78, 150.39, 0.00), (115.38, 326.88), 16.39
M 0.00000 59 (143.30, 69.23, 0.00), (180.97, 363.66), 12.26
M 0.00000 60 (420.21, 251.52, 0.00), (411.30, 79.43), 11.40
M 0.00000 61 (415.72, 110.23, 0.00), (377.46, 98.01), 14.70
M 0.00000 62 (460.85, 247.83, 0.00), (164.35, 79.62), 4.97
M 0.00000 63 (281.92, 143.29, 0.00), (385.52, 94.25), 3.41
M 0.00000 64 (30.70, 67.28, 0.00), (381.01, 112.95), 12.77
M 0.00000 65 (183.58, 89.02, 0.00), (445.08, 69.23), 6.55
M 0.00000 66 (154.68, 482.38, 0.00), (350.82, 27.12), 8.12
M 0.00000 67 (177.27, 205.66, 0.00), (160.83, 50.66), 14.06
M 0.00000 68 (416.64, 91.89, 0.00), (89.33, 475.83), 10.80
M 0.00000 69 (291.95, 65.35, 0.00), (274.94, 381.39), 12.00
M 0.00000 70 (350.16, 176.64, 0.00), (103.56, 416.84), 9.67
M 0.00000 71 (245.88, 377.87, 0.00), (252.26, 86.39), 12.92
M 0.00000 72 (115.59, 102.47, 0.00), (111.61, 358.51), 19.43
M 0.00000 73 (123.80, 6.42, 0.00), (310.33, 138.45), 14.23
M 0.00000 74 (141.08, 365.91, 0.00), (114.21, 331.18), 13.05
M 0.00000 75 (449.68, 267.87, 0.00), (30.00, 365.32), 14.21
M 0.00000 76 (424.80, 470.05, 0.00), (384.38, 63.47), 7.52
M 0.00000 77 (297.69, 470.37, 0.00), (262.65, 124.88), 17.09
M 0.00000 78 (39.01, 137.14, 0.00), (319.06, 18.47), 7.17
M 0.00000 79 (337.01, 441.02, 0.00), (123.11, 205.46), 17.90
M 0.00000 80 (24.71, 399.52, 0.00), (119.07, 266.07), 4.17
M 0.00000 81 (31.13, 173.84, 0.00), (63.49, 61.23), 2.48
M 0.00000 82 (434.33, 250.56, 0.00), (32.50, 206.61), 7.25
M 0.00000 83 (334.81, 86.55, 0.00), (18.48, 210.83), 12.98
M 0.00000 84 (490.51, 100.29, 0.00), (456.96, 409.74), 9.72
M 0.00000 85 (392.16, 176.93, 0.00), (306.52, 151.88), 5.76
M 0.00000 86 (94.29, 416.65, 0.00), (326.79, 227.70), 3.39
M 0.00000 87 (95.24, 432.42, 0.00), (256.51, 210.90), 16.70
M 0.00000 88 (383.91, 447.06, 0.00), (484.45, 219.47), 2.29
M 0.00000 89 (252.73, 418.29, 0.00), (487.47, 100.99), 11.82
M 0.00000 90 (30.44, 175.03, 0.00), (55.50, 476.67), 8.81
M 0.00000 91 (432.26, 275.21, 0.00), (141.24, 201.60), 3.65
M 0.00000 92 (315.01, 295.41, 0.00), (121.58, 206.45), 5.91
M 0.00000 93 (134.20, 344.03, 0.00), (192.69, 203.47), 9.25
M 0.00000 94 (432.00, 216.04, 0.00), (143.76, 303.68), 4.38
M 0.00000 95 (126.83, 415.49, 0.00), (400.54, 233.41), 0.88
M 0.00000 96 (131.44, 361.24, 0.00), (499.71, 196.09), 16.88
M 0.00000 97 (117.87, 391.12, 0.00), (472.65, 228.31), 10.22
M 0.00000 98 (332.95, 299.36, 0.00), (196.49, 235.36), 19.43
M 0.00000 99 (65.65, 433.15, 0.00), (338.64, 16.25), 15.68
s -t 2.556838879 -Hs 1 -Hd -2 -Ni 1 -Nx 329.17 -Ny 413.28 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.0 -Id 2.0 -It cbr -Il 512 -If 0 -Ii 0 -Iv 32 -Pn cbr -Pi 0 -Pf 0 -Po 1
M 2.66741 15 (449.09, 291.43, 0.00), (204.21, 201.51), 4.09
M 2.73328 61 (377.46, 98.01, 0.00), (425.08, 107.86), 19.67
M 3.36577 74 (114.21, 331.18, 0.00), (20.61, 164.74), 2.11
M 4.58791 50 (279.28, 117.65, 0.00), (209.66, 482.68), 14.57
M 5.20590 61 (425.08, 107.86, 0.00), (321.80, 402.25), 5.51
s -t 6.352093490 -Hs 1 -Hd -2 -Ni 1 -Nx 332.93 -Ny 414.31 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.0 -Id 2.0 -It cbr -Il 512 -If 0 -Ii 1 -Iv 32 -Pn cbr -Pi 1 -Pf 0 -Po 1
M 6.70031 23 (397.61, 419.89, 0.00), (430.49, 264.33), 0.95
M 6.98172 41 (417.99, 365.55, 0.00), (103.56, 391.55), 6.54
s -t 7.110637104 -Hs 77 -Hd -2 -Ni 77 -Nx 285.43 -Ny 349.45 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 77.0 -Id 78.0 -It cbr -Il 512 -If 0 -Ii 2 -Iv 32 -Pn cbr -Pi 0 -Pf 0 -Po 2
r -t 7.223957135 -Hs 78 -Hd 78 -Ni 78 -Nx 86.73 -Ny 116.92 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 4e -Ms 15 -Mt 800 -Is 77.0 -Id 78.0 -It cbr -Il 532 -If 0 -Ii 2 -Iv 25 -Pn cbr -Pi 0 -Pf 6 -Po 2
M 7.46230 46 (299.08, 180.06, 0.00), (191.29, 334.59), 2.54
s -t 7.703020315 -Hs 7 -Hd -2 -Ni 7 -Nx 174.60 -Ny 265.95 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 7.2 -Id 9.0 -It cbr -Il 512 -If 0 -Ii 3 -Iv 32 -Pn cbr -Pi 0 -Pf 0 -Po 1
M 7.75814 98 (196.49, 235.36, 0.00), (303.92, 112.70), 15.23
r -t 7.772143318 -Hs 9 -Hd 9 -Ni 9 -Nx 308.67 -Ny 213.27 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 9 -Ms 24 -Mt 800 -Is 7.2 -Id 9.0 -It cbr -Il 532 -If 0 -Ii 3 -Iv 29 -Pn cbr -Pi 0 -Pf 2 -Po 1
M 7.94319 22 (314.03, 343.81, 0.00), (47.73, 104.78), 13.47
M 8.33107 42 (419.51, 225.20, 0.00), (357.38, 7.14), 4.23
r -t 8.526714983 -Hs 2 -Hd 2 -Ni 2 -Nx 402.17 -Ny 395.17 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 2 -Ms 1 -Mt 800 -Is 1.0 -Id 2.0 -It cbr -Il 532 -If 0 -Ii 0 -Iv 30 -Pn cbr -Pi 0 -Pf 1 -Po 1
r -t 8.532555915 -Hs 2 -Hd 2 -Ni 2 -Nx 402.11 -Ny 395.18 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 2 -Ms 1 -Mt 800 -Is 1.0 -Id 2.0 -It cbr -Il 532 -If 0 -Ii 1 -Iv 30 -Pn cbr -Pi 1 -Pf 1 -Po 1
M 9.93999 0 (226.30, 434.11, 0.00), (32.32, 204.42), 11.64
s -t 10.565625155 -Hs 79 -Hd -2 -Ni 79 -Nx 209.89 -Ny 301.03 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 79.2 -Id 80.0 -It cbr -Il 512 -If 0 -Ii 4 -Iv 32 -Pn cbr -Pi 0 -Pf 0 -Po 1
r -t 10.635182162 -Hs 80 -Hd 80 -Ni 80 -Nx 50.30 -Ny 363.33 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 50 -Ms 48 -Mt 800 -Is 79.2 -Id 80.0 -It cbr -Il 532 -If 0 -Ii 4 -Iv 29 -Pn cbr -Pi 0 -Pf 2 -Po 1
M 10.77486 58 (115.38, 326.88, 0.00), (288.00, 351.52), 10.98
M 11.02768 28 (460.90, 311.07, 0.00), (153.34, 88.39), 18.78
M 11.08236 67 (160.83, 50.66, 0.00), (485.07, 80.08), 16.25
s -t 11.165845313 -Hs 1 -Hd -2 -Ni 1 -Nx 337.70 -Ny 415.62 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 1.0 -Id 2.0 -It cbr -Il 512 -If 0 -Ii 5 -Iv 32 -Pn cbr -Pi 2 -Pf 0 -Po 1
r -t 11.171361711 -Hs 2 -Hd 2 -Ni 2 -Nx 374.02 -Ny 399.31 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 13a -Md 2 -Ms 1 -Mt 800 -Is 1.0 -Id 2.0 -It cbr -Il 532 -If 0 -Ii 5 -Iv 30 -Pn cbr -Pi 2 -Pf 1 -Po 1
M 11.80416 24 (94.06, 252.37, 0.00), (492.74, 351.86), 6.37
M 12.04447 48 (166.98, 441.22, 0.00), (153.77, 145.30), 11.60
M 12.68424 17 (490.44, 308.50, 0.00), (404.24, 448.00), 18.34
M 13.18067 72 (111.61, 358.51, 0.00), (462.41, 65.80), 19.40
s -t 13.906898932 -Hs 7 -Hd -2 -Ni 7 -Nx 200.42 -Ny 209.84 -Nz 0.00 -Ne -1.000000 -Nl AGT -Nw --- -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 7.2 -Id 9.0 -It cbr -Il 512 -If 0 -Ii 6 -Iv 32 -Pn cbr -Pi 1 -Pf 0 -Po 1
M 13.91329 11 (125.39, 271.21, 0.00), (434.49, 383.09), 17.25
d -t 13.939183932 -Hs 7 -Hd 36 -Ni 7 -Nx 200.55 -Ny 209.55 -Nz 0.00 -Ne -1.000000 -Nl RTR -Nw CBK -Ma 13a -Md 24 -Ms 7 -Mt 800 -Is 7.2 -Id 9.0 -It cbr -Il 532 -If 0 -Ii 6 -Iv 30 -Pn cbr -Pi 1 -Pf 0 -Po 1

I don't understand why the routing packets are not picked up when running the awk file. I also use the same awk file for aodv, dsr and dsdv just change the routing protocol in the awk file, I am unaware if I am required to change any other parameters when changing the routing protocol. I cannot however obtain any results of routing packets and normalised routing load for any of the protocols despite being able to see RTR packets in the trace file.

Any help would be greatly appreciated as I cannot find any answers on the web and time is short for me to figure this out in order to complete my project.

Thanks.

Last edited by Tinkster; 08-20-2009 at 01:45 PM. Reason: fixed code tag
 
Old 08-20-2009, 01:54 PM   #2
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,986
Blog Entries: 11

Rep: Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880
Well, looking at the snippet of data you've provided none of
the lines match the criteria you're asking for.

The only line that has "RTR" in position 19 has a "d" in position 1,
while you require it to be an "s" or an "f" ... so awk is handling
the data exactly to your requirements.



Cheers,
Tink
 
Old 08-20-2009, 02:30 PM   #3
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
On checking the trace files I noticed all the RTR entries are marked D for dropped and I guess this is why the parameters awk file always returns zero for routing packets as it searches for forwarded or sent packets however all RTR entries in my trace files are marked D. Can anyone help to explain why this is the case and how I can fix it and analyse aodv, dsr and dsdv routing overhead?
 
Old 08-20-2009, 02:39 PM   #4
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
Thanks Tinkster, you are right I know my other post says exactly what you were explaining, I sent it before I noticed your thread as my page had not refreshed to show your reply. Is this normal behaviour that all RTR entries are marked D for the routing protocols or is there anything I can be doing wrong. I just don't understand why they can all be dropped packets for every simulation and that too for every routing protocol as surely routing packets would need to be sent, recieved and forwarded for routing to work. I am getting output results for packets sent and recieved so as I understand it packets must be getting routed for this to happen. If anyone can help explain why this happens and how I can fix it it would be greatly appreciated as my Uni project depends on it and analysing the routing overhead.
 
Old 08-20-2009, 03:11 PM   #5
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,986
Blog Entries: 11

Rep: Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880
Sorry, I have no idea what MANET is ... at this stage I'd recommend moving this thread
to networking as the problem is obviously with the data (and the way the network traffic
you're trying to analyse is handled), rather than with the script or its output?


Cheers,
Tink
 
Old 08-20-2009, 03:56 PM   #6
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
Thanks for your help, Tinkster. I shall post the thread on the Networking section.
 
Old 08-20-2009, 04:09 PM   #7
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
Cannot analyse normalised routing load as RTR packets show as dropped in trace file

HI,

I am simulating MANET routing protcols AODV, DSDV and DSR in NS-2.34 with varying parameters in order to compare them. I need to analyse the metrics packet delivery ratio, end to end delay and normalised routing load. I am using an awk file named parameters to analyse the trace files for these metrics. The problem is that all routing packets returns a value of zero in the awk output as in the trace file all RTR entries show as D for dropped and therefore are not picked up as the awk file searches for s sent or f forwarded RTR packets. All my trace files for different scenario files for all routing protocols give the entry of D dropped for all RTR entries. I am getting output for the data for PDR and end-to-end delay as they are based on the AGT entry.

I don't understand why all RTR entries are shown as D for dropped as surely for routing to work for the AGT packets then routing must take place for them to be sent and recieved, RTR packets would have to be sent, forwarded and recieved. Can anyone explain why all RTR entries show as D for dropped and how I can fix this?

My Uni project depends on analysing the metric NRL and without any analysis of routing packets sent and forwarded I cannot do this.

Any help would be greatly appreciated. I had posted this thread earlier in the newbie section and was advised to post it here in networking. http://www.linuxquestions.org/questi...0/#post3651138

I don't understand what the problem is or why it happening or how to fix it. Without being able to I cannot complete my Uni project. I am grateful for any help or suggestions.
 
Old 08-20-2009, 05:51 PM   #8
Tinkster
Moderator
 
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,986
Blog Entries: 11

Rep: Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880Reputation: 880
please don't ... I'll just move this one
 
Old 08-20-2009, 07:01 PM   #9
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
I must confess, I needed to look up MANET on the web:
http://www.olsr.org/docs/report_html/node9.html

Is this now an NS-2 configuration question? If so, you will need to post relevant information.
 
Old 08-25-2009, 09:11 AM   #10
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
Sorry I should have explained MANET (Mobile ad hoc network). I am not sure if it is something I have configured wrong or if it is a problem in NS2. I created scenario files and traffic files along with a tcl script that lays out the parameters and routing protocol to use, I created another script file that runs the tcl, scenario and traffic files and compares the output against the parameters in the awk files. It also repeats each simulation 3 times. As far as I can understand the procedure is correct the simulations run, and the output files are created along wtih the results from the parameters asked for in the awk files. I just don't understand why all the trace files show d for dropped for all RTR (router) entries meaning I can't analyse routing overhead. I don't understand why this happens at all if it is something I am doing or if it is some problem in NS2.
 
Old 08-25-2009, 09:17 AM   #11
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
Sorry I should have explained MANET (mobile ad hoc network). I am not sure what the problem is if it is in the configuration or if it is something to do with NS2. I have created scenario and traffic files and a tcl file that lays out the parameters and routing protocol to use. Another script file funs all 3 of these files an compares the output against the parameters in the awk files and sends that to an output file, it also repeats each simulation 3 times. The procedure seems to be correct the simulations run I get trace file output and the output files created with the results of the parameters in the awk files. I just don't understand why all trace files show d for dropped for all RTR (router) packets. I don't understand it at all or how to resolve it.
 
Old 08-25-2009, 10:07 AM   #12
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
The traffic type is CBR, the files are created using ns-2.34/indep-utils/cmu-scen-gen/cbrgen.tcl. The scenario files are created using setdest ns-2.34/indep-utils/cmu-scen-gen/setdest/setdest the tcl file has roughly the standard parameters as in the tcl files used in the NS2 tutorial http://www.isi.edu/nsnam/ns/tutorial/.
 
Old 08-25-2009, 11:23 AM   #13
Cataj
LQ Newbie
 
Registered: May 2009
Posts: 12

Original Poster
Rep: Reputation: 0
TCL file is based on the wireless1.tcl file from tutorial link.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Dropped packets Doolspin Linux - Software 1 10-22-2006 01:22 PM
too much dropped packets...Hi.. alaios Linux - Networking 2 02-10-2005 04:49 AM
Dropped packets - is this a problem?? benr77 Linux - General 4 10-04-2004 02:05 PM
dropped packets... sohmc Linux - Software 3 05-29-2003 09:26 AM


All times are GMT -5. The time now is 05:20 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration