[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TCP monitor trace





Federico Orlandini wrote:

> Hi ,
> try to use Agent/TCP/FullTcp as source and sink for your agents.
>
> Bye
>
> Federico Orlandini
> E-Mail : [email protected]

Thanks for reply
    I have tried your suggestion but I think the problem falling on how
to attach lossmonitor on TCP sink, otherwise when I tried FullTcp on
both source and sink even no traffic flowing to each other on nam.
    I list the error message and source code hope someone could give me
a hand to realize what happened on this simulation?
thanks
regards

############## Set up TCP/Tahoe Agent ##############
set tcp [new Agent/TCP/FullTcp]
$tcp set class_ 1
$tcp set fid_ 1

set sink [new Agent/TCP/FullTcp]
$ns attach-agent $n0 $tcp
$ns attach-agent $n3 $sink
set loss1 [new Agent/LossMonitor]
$ns attach-agent $n3 $loss1    <=======  question ??

$ns connect $tcp $sink
# Equivelant of set tcp [$ns create-connection TCP $n0 TCPSink $n3 1]

set ftp [new Application/FTP]
$ftp attach-agent $tcp

#########################################

    (_o89 cmd line 1)
    invoked from within
"_o89 cmd attach-agent _o87"
    invoked from within
"catch "$self cmd $args" ret"
    (procedure "_o89" line 2)
    (SplitObject unknown line 2)
    invoked from within
"$loss1 attach-agent $sink "
    (file "tcp.tcl" line 73)