lans in nam

[Ingela Anderton <ingela@docs.uu.se>]

Hi!


When I try to create a nam-trace for a lan simulation, exactly the
same way as for a point-to-point simulation I get the following result:



    (_o39 cmd line 1)
    invoked from within
"_o39 cmd attach-nam file4"
    invoked from within
"catch "$self cmd $args" ret"
    (procedure "_o39" line 2)
    (SplitObject unknown line 2)
    invoked from within
"$drpT_ attach-nam $namtrfd"
    (procedure "_o26" line 15)
    (Link/LanDuplex trace line 15)
    invoked from within
"$link_([$n1 id]:[$n2 id]) trace $self $file"
    (procedure "_o3" line 7)
    (Simulator trace-queue line 7)
    invoked from within
"$ns_ trace-queue $src $dst"
    (procedure "_o14" line 15)
    (LanLink attachLL line 15)
    invoked from within
"$self attachLL $src $dst"
    (procedure "_o14" line 28)
    (LanLink addNode line 28)
    invoked from within
"$lan addNode $nodelist $bw $delay"
    (procedure "_o3" line 3)
    (Simulator newLan line 3)
    invoked from within
"$ns newLan $nodelist $opt(bw) $opt(delay)  -llType $opt(ll) -ifqType $opt(ifq)  -macType $opt(mac) -chanType $opt(chan)"
    (procedure "create-topology" line 10)
    invoked from within
"create-topology"
    (file "lan.tcl" line 83)

Does it work differently for lans?

-- 
/Ingela

//The highway of life is always under construction. //

 	        |\      _,,,--,,_  ,)
                /,`.-'`'   -,  ;-;;' 
               |,4-  ) )-,_ ) /\
              '---''(_/--' (_/-'