anil reddy schrieb:
>     in a program to perform wired emulation i am getting the output as
> below. i am not able to understand the meaning of  cc, writing to
> target, linked sock etc. any help will be appreciated.
>   
_o13, _o18 (in general all _o<number>) refer to TCL objects inside ns-2. 
Currently I don't have access to the source code to look up the exact 
meaning of the output. Put it looks like a debug output that tells you 
that object _o13 (the TAP agent) received packets at certain times with 
a size of 78 or 202 bytes and writes them to the object _o18. This 
should be a node or agent. The warning from the RealTimeScheduler tells 
you that simulation time and real time are out of sync more than the 
specified threshold. This can happen if you have a slow machine, high 
throughput or other processes running on the simulator host. It helps to 
reduce the CPU load and/or to set nse to run with real-time priority 
(e.g. using rude or rerude command). If this is not sufficient you can 
try the performance enhanced nse version - see the nsnam Wiki 
(contributed code) for the link.

> When configured, ns found the right version of tclsh in
> /root/ns-allinone-2.29/bin/tclsh8.4
> but it doesn't seem to be there anymore, so ns will fall back on
> running the first tclsh in your path. The wrong version of tclsh may
> break the test suites. Reconfigure and rebuild ns if this is a
> problem.
> TapAgent(_o13): linked sock 3 as READABLE
> listening for pings on addr 192.168.1.8...
> 0.000029: Tap(_o13): recvpkt, cc:78
> 0.000029: Tap(_o13): recvpkt, writing to target: _o18
> 0.000214: Tap(_o13): recvpkt, cc:78
> 0.000214: Tap(_o13): recvpkt, writing to target: _o18
> 0.000256: Tap(_o13): recvpkt, cc:78
> 0.000256: Tap(_o13): recvpkt, writing to target: _o18
> 0.313650: Tap(_o13): recvpkt, cc:202
> 0.313650: Tap(_o13): recvpkt, writing to target: _o18
> RealTimeScheduler: warning: slop 0.105400 exceeded limit 0.010000
> [clock_:0.419066, p->time_:0.313666]
> 0.419096: Tap(_o13): recvpkt, cc:78
> 0.419096: Tap(_o13): recvpkt, writing to target: _o18
> 0.419194: Tap(_o13): recvpkt, cc:78
> 0.419194: Tap(_o13): recvpkt, writing to target: _o18
> 0.599329: Tap(_o13): recvpkt, cc:78
> 0.599329: Tap(_o13): recvpkt, writing to target: _o18
> 0.705903: Tap(_o13): recvpkt, cc:78
> 0.705903: Tap(_o13): recvpkt, writing to target: _o18
> 0.729205: Tap(_o13): recvpkt, cc:78
> 0.729205: Tap(_o13): recvpkt, writing to target: _o18
> 0.745454: Tap(_o13): recvpkt, cc:78
> 0.745454: Tap(_o13): recvpkt, writing to target: _o18
> 0.745541: Tap(_o13): recvpkt, cc:78
> 0.745541: Tap(_o13): recvpkt, writing to target: _o18
> 0.837391: Tap(_o13): recvpkt, cc:78
> 0.837391: Tap(_o13): recvpkt, writing to target: _o18
> 1.002148: PingResponder(_o15): not ICMP (proto: 17)
> IP v:4, ihl:5, tos:0x0, id:21262, off:0 [df:0, mf:0], sum:15459, prot:17
> IP src:192.168.1.5, dst: 192.168.1.255
> IP len:78 ttl: 128
> 1.002319: PingResponder(_o15): not ICMP (proto: 17)
> IP v:4, ihl:5, tos:0x0, id:15743, off:0 [df:0, mf:0], sum:18294, prot:17
> IP src:192.168.2.137, dst: 192.168.2.255
> IP len:78 ttl: 128
> 1.002349: PingResponder(_o15): not ICMP (proto: 17)
> IP v:4, ihl:5, tos:0x0, id:15744, off:0 [df:0, mf:0], sum:18038, prot:17
> IP src:192.168.2.137, dst: 192.168.2.255
> IP len:78 ttl: 128
>   

Daniel.

Reply via email to