[ns] TCP send sduplicate packet?!?

2011-05-27 Thread thn80


Hello,

I simulated the exactly same scenario with two routing protocols (AOMDV and
a modification of AOMDV).
When using the modified protocol there is a TCP packet dropped. After the
Retransmission Timeout of 3 seconds, the packet is send again (time
8.0).
My problem/question is, why TCP sends the data packet two times (time
8.00382380 and 8.008261611) and not only one time as specified in the
simulation script. The standard AOMDV only sends the packet one time.
I think this behaviour has something to do with the dropped packet, but I
don't understand why.

Here are the lines from the trace files:

AOMDV
-

s -t 5.0 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 40 -If 0 -Ii 4 -Iv 32 -Pn tcp -Ps 0 -Pa 0 -Pf 0 -Po 0 
r -t 5.009845349 -Hs 3 -Hd 3 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 3 -Ms 2 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 60 -If 0 -Ii 4 -Iv 28 -Pn tcp -Ps 0 -Pa 0 -Pf 3 -Po 0 
s -t 5.009845349 -Hs 3 -Hd -2 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 3.0 -Id 0.0
-It ack -Il 40 -If 0 -Ii 5 -Iv 32 -Pn tcp -Ps 0 -Pa 0 -Pf 0 -Po 0 
r -t 5.011312029 -Hs 0 -Hd 0 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 0 -Ms 1 -Mt 800 -Is 3.0 -Id
0.0 -It ack -Il 60 -If 0 -Ii 5 -Iv 28 -Pn tcp -Ps 0 -Pa 0 -Pf 3 -Po 0 
s -t 5.011312029 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 6 -Iv 32 -Pn tcp -Ps 1 -Pa 0 -Pf 0 -Po 0 
r -t 5.013263154 -Hs 3 -Hd 3 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 3 -Ms 2 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 6 -Iv 28 -Pn tcp -Ps 1 -Pa 0 -Pf 3 -Po 0 
s -t 5.013263154 -Hs 3 -Hd -2 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 3.0 -Id 0.0
-It ack -Il 40 -If 0 -Ii 7 -Iv 32 -Pn tcp -Ps 1 -Pa 0 -Pf 0 -Po 0 
r -t 5.015109835 -Hs 0 -Hd 0 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 0 -Ms 1 -Mt 800 -Is 3.0 -Id
0.0 -It ack -Il 60 -If 0 -Ii 7 -Iv 28 -Pn tcp -Ps 1 -Pa 0 -Pf 3 -Po 0 

AOMDV mod.


s -t 5.0 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 40 -If 0 -Ii 4 -Iv 32 -Pn tcp -Ps 0 -Pa 0 -Pf 0 -Po 0 
The first packet is dropped here !!!
s -t 8.0 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 40 -If 0 -Ii 5 -Iv 32 -Pn tcp -Ps 0 -Pa 0 -Pf 0 -Po 0 
r -t 8.001757125 -Hs 3 -Hd 3 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 3 -Ms 2 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 60 -If 0 -Ii 5 -Iv 28 -Pn tcp -Ps 0 -Pa 0 -Pf 3 -Po 0 
s -t 8.001757125 -Hs 3 -Hd -2 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 3.0 -Id 0.0
-It ack -Il 40 -If 0 -Ii 6 -Iv 32 -Pn tcp -Ps 0 -Pa 0 -Pf 0 -Po 0 
r -t 8.003823805 -Hs 0 -Hd 0 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 0 -Ms 1 -Mt 800 -Is 3.0 -Id
0.0 -It ack -Il 60 -If 0 -Ii 6 -Iv 28 -Pn tcp -Ps 0 -Pa 0 -Pf 3 -Po 0 
s -t 8.003823805 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 7 -Iv 32 -Pn tcp -Ps 1 -Pa 0 -Pf 0 -Po 0 
r -t 8.006174930 -Hs 3 -Hd 3 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 3 -Ms 2 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 7 -Iv 28 -Pn tcp -Ps 1 -Pa 0 -Pf 3 -Po 0 
s -t 8.006174930 -Hs 3 -Hd -2 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 3.0 -Id 0.0
-It ack -Il 40 -If 0 -Ii 8 -Iv 32 -Pn tcp -Ps 1 -Pa 0 -Pf 0 -Po 0 
r -t 8.008261611 -Hs 0 -Hd 0 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 0 -Ms 1 -Mt 800 -Is 3.0 -Id
0.0 -It ack -Il 60 -If 0 -Ii 8 -Iv 28 -Pn tcp -Ps 1 -Pa 0 -Pf 3 -Po 0 
s -t 8.008261611 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 9 -Iv 32 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
r -t 8.010212736 -Hs 3 -Hd 3 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 3 -Ma 46 -Md 3 -Ms 2 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 9 -Iv 28 -Pn tcp -Ps 2 -Pa 0 -Pf 3 -Po 0 
s -t 8.010212736 -Hs 3 -Hd -2 -Ni 3 -Nx 1000.00 -Ny 600.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 3.0 -Id 0.0
-It ack -Il 40 -If 0 -Ii 10 -Iv 32 -Pn tcp -Ps 2 -Pa 

[ns] Delay in ns2

2011-05-19 Thread thn80


Hello,

