[Ns-developers] DelayBox - ns-3
Matt Crinklaw
matt.crinklaw at gmail.com
Thu Apr 17 20:34:02 PDT 2008
sorry for the double, forgot to reply to all.
> Yep. These are outdated docs. The documentation generated in the
> ns-3-doc branch does generate a full list of all trace paths but, it has
> not been merged yet. So, In the meantime, the following should work:
>
> /NodeList/nodeid/ApplicationList/appid/TxPacket
>
> Hopefully, the next release due in a couple of weeks will document that
> and the trace connection process will also have some means of reporting
> what it is doing. I am sorry that this is painful for now :/
Well I've got a rough version of delaybox up and running doing
queueing and link delays as well as packet loss, but I still can't get
my source connected to the sink... Is there a way to get config to
print out a list of accessible trace sources at runtime? Or is there
something I have to do in addition to specifying the GetTypeId
function to get my application class registered with the metadata
system?
> /NodeList/nodeid/ApplicationList/appid/TxPacket
The nodeid is that which is given from node.GetId() ? And the
application id is the index of the application on the node?
More information about the Ns-developers
mailing list