-
I also have the same problem and after some searching in the architecture (
i.e. NS-manual)
of NS, I noticed that the monitor objects as they are now, upon their
initialization
are getting attached to a link object, not a node. This will not work for
wireless networks,
since there is no physical link from the start to attach a node to, but it
is created on demand.

One solution would be to attach (manually - by changing the tcl code of the
wireless node
creation) the monitor objects directly to the wireless node and from thereon
to monitor
every packet that is inserted, queued and dropped directly at the node.
Check chapter 16 about
wireless node creation and then chapter 25 "Trace and monitoring support"
and specifically
the section about the monitor objects, to see how they are attached to the
link object of a wired node. The code is in TCL, so any changes will be
quick and easy to implement. Afterwards we can combine the techniques from
the 2 chapters and create a new "init-monitor " that gets attached to a
wireless node "per se" and not to a link.

Unfortunately, currently there is no straightforward method of implementing
this.
When I'll have it ready, I'll post it up. Or you maybe...

Regards,

-Fk


On 8/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> ---------- Forwarded message ----------
> From: "Amita Singh" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Date: 26 Aug 2006 10:18:33 -0000
> Subject: [ns] I have tried to put queue-monitor on the wireless node
> Hi all,I have tried to put queue-monitor on the wireless node, but I got
> an error about link.Is it possible to use queue-monitor on wireless
> node.If possible, is there any example of how to use it. Othervise any
> other method to get interface queue length.Thanks in advance.
>
>

-- 
Filippos N Kolovos

Software Systems Analyst & Engineer
M.Sc. (Eng.) in Data Communications

Automation & Networking Department
University of Macedonia Library
Egnatia 156, P.O.Box 1591
540 06 Thessaloniki, Greece

E-Mail: [EMAIL PROTECTED],
           [EMAIL PROTECTED]
----------------------------------------------

Reply via email to