I have two routing protocols and got the following two tracefiles (it's only
a part of each tracefile). My problem is that protocol 2 is a modification
of protocol 1 and in the following tracefiles the protocols exchange exactly
the same packets, but the time values -t in the tracefiles are different.
Can someone tell me at which positions in ns2 the packet delay is
calculated?
Protocol 1 is AOMDV on top of a WiFi connection.

Routing protocol 1:
--
s -t 5.1 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 8 -Iv 32 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
r -t 5.1 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 8 -Iv 32 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
s -t 5.1 -Hs 0 -Hd 1 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1060 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
s -t 5.10051 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 1 -Ms 0 -Mt 0 
r -t 5.100594222 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 1 -Ms 0 -Mt 0 
s -t 5.100604222 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma f5 -Md 0 -Ms 0 -Mt 0 
r -t 5.10066 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma f5 -Md 0 -Ms 0 -Mt 0 
s -t 5.10067 -Hs 0 -Hd 1 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1118 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
r -t 5.100840741 -Hs 1 -Hd 1 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 1 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 1 -Po 0 
r -t 5.100840741 -Hs 1 -Hd 1 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 1 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 1 -Po 0 
f -t 5.100840741 -Hs 1 -Hd 2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 1 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 8 -Iv 29 -Pn tcp -Ps 2 -Pa 0 -Pf 1 -Po 0 
s -t 5.100850741 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 
r -t 5.100910963 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 
s -t 5.101020296 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 2 -Ms 1 -Mt 0 
r -t 5.101104519 -Hs 2 -Hd -2 -Ni 2 -Nx 900.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 2 -Ms 1 -Mt 0 
s -t 5.101114519 -Hs 2 -Hd -2 -Ni 2 -Nx 900.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma f5 -Md 1 -Ms 0 -Mt 0 

Routing protocol 2:
--
s -t 5.1 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl AGT -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 8 -Iv 32 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
r -t 5.1 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1040 -If 0 -Ii 8 -Iv 32 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
s -t 5.1 -Hs 0 -Hd 1 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 0 -Ma 0 -Md 0 -Ms 0 -Mt 0 -Is 0.0 -Id 3.0
-It tcp -Il 1060 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
s -t 5.10039 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 1 -Ms 0 -Mt 0 
r -t 5.100474222 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 13b -Md 1 -Ms 0 -Mt 0 
s -t 5.100484222 -Hs 1 -Hd -2 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma f5 -Md 0 -Ms 0 -Mt 0 
r -t 5.10054 -Hs 0 -Hd -2 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma f5 -Md 0 -Ms 0 -Mt 0 
s -t 5.10055 -Hs 0 -Hd 1 -Ni 0 -Nx 500.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 0 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1118 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 0 -Po 0 
r -t 5.100720741 -Hs 1 -Hd 1 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl MAC -Nw --- -CHhops 1 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 -Id
3.0 -It tcp -Il 1060 -If 0 -Ii 8 -Iv 30 -Pn tcp -Ps 2 -Pa 0 -Pf 1 -Po 0 
r -t 5.100720741 -Hs 1 -Hd 1 -Ni 1 -Nx 700.00 -Ny 400.00 -Nz 0.00 -Ne
-1.00 -Nl RTR -Nw --- -CHhops 1 -Ma 46 -Md 1 -Ms 0 -Mt 800 -Is 0.0 

[ns] Forwarding packet from classifier-addr to classifier-port

2011-05-02 Thread thn80


Hello,

how can the address classifier access the recv() function of the port
classifier? Normally this is done by using mshift() to get a slot num,ber
out of the destination node address. But in this case every node should be
able to access the port classifier, not only the destination node. That's
why I can't use mshift().

Thanks,

Thomas
-- 
View this message in context: 
http://old.nabble.com/Forwarding-packet-from-classifier-addr-to-classifier-port-tp31524756p31524756.html
Sent from the ns-users mailing list archive at Nabble.com.



[ns] How to process data packets in routing layer?

2011-04-29 Thread thn80


Hello,

for a novel routing protocol I have to extract some information from data
packets to store this information into the routing table.
How is it possible to access data packets from the routing layer?

Thanks,

Thomas
-- 
View this message in context: 
http://old.nabble.com/How-to-process-data-packets-in-routing-layer--tp31505299p31505299.html
Sent from the ns-users mailing list archive at Nabble.com.



Re: [ns] Scheduler::instance().clock() in ns.2.30

2011-04-13 Thread thn80


AFAIK it returns a floating number which tells you the time in seconds since
your simulation has been started.



molly-5 wrote:
 
 
 Hi all,
 
 Can anybody tell me something about Scheduler::instance().clock(), the
 function returns system time, what kind of system time it returns? Does
 the
 return time including the current system date and time or something else?? 
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Scheduler%3A%3Ainstance%28%29.clock%28%29-in-ns.2.30-tp31378908p31380352.html
Sent from the ns-users mailing list archive at Nabble.com.



[ns] border wrapping

2011-04-13 Thread thn80


Hello,

is it possible in ns2 to wrap borders?
If a node reaches the left border, the node should disappear at the left
side and should appear on the right sight of the simulation area. The same
question is about radio communication in wireless scenarios. Is it possible
that a node transmits out of the left border and communicates with a node on
the right border?

How can I configure ns2 to do this? What is the default setting for ns2?

Thanks,

Thomas
-- 
View this message in context: 
http://old.nabble.com/border-wrapping-tp31380274p31380274.html
Sent from the ns-users mailing list archive at Nabble.com.