Anuradha wrote:
> did you find the solution of "Classifier no-slot problem".
> I am also having the same problem.
Actually, I once had this very problem as well. Happened to me when I was
extending UdpAgent to allow "connect-on-demand" functionality and I had
not given the address in proper format (which should be ns_addr_t
(comprising of an address and port part) as opposed to ns_addr).
Your mileage may vary but you might wanna check that any destination
address you've provided (either through Tcl or C++) is correct. Basically,
ns2 keeps record of the nodes' addresses in terms of slots, and as far as
I can understand the error message, the (hashed) destination address of
_o28 cannot be found. See the manual if you like to know (a bit) more.
--T
> Armando Garcia B. wrote:
>> I have seen a lot of mails with this problem:
>>
>> --- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) ---
>> _o28: no target for slot -1
>> _o28 type: Classifier/Hash/Dest
>> content dump:
>> classifier _o28
>> 0 offset
>> 0 shift
>> 2147483647 mask
>> 1 slots
>> slot 5: _o99 (Classifier/Port)
>> -1 default
>> ---------- Finished standard no-slot{} default handler ----------
>>
>>
>> Now, I have the same problem. and I have invested a lot of time, but I
>> can not found the solution.
>>
>> Does some any know the solution? or any idea may be.
>>
>> Regards.
>> --
>> Armando Garcia B.
