No slot error in NS2
 

When I run my tcl file in NS2 im getting this error.

--- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) ---
_o12: no target for slot 4294967295
_o12 type: Classifier/Hash/Dest
content dump:
classifier _o12
0 offset
0 shift
1073741823 mask
1 slots
slot 0: _o129 (Classifier/Port)
-1 default
---------- Finished standard no-slot{} default handler ----------
ive attached my tcl file here..
I don't understand what this error is..kindly give a solution. TY

$ ns preethisingh.tcl
... I get : "invalid command name "Agent/Security_packet".

* You will have to tell which "extra protocol" you have added.

The edited file "preethisingh.tcl" is attached.
Your "my_tcl_file.tcl.txt" is missing the last two lines.
-

No slot error
 

I have added a new packet type to NS2. named. security_packet. Does the error mean that there is no path between source node and destination node? if so where have I made the mistake in my tcl file..pls help.

← #3 .
A new packet type would appear in :
ns-<unknown-version>/<folder>/file.cc
common/packet.h
tcl/lib/{ ns-decault.tcl?, ns-lib.tcl?, ns-packet.tcl, etc.}

+ that all changes to files in ns-2.xx///{ files.cc, .h, tcl/lib/**}
.. must be compiled into a new executable 'ns' : $ make clean && make

.. Then the new function may be usable in a simulation.

-

No slot error
 

when I added new packet type to ns 2.35 . I made the following entries
1)I added security_packet.cc and security_packet.h to ns-allinone-2.35/ns-2.35/apps
2)then I made entry in packet.h
3)then in ns-default.tcl
4) then in ns-packet.tcl
5) then makefile.in
6)then I used ./configure
7) then make
should I make any change in tcl/lib/ns-lib.tcl ?? or anywhere else

← #5 .

If 4) 5) 6) are the commands you used, you missed 'make clean'

Please do : $ make clean && make

No slot error
 

Now I used make clean and then make.. still im getting the error mentioned in #1. do I have to make any change in tcl/lib/ns-lib.tcl while adding new packet type?

# 7.
I don't know.

? May be you are just using "new packet type" in an impossible way ?