Re: new nam on a Sun

["Kun-chan Lan" <klan@usc.edu>]

Anastasia,

  You can still see the ray-like packet flow in newer version nam once you
turn "routerTrace" on in your tcl script .

I've tried to duplicate the scenario you described , but I didn't
observe the problem you mentioned on both linux and freebsd (
and I couldn't think of a logical explanation why running two concurrent nam
instances will cause problem like that ...) . So, could you please try to
use the nam binary and trace file I sent you last time , to see if the
problem still persist .
By the way, you should be able to have a thicker packet in wireless3 if
you're using the latest snapshot like I told you last time (again, please
try the nam binary I sent to make sure we're using the same nam)

Kun-chan

-----Original Message-----
From: Anastasia Leventi-Peetz <leventi@fgan.de>
To: kclan@ISI.EDU <kclan@ISI.EDU>
Cc: ns-users@mash.CS.Berkeley.EDU <ns-users@mash.CS.Berkeley.EDU>
Date: Wednesday, February 23, 2000 2:17 AM
Subject: new nam on a Sun


>
>
>
>    Dear Kun-chan,
>
>        I find the oldest way to show with the animator the exchange
>of packets (the line rays) much better than the way of homocentral crises
>because in the old manner one knows which node communicate with which.
>Today I got a terrible surprise:
>I had wireless1 in a stopped nam process, (older version of nam showing
rays)
>and started the newer nam for wireless2.
>The result was, in the animation the wired part was reduced to a point
>and without energy modus, the mobile IP became red by sending.
>The two nam processes shouldn't communicate with one another isn't it so?
>Please give me a hint how can I make the transfer of data on the wired
>part a little bit thicker by the animation?!
>best regards:
>Anastasia
>